How to turn on IP forwarding?
Andy McKay
lonewolff at gmail.com
Thu Oct 7 20:59:34 UTC 2004
to list the routing table goto http://home/management and there is one
in there called static routes. should show you the routing table.
On Thu, 07 Oct 2004 13:36:48 -0700, Jonathan Ryshpan
<jonrysh at pacbell.net> wrote:
> On Thu, 2004-10-07 at 14:27, Jonathan Ryshpan wrote:
> I'm trying to make the machine amito forward packets from machine
> claremont to machine home. Claremont pings amito and amito pings home,
> but claremont doesn't ping home. All these machines are directly
> connected via ethernet claremont to amito on 192.168.10.x and amito to
> home on 172.16.0.x. I have IP forwarding turned on in amito:
>
> amito $ cat /proc/sys/net/ipv4/ip_forward
> 1
> claremont $ route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.10.0 * 255.255.255.0 U 0 0 0 eth0
> 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
> default amito.localdoma 0.0.0.0 UG 0 0 0 eth0
>
> claremont $ cat /etc/hosts
> 127.0.0.1 localhost.localdomain localhost
> 192.168.10.1 amito.localdomain amito
> 192.168.10.2 claremont.localdomain claremont
> 172.16.0.1 home home.localdomain
>
> What have I missed?
>
> =========================
>
> On Thu, 2004-10-07 at 00:13, Ow Mun Heng wrote:
> Can you tell us what is the routing table on claremont? since amito can
> ping home, it means there's connectivity.
>
> But since claremont cannot ping home, this could mean several things.
>
> 1. Firewall?
> 2. Wrong routing table.
>
> =========================
>
> On Thu, 2004-10-07 at 17:13, Jonathan Ryshpan wrote:
> The above routing table **is** the routing table in claremont.
> The firewall in amito is turned off.
>
> =========================
>
> On Thu, 2004-10-07 at 02:40, Ow Mun Heng wrote:
> Perhaps you can try to do a tcpdump/ethereal trace
>
> Here's a tcpdump of 20 packets of claremont trying to reach amito:
>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
> 11:17:06.637301 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 92
> 11:17:06.638579 IP amito.localdomain.32771 > homeportal.gateway.2wire.net.domain: 15570+ PTR? 1.0.16.172.in-addr.arpa. (41)
> 11:17:06.640011 IP homeportal.gateway.2wire.net.domain > amito.localdomain.32771: 15570*- 1/1/1 (187)
> 11:17:06.640598 IP amito.localdomain.32771 > homeportal.gateway.2wire.net.domain: 15571+ PTR? 33.1.16.172.in-addr.arpa. (42)
> 11:17:06.641985 IP homeportal.gateway.2wire.net.domain > amito.localdomain.32771: 15571*- 1/1/1 (179)
> 11:17:07.637109 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 93
> 11:17:08.636972 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 94
> 11:17:09.636823 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 95
> 11:17:10.636683 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 96
> 11:17:11.636533 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 97
> 11:17:12.636388 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 98
> 11:17:13.636235 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 99
> 11:17:14.636100 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 100
> 11:17:15.635952 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 101
> 11:17:16.635811 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 102
> 11:17:17.635663 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 103
> 11:17:18.635522 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 104
> 11:17:19.635381 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 105
> 11:17:20.635237 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 106
> 11:17:21.635082 IP claremont.localdomain > homeportal.gateway.2wire.net: icmp 64: echo request seq 107
> 20 packets captured
> 20 packets received by filter
> 0 packets dropped by kernel
>
> =========================
>
> On Thu, 2004-10-07 at 03:42, Stuart Sears wrote:
> What's the routing table like on amito? (route -n to show IPs)
> I take it that amito has two NICs? (ip addresses?)
>
> amito has two NICs: 192.168.10.1 attached to claremont and
> 172.16.1.33 attached to home
>
> amito $ route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
> 172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
> 0.0.0.0 172.16.0.1 0.0.0.0 UG 0 0 0 eth0
>
> While I'm at it, here's amito's host table:
>
> amito $ cat /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 localhost.localdomain localhost
> 192.168.10.1 amito.localdomain amito
> 192.168.10.2 claremont.localdomain claremont
>
> =========================
>
> On Thu, 2004-10-07 at 05:10, Scot L. Harris wrote:
> You should also look at the routing table on home. It has to know how
> to route the packets back to claremont via amito.
>
> Unfortunately, home is a 2Wire Model 100 Firewall/Masquerader. I don't know
> any way to list its routing table, though I'm sure it must have one.
>
> =========================
>
> Thanks - jon
>
>
>
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>
More information about the fedora-list
mailing list