LARTC - Oct 2002 - Problem with windows routing

Hi,

    I have little problem with windows computers and two routers on one
subnet. One router is to route packets to the internet and the second to
route packets to other LANs. By dhcpd, windows machines get the default
gateway the LAN router. But they change their route tables because some
packets go of course to internet. I turned off sending redirects on both
routers but windows do it on their own I think. The problem is when I want
to connect from the other LAN to this segment, the comupters doesn''t
answer,
however ping works well. (Because the packet comes from LAN router but
windows has the default route to the inet router and the packet gets lost)
When I set the route table on some of those windows machines manually it
works fine but that''s thing I cannot do by dhcpd. Unfortunately, dhcpd
is
the only way to configure all those f*c*i*g (;-)) windows.
    One solution is to set mask of the internet router to something else so
that the windows machines wouldn''t see it and set default route to the
LAN
router. On the LAN router set virtual interface to see the internet router
etc. etc. In addition to this complicated solution, the packets would double
the bandwidth on the segment :-(

Any idea?

Thanks very much,
Vladimir Trebicky

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

> I turned off sending redirects on both routers
> but windows do it on their own I think
Why?
> Because the packet comes from LAN router but windows 
> has the default route to the inet router and the packet gets lost
Your internet router does NAT I think? Then it seems logical..
> when I set the route table on some of those windows machines 
> manually it works fine but that''s thing I cannot do by dhcpd
Simplest solution is re-enabling redirects on the inet router (I don''t
see
the problem only that the windows box builds a big route table with many
single routes) 

Second simple solution is adding the routes to the second LAN manually on
the windows boxes and use the -p switch... With -p they become permanent
routes even if you restart the machine.

Niels.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

You discovered it :-) Probably it is the NAT ! When the packet returns via
the inet router it gets someone else''s ip.

So I must set in iptables on the inet router not to SNAT packets not coming
to inet ;-)

Thanks,

Vladimir Trebicky

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/