As suspected, the problems lie in Windows...
In spite of having the gateway defined under TCP/IP properties, winipcfg didn't show a default gateway. Manually adding the gateway with the command "route add 0.0.0.0 mask 0.0.0.0 192.168.1.1" makes everything work (and winipcfg correctly reports the gateway).
Dave
At 16:32 15/05/00 +1200, you wrote:
Hello all,- To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
I have diald working on the gateway machine but can not get Windows clients to go through it. Under Windows, TCP/IP properties/gateway is set to the Linux IP address (which I can happily ping). However, a ping to (say) sun.com doesn't appear to even get as far as the Linux machine (which is watching with tcpdump). If I bring the link up under Linux and add a specific route to an outside address via the gateway (from the DOS command prompt) then I can ping the address.
Any clues please... I suspect MS software - Grrrrr.
I have ipchains set up as follows:
Chain input (policy ACCEPT):
Chain forward (policy DENY):
target prot opt source destination ports
MASQ all ------ 192.168.1.0/24 anywhere n/a
DENY tcp ------ anywhere anywhere netbios-ns:netbios-ssn -> any
DENY udp ------ anywhere anywhere netbios-ns:netbios-ssn -> any
Chain output (policy ACCEPT):
Many thanks,
Dave
- To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
