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
On 02/05/2009 02:15 AM, Zanga Chimombo wrote:
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
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
On 02/05/2009 07:07 AM, Zanga Chimombo wrote:
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
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
On Thu, Feb 5, 2009 at 1:37 PM, Zanga Chimombo z.chimo...@admarc.co.mw wrote:
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,
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
On Thu, Feb 5, 2009 at 2:02 PM, Zanga Chimombo z.chimo...@admarc.co.mw wrote:
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
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
On Thu, Feb 05, 2009 at 05:11:47PM +0200, Zanga Chimombo wrote:
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
On Thu, Feb 5, 2009 at 3:11 PM, Zanga Chimombo z.chimo...@admarc.co.mw wrote:
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
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
i've searched for this topic both online and in the archives but the
results all seem to have some slight but crucial difference with my
configuration. e.g. use of firewall
i'm setting up a gateway for use in one of our remote offices. it will
use a GPRS modem to connect to the outside world
On 02/05/2009 01:36 AM, Zanga Chimombo wrote:
i've searched for this topic both online and in the archives but the
results all seem to have some slight but crucial difference with my
configuration. e.g. use of firewall
i'm setting up a gateway for use in one of our remote offices. it will
14 matches
Mail list logo
