[plug] Still not able to route to adsl
Matt Kemner
zombie at penguincare.com.au
Sat May 1 20:11:35 WST 2004
Quoth bob:
> tcpdump gives stuff like
> 19:22:35.870650 192.168.0.111 > 202.72.177.62: icmp: echo request (DF)
>
> Its stopping at the NB1300 (or going out and not returning -hard to say
> which, the leds on the NB1300 are not that informative)
> (just checked... yes it does ping via ppp0 :)
It's possible the NB1300 doesn't NAT anything that isn't 192.168.1.x and
therefore westnet is receiving packets with source of 192.168.0.x which
they most likely drop, and even if they didn't spark would not know how to
reply to you.. :)
I don't know if you can tell the router to NAT for you - it's probably
easier to just NAT on the Linux box.
> Hmm... pinging the ADSL assigned IP from spark is VERY slow. I would have
> expected much better than min/avg/max = 1041.3/1595.5/2040.1 ms to a
> westnet IP#
Yes, should be much better than that, unless the LinuxIT link was busy at
the time (unlikely since PLUG is the only thing hanging off that link now,
at least when we're not in the office)
> > iptables -t nat -vnxL
> > look for -j SNAT or -j MASQUERADE
>
> pkts bytes target prot opt in out source
> destination
> 59 4468 MASQUERADE all -- * ppp0 192.168.0.0/24
> 0.0.0.0/0
> 60 4560 MASQUERADE all -- * ppp0 192.168.1.0/24
> 0.0.0.0/0
> No -j SNAT or -j MASQUERADE !?
My bad, I meant look for MASQUERADE in the target
> Looks to me like 192.168.0.0/24 and 192.168.1.0/24 are masq'd out ppp0
> though (yes?)
Correct.
Do this to MASQ packets going out eth1 too:
iptables -t nat -A POSTROUTING -o eth1 -s 192.168.0.0/24 -j MASQUERADE
- Matt
More information about the plug
mailing list