1 Sep
2013
1 Sep
'13
3:27 p.m.
Subject:
[44net] ripv2
From:
Brian Rogers <n1uro(a)n1uro.ampr.org>
Date:
09/01/2013 12:12 AM
To:
AMPRNet working group <44net(a)hamradio.ucsd.edu>
There appears to be at least one valid route missing in the rip
broadcasts. aa6hf is not received via rip however it is using the munge
script... is there an issue in the portal?
I receive the routes from RIP and his
route is OK.
44.17.0.128/31 via 67.49.91.65 dev tunl0 proto ampr-ripd onlink
1 Sep
1 Sep
3:35 p.m.
New subject: ripv2
Hello Rob
I receive the routes from RIP and his route is OK.
44.17.0.128/31 via 67.49.91.65 dev tunl0 proto ampr-ripd onlink
It's coming through today after I informed the sysop his block was being
omitted. I think he re-entered his block in the portal, but i'm not
positive. I know on two systems I help out on his block was not coming
through via rip.
--
73 de Brian Rogers - N1URO
email: <n1uro(a)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,
Massachusetts, New Hampshire,
Pennsylvania, Rhode Island,
and Vermont.
3:53 p.m.
New subject: ripv2
When you first mentioned it yesterday I checked the encap.txt file and his
address was there. Maybe the rip process hiccuped?
73, Don - ve3zda
On Sun, Sep 1, 2013 at 3:35 PM, Brian Rogers <n1uro(a)n1uro.ampr.org> wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> Hello Rob
> > I receive the routes from RIP and his route is OK.
> >
> > 44.17.0.128/31 via 67.49.91.65 dev tunl0 proto ampr-ripd onlink
>
> It's coming through today after I informed the sysop his block was being
> omitted. I think he re-entered his block in the portal, but i'm not
> positive. I know on two systems I help out on his block was not coming
> through via rip.
> --
> 73 de Brian Rogers - N1URO
> email: <n1uro(a)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,
> Massachusetts, New Hampshire,
> Pennsylvania, Rhode Island,
> and Vermont.
>
11:40 p.m.
New subject: another ripv2
I find these interesting:
via munge script (which is correct):
ip ro get 44.165.2.3
44.165.2.3 via 87.251.250.110 dev tunl0
via RipV2:
ip ro get 44.165.2.3
44.165.2.3 via 169.228.66.251 dev tunl0
<$0.02>
I don't by all means fault the rip daemons, I get the same result via
rip using either the perl script from Hessu as I do the c code from
Marius. They seem to work exactly as they should, however for so many
emails about switching to bgp/ospf/etc, we should be TOTALLY EMBARASSED
that we're dropping routes from a simple rip table as we are.
</$0.02>
--
73 de Brian Rogers - N1URO
email: <n1uro(a)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,
Massachusetts, New Hampshire,
Pennsylvania, Rhode Island,
and Vermont.
2 Sep
2 Sep
1:20 a.m.
New subject: another ripv2
This is strange...
On my system running the C version:
ip ro get 44.165.2.3
44.165.2.3 via 87.251.250.110 dev ampr0 src 44.182.21.1
cache mtu 1480 window 840 advmss 1440 hoplimit 64
And there is an entry for 44.165.2/29 via 87.251.250.110 in the rip
broadcast...
So the info is clearly there...
Marius, YO2LOJ
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Brian
Rogers
Sent: Monday, September 02, 2013 06:40
To: AMPRNet working group
Subject: [44net] another ripv2
(Please trim inclusions from previous messages)
_______________________________________________
I find these interesting:
via munge script (which is correct):
ip ro get 44.165.2.3
44.165.2.3 via 87.251.250.110 dev tunl0
via RipV2:
ip ro get 44.165.2.3
44.165.2.3 via 169.228.66.251 dev tunl0
3:43 a.m.
New subject: another ripv2
On Sun, Sep 01, 2013 at 11:40:16PM -0400, Brian Rogers wrote:
via munge script (which is correct):
ip ro get 44.165.2.3
44.165.2.3 via 87.251.250.110 dev tunl0
This is the same as the rip44 sender is saying:
AFI: IPv4: 44.165.2.0/29, tag 0x0004, metric: 1, next-hop: 87.251.250.110
so I have no idea where this route is coming from:
via RipV2:
ip ro get 44.165.2.3
44.165.2.3 via 169.228.66.251 dev tunl0
- Brian
3911
days inactive
3912
days old
5 comments
5 participants
participants (5)
-
Brian Kantor -
Brian Rogers -
Don Moore -
Marius Petrescu -
Rob Janssen