All of lore.kernel.org
 help / color / mirror / Atom feed
From: IZ4EFN Alessio <iz4efn@libero.it>
To: linux-hams@vger.kernel.org
Subject: Gateway matters...routing matters!
Date: Sat, 16 Jul 2005 23:00:56 +0200	[thread overview]
Message-ID: <42D97588.3050509@libero.it> (raw)

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.





             reply	other threads:[~2005-07-16 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-16 21:00 IZ4EFN Alessio [this message]
2005-07-16 21:53 ` Gateway matters...routing matters! Stewart Wilkinson
2005-07-16 22:21   ` IZ4EFN Alessio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42D97588.3050509@libero.it \
    --to=iz4efn@libero.it \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.