By default rip44d is using the interface tunl0, it seems: my $tunnel_if = 'tunl0'; You seem to be using tun0 in your networking scripts, so i suppose you either need to adjust the default, use the -i option to change the interface used by rip44d, or change the tunnel interface name to match so the rip44d is listening on the right interface.
Pieter. Sent from a mobile, sorry for any typoes...
This is probably the right answer - tun0 is, by default, a completely different type of an interface than tunl0 (IPIP tunnel)!
tun0 would be a virtual interface used to pass IP packets between the Linux kernel and an userspace program, such as openvpn (http://en.wikipedia.org/wiki/TUN/TAP).
tunl0 is an IPIP tunnel interface which we want to use here. So, you should adjust the network interace setup to use tunl0. Just set it up with your net-44 address, no need to adjust modes or local addresses in a "normal" setup.
On Sun, Jul 28, 2013 at 6:45 AM, Pieter Luteijn luteijn@xs4all.nl wrote:
(Please trim inclusions from previous messages) _______________________________________________ By default rip44d is using the interface tunl0, it seems: my $tunnel_if = 'tunl0'; You seem to be using tun0 in your networking scripts, so i suppose you either need to adjust the default, use the -i option to change the interface used by rip44d, or change the tunnel interface name to match so the rip44d is listening on the right interface.
Pieter. Sent from a mobile, sorry for any typoes...
ubuntu won't let me create an interface called tunl0. There is one created automatically when I create tun0.
nmjoo@earth:~$ sudo ip tunnel [sudo] password for nmjoo: tun0: ip/ip remote any local 128.255.134.47 ttl inherit tunl0: ip/ip remote any local any ttl inherit nopmtudisc nmjoo@earth:~$
I'm new at ubuntu (I come from a Fedora background, but I wanted to run a distribution that doesn't go out of date every 18 months).
-Neil
On Mon, Jul 29, 2013 at 5:41 AM, Heikki Hannikainen hessu@hes.iki.fiwrote:
(Please trim inclusions from previous messages) _______________________________________________ This is probably the right answer - tun0 is, by default, a completely different type of an interface than tunl0 (IPIP tunnel)!
tun0 would be a virtual interface used to pass IP packets between the Linux kernel and an userspace program, such as openvpn (http://en.wikipedia.org/wiki/TUN/TAP).
tunl0 is an IPIP tunnel interface which we want to use here. So, you should adjust the network interace setup to use tunl0. Just set it up with your net-44 address, no need to adjust modes or local addresses in a "normal" setup.
On Sun, Jul 28, 2013 at 6:45 AM, Pieter Luteijn luteijn@xs4all.nl wrote:
(Please trim inclusions from previous messages) _______________________________________________ By default rip44d is using the interface tunl0, it seems: my $tunnel_if = 'tunl0'; You seem to be using tun0 in your networking scripts, so i suppose you
either need to adjust the default, use the -i option to change the interface used by rip44d, or change the tunnel interface name to match so the rip44d is listening on the right interface.
Pieter. Sent from a mobile, sorry for any typoes...
Hi Neil,
Try: ip tun add ampr0 mode ipip local 128.255.134.47
I prefer the name ampr0 not to confuse it with tun0. But of course you can use tunl0 if you like.
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Neil Johnson Sent: Monday, July 29, 2013 17:36 To: AMPRNet working group Subject: Re: [44net] Tunnel issues with rip44d
nmjoo@earth:~$ sudo ip tunnel [sudo] password for nmjoo: tun0: ip/ip remote any local 128.255.134.47 ttl inherit tunl0: ip/ip remote any local any ttl inherit nopmtudisc nmjoo@earth:~$
Neil et al;
On Mon, 2013-07-29 at 09:36 -0500, Neil Johnson spake:
ubuntu won't let me create an interface called tunl0. There is one created automatically when I create tun0.
You can use the suggestion from Marius or you can simply do: ifconfig tunl0 <ip> netmask <mask> up
I too however on Ubuntu have issues using rip44d. I see the rip frames come in, and the script is configured to do it's thing, but it refuses to write the routes. The path to IP is in the script properly.
I've used it on other systems with great success, only my own (Mr. Murphy striking again!) do I have issues with rip44d.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
ifconfig tunl0 up 44.111.222.333 netmask 255.255.255.255
works fine for me. (I'm using an illegal IP for those who copy-paste straight into their console. :-D )
As it has been stated you *must* *not* set local and remote address for the tunnel interface.
73 de Marc, LX1DUC
On 29/07/2013 16:36, Neil Johnson wrote:
(Please trim inclusions from previous messages) _______________________________________________ ubuntu won't let me create an interface called tunl0. There is one created automatically when I create tun0.
nmjoo@earth:~$ sudo ip tunnel [sudo] password for nmjoo: tun0: ip/ip remote any local 128.255.134.47 ttl inherit tunl0: ip/ip remote any local any ttl inherit nopmtudisc nmjoo@earth:~$
I'm new at ubuntu (I come from a Fedora background, but I wanted to run a distribution that doesn't go out of date every 18 months).
-Neil
On Mon, Jul 29, 2013 at 5:41 AM, Heikki Hannikainen hessu@hes.iki.fiwrote:
(Please trim inclusions from previous messages) _______________________________________________ This is probably the right answer - tun0 is, by default, a completely different type of an interface than tunl0 (IPIP tunnel)!
tun0 would be a virtual interface used to pass IP packets between the Linux kernel and an userspace program, such as openvpn (http://en.wikipedia.org/wiki/TUN/TAP).
tunl0 is an IPIP tunnel interface which we want to use here. So, you should adjust the network interace setup to use tunl0. Just set it up with your net-44 address, no need to adjust modes or local addresses in a "normal" setup.
On Sun, Jul 28, 2013 at 6:45 AM, Pieter Luteijn luteijn@xs4all.nl wrote:
(Please trim inclusions from previous messages) _______________________________________________ By default rip44d is using the interface tunl0, it seems: my $tunnel_if = 'tunl0'; You seem to be using tun0 in your networking scripts, so i suppose you
either need to adjust the default, use the -i option to change the interface used by rip44d, or change the tunnel interface name to match so the rip44d is listening on the right interface.
Pieter. Sent from a mobile, sorry for any typoes... -------------- next part -------------- An HTML attachment was scrubbed... URL: <
http://hamradio.ucsd.edu/mailman/private/44net/attachments/20130728/8385e52b...
_________________________________________
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
Hello,
I created a first version of a C port of the router daemon, with the resulting small memory footprint... You can get it for testing from my homepage: www.yo2loj.ro under "Ham Projects" or via direct link http://www.yo2loj.ro/hamprojects/ampr-ripd-1.0.tgz
News and issues: - For the moment TCP windows size is not set and the routng table can not be selected (main table is used). - Routes are marked with protocol 44 for better visibility and management. - Routes are saved to a file under /var/lib/ampr-ripd in encap format, 30 sec after receiving a route change in the broadcast data - This file is loaded at startup and routes set accordingly.
Any feedback is welcome.
Have fun, Marius, YO2LOJ
On 13-07-31 07:46 PM, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello,
I created a first version of a C port of the router daemon, with the resulting small memory footprint... You can get it for testing from my homepage: www.yo2loj.ro under "Ham Projects" or via direct link http://www.yo2loj.ro/hamprojects/ampr-ripd-1.0.tgz
News and issues:
- For the moment TCP windows size is not set and the routng table can not be
selected (main table is used).
- Routes are marked with protocol 44 for better visibility and management.
- Routes are saved to a file under /var/lib/ampr-ripd in encap format, 30
sec after receiving a route change in the broadcast data
- This file is loaded at startup and routes set accordingly.
Any feedback is welcome.
Have fun, Marius, YO2LOJ
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
downloaded, compiled fine mint13...running it now...no probs so far...thanks Marius
Just a small update to have 2 versions on the same day :-)
I added setting of TCP window size 840 and routing table selection (by name or number) to the daemon. Soooo... version 1.1 is available on www.yo2loj.ro under 'Ham Projects' or directly under http://www.yo2loj.ro/hamprojects/ampr-ripd-1.1.tgz So it is fully functional (I hope).
Again, have fun, Marius, YO2LOJ
Hello YLs and OMs.
I added an option to use raw sockets instead of multicast to the daemon. This is needed on systems that do not support multicast properly. On system where it works, there is no need to upgrade.
Version 1.2 is available on www.yo2loj.ro under 'Ham Projects' or directly under http://www.yo2loj.ro/hamprojects/ampr-ripd-1.2.tgz
Have fun, Marius, YO2LOJ
On Sat, 2013-08-03 at 11:46 +0300, Marius Petrescu spake:
Hello YLs and OMs.
I definately fit into the latter!
I added an option to use raw sockets instead of multicast to the daemon. This is needed on systems that do not support multicast properly. On system where it works, there is no need to upgrade.
Thank you Marius - it's definately now doing what it needs to do! Good job! With my 10 yr old system running a P-III I'm lucky to have a circa 2009 setup running. I don't know why on earth though this 2.6 kernel doesn't support multicast.
-
Brian Rogers -
Brian Rogers -
Heikki Hannikainen -
JJ -
Marc, LX1DUC -
Marius Petrescu -
Neil Johnson -
Pieter Luteijn