same prob again...cannot ping 184.108.40.206
Sietse van Zanen
sietse at wizdom.nu
Wed Jun 21 11:25:42 CEST 2006
Like I said before, the best thing you can do is start reading up on TCP/IP and routing.
This would be some good places to start:
What you are trying to do is the very basics of setting up a couple of routed subnets/vlans. And unless you educate yourself, you will never fix your problem, as you haven't got the slightest clue of what you are doing.
Also for routing, you do not need iptables. Trying to NAT what you can actually just route only makes things more complicated and not easier. First get your routing set up correctly, then start with firewalling.
From: netfilter-bounces at lists.netfilter.org on behalf of Diana Asnani
Sent: Wed 21-Jun-06 9:03
To: netfilter at lists.netfilter.org
Subject: same prob again...cannot ping 220.127.116.11
this time is about iptables...previously, i posted about routing issues and
i got quite a lot of response on that...
ok, i still could not ping 18.104.22.168 from my IP, 192.168.202.1...i could
not add this "route add -net 22.214.171.124/24 gw 192.168.202.1" in my routing
table because my default gateway is set as 192.168.202.14 in the vlan
configuration....and yes ipv4 forwarding is enabled in /etc/sysctl.conf...I
could always ping 192.168.206.1 because we are in the same vlan...but with
my gateway as 192.168.202.14 because its connected to the
vlan...192.168.206.1 is in the same PC with 126.96.36.199...
the PC router 188.8.131.52/192.168.206.1 ( the PC router ) did NAT and
added this in the iptables:
iptables -t nat -A POSTROUTING -o eth1 -j SNAT --to 184.108.40.206
is there anything else that i should do to make the PC 192.168.202.1 to
ping 220.127.116.11?? I'm really devastated with this problem...hope you guys
Get your mobile ringtones, operator logos and picture messages from MSN
More information about the netfilter