Gateway matters...routing matters!

Gateway matters...routing matters!

[IZ4EFN Alessio]

Hi all,

I'm currently trying to setup a gateway to the 44 network for my local 
wi-fi users.

I've been following some advices offered by local gateway owner and 
linuxham how to as well.

Now:

I'm able to load the module ipip.

I'm able to load the tunl0 interface for tunneling: ifconfig tunl0 
44.134.130.1 mtu 576 up

I'm able to set the default route to USCD.EDU: ip route add 44.0.0.0/8 
via 128.54.16.18 dev tunl0 onlink

and the routing table says:

root@arimodena:/etc# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
localnet        *               255.255.255.0   U     0      0        0 eth0
loopback        *               255.0.0.0       U     0      0        0 lo
44.0.0.0        mirrorshades.uc 255.0.0.0       UG    0      0        0 
tunl0
default         192.168.0.1     0.0.0.0         UG    1      0        0 eth0
root@arimodena:/etc#



Now I should load from a file all the routes, but let's try manually 
with one single routes!

I wanna add the 44.134.8.0/24 network to be routed through 134.43.26.1 
via the tunl0 device:

root@arimodena:/etc# route add -net 44.134.8.0 netmask 255.255.255.0 dev 
tunl0 gw 134.43.26.1
SIOCADDRT: Network is unreachable
root@arimodena:/etc#

The SIOCADDRT error is clear, but I don't understand why this happends.

Maybe I forgot something before setting the roules?

Any help is really appreciated!

(I know I should ask this on the Gateways ML on cows.net but its server 
looks down...)

Thanks!!

Alessio IZ4EFN.

RE: Gateway matters...routing matters!

[Stewart Wilkinson]

> I'm able to set the default route to USCD.EDU: ip route add 44.0.0.0/8 
> via 128.54.16.18 dev tunl0 onlink

> root@arimodena:/etc# route add -net 44.134.8.0 netmask 255.255.255.0 dev 
> tunl0 gw 134.43.26.1
> SIOCADDRT: Network is unreachable
> root@arimodena:/etc#

I think you need:

	ip route add 44.134.8.0/24 via 134.43.26.1 dev tunl0 onkink

--
Stewart G0LGS

Re: Gateway matters...routing matters!

[IZ4EFN Alessio]

>I think you need:
>
>	ip route add 44.134.8.0/24 via 134.43.26.1 dev tunl0 onkink
>
>--
>Stewart 
>
Thanks Stewart!!

I'm OK now!

I tryed with some known routes and hosts, everything worked fine with 
the routing table:

root@arimodena:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
ir3ip.ampr.org  ppp-217-133-38- 255.255.255.255 UGH   0      0        0 
tunl0
44.134.8.0      134.43.26.1     255.255.255.0   UG    0      0        0 
tunl0
localnet        *               255.255.255.0   U     0      0        0 eth0
44.134.144.0    213.254.10.100  255.255.252.0   UG    0      0        0 
tunl0
44.134.128.0    213.254.10.100  255.255.240.0   UG    0      0        0 
tunl0
loopback        *               255.0.0.0       U     0      0        0 lo
default         192.168.0.1     0.0.0.0         UG    1      0        0 eth0
root@arimodena:~#


but i'm not able to use the gateway to ping a known host behind the 
network routed.

ip_forward IS configured (echo 1 > /proc/sys/net/ipv4/ip_forward).

I'm wondering if my router is blocking Protocol 94 (it's a Cisco SOHO 
97, and the gateway machine as all ports opened on its pubblic IP).

Or other mistakes are stopping the connection?

I just noticed (with netwatch) that i send packets to the rigth gateway 
(on the iNET address) while pinging, but nothing comes back. RX packets 
are 0.
That's why I'm wondering about the router...even if all ports are 
opened...Protocol 94 matter?

Thanks!

Alessio IZ4EFN.