Hi,
> When you are doing things on the gateway they will
> not get masqueraded!
Yes, but I was thinking that maybe some of the TCP/IP
stuff goes haywire when the machine is masquerading
for others, as it did work fine before it was a
gateway.
> Only the ones behind the gateway machine will get
> masqueraded. This is
> not the problem.
> And since the machines behind the gateway work fine
> I suspect that the
> problem is with the gateway machine's browsing setup
> - possibly DNS,
> routing.
Yes, I think it may be a routing problem. I don't
think DNS is an issue, as performance remains this way
after names are resolved.
The machines are numbered 192.168.0.x, the gateway in
question has an IP of 203.56.8.98*, and it's private
IP is 192.168.0.254.
Here is the output from route (formatted to fit):
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.0.254 0.0.0.0 255.255.255.255 UH 0 0 0
eth1
203.56.8.0 0.0.0.0 255.255.255.128 U 0 0 0
eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 203.56.8.1 0.0.0.0 UG 0 0 0
eth0
If someone could kindly comment on this, that would be
great. I don't know what the first entry is doing
there, but the rest looks reasonable to me...
Regards,
Alex
*fake, but accurate for the purposes of the question
__________________________________________________
Do You Yahoo!?
Yahoo! Messenger - Talk while you surf! It's FREE.
http://im.yahoo.com/
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
