24 Apr
2017
24 Apr
'17
4:26 p.m.
Yes, that's very much a mystery, because my
tcpdump shows the route
being sent right after the one for 44.2.2.0/24.
[...]
AFI IPv4, 44.2.2.0/24, tag 0x0004, metric: 1, next-hop: 24.52.189.1
AFI IPv4, 44.0.0.1/32, tag 0x0004, metric: 1, next-hop: 169.228.66.251
Could there be some length or count field that is off by one?
I am tracing with wireshark (tshark). But ampr-ripd does not pick it up either.
Rob
24 Apr
24 Apr
4:53 p.m.
New subject: rip sender change
Programming errors are always a possibility. I'll check, but the
fact that the packet as seen on the outbound interface has the
entry in it lobbies against there being an error in the sender.
- Brian
On Mon, Apr 24, 2017 at 10:26:16PM +0200, Rob Janssen wrote:
Could there be some length or count field that is off
by one?
I am tracing with wireshark (tshark). But ampr-ripd does not pick it up either.
Rob
5 p.m.
New subject: rip sender change
I'm also seeing the last RIP packet ending in 44.2.2.0
There aren't any stray bytes following the last entry
73,
John G8BPQ
-----Original Message-----
From: 44Net [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu]
On Behalf Of Brian Kantor
Sent: 24 April 2017 21:54
To: AMPRNet working group
Subject: Re: [44net] rip sender change
(Please trim inclusions from previous messages)
_______________________________________________
Programming errors are always a possibility. I'll check, but the
fact that the packet as seen on the outbound interface has the
entry in it lobbies against there being an error in the sender.
- Brian
5:21 p.m.
New subject: rip sender change
Yes, there was an off-by-one error in the count of entries in
the last packet. This error was not present when we were sending
in gateway major order, but was there in packet-major-order which
change I made early today. It has been corrected. Please check
the next RIP update and see if that fixes things.
I think the tcpdump which I was referring to was made before the
ordering change. Oops.
- Brian
On Mon, Apr 24, 2017 at 10:00:44PM +0100, John Wiseman wrote:
I'm also seeing the last RIP packet ending in
44.2.2.0
There aren't any stray bytes following the last entry
73,
John G8BPQ
5:46 p.m.
New subject: rip sender change
Brian,
Yes, 44.0.0.1 is there again.
73,
John
-----Original Message-----
From: 44Net [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu]
On Behalf Of Brian Kantor
Sent: 24 April 2017 22:22
To: AMPRNet working group
Subject: Re: [44net] rip sender change
(Please trim inclusions from previous messages)
_______________________________________________
Yes, there was an off-by-one error in the count of entries in
the last packet. This error was not present when we were sending
in gateway major order, but was there in packet-major-order which
change I made early today. It has been corrected. Please check
the next RIP update and see if that fixes things.
I think the tcpdump which I was referring to was made before the
ordering change. Oops.
- Brian
2581
days inactive
2581
days old
4 comments
3 participants
participants (3)
-
Brian Kantor -
John Wiseman -
Rob Janssen