ok, i needed to do the following on the gateway.
iptables --table nat -A POSTROUTING --out-interface ppp0 -j MASQUERADE
iptables -A FORWARD --in-interface eth0 -j ACCEPT
Aneurin Price wrote:
My personal recommendation would be to use Shorewall
thanks, but usual story: i want to know what's goin
You said 'i am able to ping 172.21.5.136 but not 172.21.0.1'
from a client machine on the internal network.
and 'i can
connect fine to the internet from the gateway'.
So you can ping, say google.com from your gateway machine correctly?
yes.
But
you can't ping 172.21.0.1 from your gateway?
Aneurin Price wrote:
You shouldn't need to set a gateway in order to ping 172.21.0.1 because
you should have a direct connection to it. Your initial routing table
looks like it should work so I'd suspect another problem. That said, the
final line isn't right if you want to contact the outside wor
Ron Johnson wrote:
It needs to modify the Iface 172.21.0.1.
i'm not sure how. any pointers would be greatly appreciated.
Preferably when you actually create the link in wvdial.
my ISP uses DHCP so the local IP, gateway and DNSs are being assigned
automatically. i did the minimum of configurat
Your problem is that you aren't defining a gateway address.
i've tried "route add default gw 172.21.0.1 ppp0", after which the
routing table looks thus.
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
172.21.0.1 0.0.0.0 255.25
What does your current route table look like?
This is what the output of "netstat -rn" looks like upon startup.
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
i
need to add?
--
Regards,
Zanga Chimombo
IT Manager
ADMARC
PO Box 5052
Limbe
Malawi
Tel: 01 840 044/500
Fax: 01 840 486
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
7 matches
Mail list logo
