[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

ip forwarding; was Re: /etc/resolv.conf, /etc/ppp/resolv.conf, dhcp3-server and dnsmasq

Doug & others,

dat> DNS and IP forwarding are two separate issues. 

OK; with ipmasq installed, a Debian client  
communicates through the router system just as if 
directly connected.  One more small problem 
solved.  Thanks.

dat> You need to enable IP forwarding as well 
as: see /etc/sysctl.conf.

Prior to installing ipmasq, there was no forwarding
even with net.ipv4.conf.default.forwarding=1 .

ipmasq continues to work just as well with 
net.ipv4.conf.default.forwarding commented out;
which I assume is equivalent to 
net.ipv4.conf.default.forwarding=0 .  (Ever 
wish that configuration texts were less ambiguous?)

The Windows 98 client system is not so cooperative.
If it is connected to the Debian router with the 
crossover cable which works for the Debian client, 
the link lights are on but no communication 
is evident.  This is the pertinent stanza from 
/etc/network/interfaces in the router.

# Interface to LAN  
iface eth3 inet static
	up	route add	-host all-ones dev eth3
	down	route delete	-host all-ones dev eth3

A hub and two patch cables produce the same 
result as the crossover cable.

Any tips on how to get a Windows client connected?

Thanks,          ... Peter E.

Desktops.OpenDoc  http://carnot.yi.org/

Reply to: