solaris9x86 as a router

[MrKotter]

<snip>

> But from the WinWorkstation residing on 172.16.0.0 net with IP
> 172.16.0.144
> I CAN
> ping to 172.16.0.220 (iprb1 on Solx86_9)
> ping to 193.87.54.220 (iprb0 on Solx86_9)
> I CANNOT
> ping to x.x.x.240 (for example)
> ping to x.x.x.129 (gateway/router to internet for x.x.x.128 address
> range)
> and this is valid both for ip_forwarding = 0 and ip_forwarding = 0
> (manualy set)

Routing 101 ;-)

Chances are the machines on 193.87.54.128/25 do not have a route
pointing back to 193.87.54.220 for the 172.16.0.0 network, so they will
be sending the return ping packets out their default route to the
internet instead of sending them back to the solaris machine.

Easiest way to fix is to add a route to the x.x.x.129 box for the
172.16.0.0 network and have the other hosts bounce of that. Or you could
configure routes on everything on 193.87.54.128/25.

The problem is NOT on the solaris box. Run snoop on the interfaces to
see what's happening.

Rgs,
Kot

[Martin Schoen]

MrKotter wrote:

>> But from the WinWorkstation residing on 172.16.0.0 net with IP
>> 172.16.0.144
>> I CAN
>> ping to 172.16.0.220 (iprb1 on Solx86_9)
>> ping to 193.87.54.220 (iprb0 on Solx86_9)
>> I CANNOT
>> ping to x.x.x.240 (for example)
>> ping to x.x.x.129 (gateway/router to internet for x.x.x.128 address
>> range)
>> and this is valid both for ip_forwarding = 0 and ip_forwarding = 0
>> (manualy set)

>
>
> Routing 101 ;-)

Nope. Or, partly. NATting should be the clue.

With a routing entry on your router (or the half-external hosts) you
might reach the external router, but you cannot get to internet with
your 172.16.X.X addresses.
Either your SUNBox (preferably) or your InternetRouter must do this job
and hide the internal addresses behind something that gets routed
through the internet (e.g. its own external ip).

Martin

[Darren Dunham]

Dusan <dkulisie@truni.sk> wrote:

> But NO ip_forwarding has been enabled after reboot. I know that due to
> the algorithm of routing after the system had found a file
> defaultrouter no in.rdisc and in.routed had been started. But
> sunSupportDoc mentioned above claims that static routing only will be
> enabled (and this is what I would like the most) when the
> corresponding startup script inetinit finds more than one network
> interface (which is clearly true in my case).

I believe this behavior has changed over timer. You may prefer to force
ip_forwarding on via ndd in a startup script. It appears that the stock
script will force ip_forwarding off if there is a default router
configured.

if [ -z "$defrouters" ]; then
[snip]
else
/usr/sbin/ndd -set /dev/ip ip_forwarding 0
fi

However, as others have said, this won't make everything work. The
internet as a whole will not have a router for traffic from 172.16.0.0.
You'd need to put them on the class C which the ISP has given you, or
you'd need to do NAT on the solaris box.

--
Darren Dunham [email]ddunham@taos.com[/email]
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >