Hi there, > Just a thought. Do you other machines have 192.168.20.254 > shown as your gateway?
Yes they were coming. I've realised my problem and solved it anyhow. Quick rundown: > : eth0 Link encap:Ethernet HWaddr 00:00:E8:74:32:FD > : inet addr:192.168.20.254 Bcast:192.168.20.255 Mask:255.255.255.0 > : UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > : RX packets:3042 errors:0 dropped:0 overruns:0 > : TX packets:1038 errors:0 dropped:0 overruns:0 > : Interrupt:10 Base address:0xfca0 > > : eth1 Link encap:Ethernet HWaddr 00:00:E8:D6:D5:21 > : inet addr:203.17.240.6 Bcast:203.17.240.255 Mask:255.255.255.224 > : UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > : RX packets:14850 errors:0 dropped:0 overruns:0 > : TX packets:1203 errors:0 dropped:0 overruns:0 > : Interrupt:11 Base address:0xfcc0 I assumed from the following that the masquerading rule needs to be applied to eth0. But i was wrong, it needed to be applied to eth1. ie. ipfwadm -F -a masquerade -W eth0 -S 192.168.20.0/24 -D 0.0.0.0/0 needed to be changed to: ipfwadm -F -a masquerade -W eth1 -S 192.168.20.0/24 -D 0.0.0.0/0 and it was all good. I would have thought that the masquerading would need to be applied to the internal interface? Regards, Marc-Adrian Napoli Connect Infobahn Australia +61 2 92811750
