attached mail follows:
Many thanks to all who have responded:
Henry Yiin
Imre Kolos
Casper Dik
Rahul Roy
Bruce R. Zimmer
Prashand Ranade
Nadkishor Kale
All pointed out
1. to remove /etc/defaultrouter
2. this will enable the Ultra 5 to act as a router
5. to declare in an (extra) script or in S72inetsvc the default route
route add default 149.243.224.1 1
That's it.
Again, many thanks!
Rainer B.
Rainer.Blaes@ri.dasa.de wrote:
> Dear experts,
>
> we have installed an Ultra 5 under Solaris 2.6 as a router
> between to 2 subnets 224 and 225:
>
> +----------------+ |
> | | +-------------+
> | Sun 1 | | CISCO router|
> | | 149.243.224.1 +-------------+
> +----------------+ |
> | 149.243.224.2 |
> | 224 LAN |
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> |
> |
> |
> ----------------
> | 149.243.224.3 |
> | Ultra 5 |
> | 149.243.225.1 |
> ----------------
> |
> |
> | 225 LAN
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> |
> |
> |
> Sun(s) with .225.x
>
> On the Ultra 5 we have defined in /etc/defaultrouter 149.243.224.1 as
> our default router to other in-house LANs and on the Sun 1 we are using
> a static route 'route add net 149.243.225.0 149.243.224.3 1' to have
> access to the Suns in the 225 LAN.
>
> In this case we can't ping from Sun 1 to the Suns in the 225 LAN.
>
> When we delete on the Ultra 5 the /etc/defaultrouter then we can reach all
> Suns in the 225 LAN.
>
> Studying /etc/init.d/inetinit we find out that this is caused by the actions
>
> a) ndd -set ip_forwarding 1
> b) in.routed
> c) in.rdisc
>
> But now all Suns in the 225 LAN have no access to the other in-house LANs
> over the Ultra 5 - CISCO router.
>
> Is there any way, clue to correct our problem?
>
> Many thanks in advance!
>
> Rainer Blaes
> DASA-Ri, Bremen (Germany)
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:31 CDT