Greetings list members;
While I still search for a true fix, a hack fix would be to create a tunl1 and route via that interface, however if you take tunl0 down, for some reason rip fails.
If anyone has a better solution or a true fix, please relay it. Thanks in advance...
Brian,
How about this library bug???
Tom - sp2lob
-----Oryginalna wiadomość----- From: Brian Rogers Sent: Monday, December 30, 2013 8:22 PM To: AMPRNet working group Subject: [44net] Hack fix for Pi
(Please trim inclusions from previous messages) _______________________________________________ Greetings list members;
While I still search for a true fix, a hack fix would be to create a tunl1 and route via that interface, however if you take tunl0 down, for some reason rip fails.
If anyone has a better solution or a true fix, please relay it. Thanks in advance...
On Mon, 2014-01-06 at 17:41 +0100, sp2lob@tlen.pl spake:
How about this library bug???
I haven't seen a true fix for it yet. The Pi force defaults tunl0 to MTU = 0 and you can't adjust ttl. It doesn't matter if you tear it all down the second you load the ipip module and ifconfig tunl0 or ip tunnel add, it force defaults MTU = 0 (auto sense) to which it expects fragmentation.
Hi,
I guess then that this means the RPi is useless for and AMPRnet GATEWAY using Rip.
Maybe ARM Slack or SlackArm for RPi is better than Wheezy distros?
There is a version based in Slackware 13.37 using kernel 2.6.37.6 and another one based in Slackware 14.0 using kernel 3.
73 de Demetre SV1UY
On Tue, Jan 7, 2014 at 2:34 PM, Brian Rogers n1uro@n1uro.ampr.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Mon, 2014-01-06 at 17:41 +0100, sp2lob@tlen.pl spake:
How about this library bug???
I haven't seen a true fix for it yet. The Pi force defaults tunl0 to MTU = 0 and you can't adjust ttl. It doesn't matter if you tear it all down the second you load the ipip module and ifconfig tunl0 or ip tunnel add, it force defaults MTU = 0 (auto sense) to which it expects fragmentation. -- 73 de Brian Rogers - N1URO email: n1uro@n1uro.ampr.org Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Demetre;
On Tue, 2014-01-07 at 15:40 +0200, Demetre SV1UY wrote:
I guess then that this means the RPi is useless for and AMPRnet GATEWAY using Rip.
This has nothing at all to do with rip, nor does it make the RPi useless for amprnet use. If that were true my direct link to you would have been gone a few weeks ago.
You could try my amprd instead of ripd + ipip driver... That one uses a tun/tap driver creating a virtual ethernet and does the cap/encap in user space. (not very well tested but works on my machine)
http://www.yo2loj.ro/hamprojects/amprd-1.4.tgz
73s de 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 Brian Rogers Sent: Tuesday, January 07, 2014 15:48 To: Demetre SV1UY Cc: AMPRNet working group Subject: Re: [44net] Hack fix for Pi
(Please trim inclusions from previous messages) _______________________________________________ Demetre;
On Tue, 2014-01-07 at 15:40 +0200, Demetre SV1UY wrote:
I guess then that this means the RPi is useless for and AMPRnet GATEWAY using Rip.
This has nothing at all to do with rip, nor does it make the RPi useless for amprnet use. If that were true my direct link to you would have been gone a few weeks ago.
-- 73 de Brian Rogers - N1URO email: n1uro@n1uro.ampr.org Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Anyone know of a list of routers that pass ripv2? A ham in EU is trying to set up ripv2 with our help but ripv2 gateway announcements don't seem to be coming through the router...yes, the pi is in the DMZ, hi hi! He's on virginmedia, any issues with their modems known?
Another issue I'm having (AX25/netrom) is that we have to type a fake "-0" when connecting to a callsign with no ssid...why is this behavior the default? Any way to stop this and revert to just the callsign with no ssid? Users have no way of knowing that they have to add a -0, and so cannot connect to any station unless it specifies an ssid..thus, thinking the station is not available, we lose the user...there's not a TNC that I know of that does this, but linux ax25(and netrom) sees fit that this should be the standard?
Are you talking the usual RIP within an IPIP encapsulated packet, as used by rip44d?
If so, I have Virgin Media Internet and a WRT54G running DD-WRT, and have rip44d running fine on a PI. I had to add some custom iptables rules to the router to forward IPIP, but the PI doesn't have to be in a DMZ.
73, John G8BPQ
-----Original Message----- From: 44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu] On Behalf Of ve1jot Sent: 08 January 2014 08:43 To: 44net@hamradio.ucsd.edu Subject: Re: [44net] known good routers that pass rip/44-net friendly in uk?
_______________________________________________ Anyone know of a list of routers that pass ripv2? A ham in EU is trying to set up ripv2 with our help but ripv2 gateway announcements don't seem to be coming through the router...yes, the pi is in the DMZ, hi hi! He's on virginmedia, any issues with their modems known?
://hamradio.ucsd.edu/mailman/listinfo/44net
Mikrotik routers work nicely regarding protocol 4 forwarding.
73s de Marius
Anything you can get OpenWRT installed on will work fine.
Jerry, KD4YAL
---- Marius Petrescu marius@yo2loj.ro wrote:
(Please trim inclusions from previous messages) _______________________________________________ Mikrotik routers work nicely regarding protocol 4 forwarding.
73s de Marius
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
The -0 SSID could be coming from the "official AX.25" repository but the problem code isn't in the released source tarballs. You might try reverting to the older published version of code or maybe use VE7FET's version of the AX.25 code which has a lot of fixes, etc. that the "official" AX.25 repo still doesn't have:
http://code.google.com/p/linuxax25/
ARM binaries *are* available. This alternative code repository was originally maintained by F6BVP of FBB BBS fame as he had issues with some of the accepted patches (like this -0 SSID issue).
--David KI6ZHD
Another issue I'm having (AX25/netrom) is that we have to type a fake "-0" when connecting to a callsign with no ssid...why is this behavior the default? Any way to stop this and revert to just the callsign with no ssid? Users have no way of knowing that they have to add a -0, and so cannot connect to any station unless it specifies an ssid..thus, thinking the station is not available, we lose the user...there's not a TNC that I know of that does this, but linux ax25(and netrom) sees fit that this should be the standard?
I use the VE7FET's version because of the fixes in there.
The "ax25 node" package isn't included so you have to download the source and recompile it as the compiled node package from the distros (Ubuntu, ..) doesn't work with VE7FET's code.
B
On 14-01-08 11:41 AM, David Ranch wrote:
(Please trim inclusions from previous messages) _______________________________________________
The -0 SSID could be coming from the "official AX.25" repository but the problem code isn't in the released source tarballs. You might try reverting to the older published version of code or maybe use VE7FET's version of the AX.25 code which has a lot of fixes, etc. that the "official" AX.25 repo still doesn't have:
http://code.google.com/p/linuxax25/
ARM binaries *are* available. This alternative code repository was originally maintained by F6BVP of FBB BBS fame as he had issues with some of the accepted patches (like this -0 SSID issue).
--David KI6ZHD
Btw, I can confirm that the current UroNode code works well with the VE7FET AX.25 toolkit too.
--David KI6ZHD
On 01/08/2014 02:15 PM, Bob Tenty wrote:
(Please trim inclusions from previous messages) _______________________________________________ I use the VE7FET's version because of the fixes in there.
The "ax25 node" package isn't included so you have to download the source and recompile it as the compiled node package from the distros (Ubuntu, ..) doesn't work with VE7FET's code.
B
On 14-01-08 11:41 AM, David Ranch wrote:
(Please trim inclusions from previous messages) _______________________________________________
The -0 SSID could be coming from the "official AX.25" repository but the problem code isn't in the released source tarballs. You might try reverting to the older published version of code or maybe use VE7FET's version of the AX.25 code which has a lot of fixes, etc. that the "official" AX.25 repo still doesn't have:
http://code.google.com/p/linuxax25/ARM binaries *are* available. This alternative code repository was originally maintained by F6BVP of FBB BBS fame as he had issues with some of the accepted patches (like this -0 SSID issue).
--David KI6ZHD
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On 14-01-08 08:00 PM, David Ranch wrote:
(Please trim inclusions from previous messages) _______________________________________________
Btw, I can confirm that the current UroNode code works well with the VE7FET AX.25 toolkit too.
ahh, that's good to know...I run uronode.... thank you all, very good input!
-
Bob Tenty -
Brian Rogers -
David Ranch -
Demetre SV1UY -
Jerald A DeLong -
John Wiseman -
Marius Petrescu -
sp2lob＠tlen.pl -
ve1jot