Hi All,
Does any one know if there is a problem with UDP port 520 and rip44d, I am monitoring it but I see no data arriving here at all.
Have tested from an outside source and the port is receiving all ok.
Comments ?
Hi Peter,
All seems up and running, broadcasts arrive as they should. Ping to your ham gw (44.147.210.26) and access to your node (BAUNODE) is ok.
Could you detail more what/how you monitor?
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 Peter - ZL2BAU Sent: Sunday, May 04, 2014 11:26 To: AMPRNet working group Subject: [44net] rip44d
(Please trim inclusions from previous messages) _______________________________________________
Hi All,
Does any one know if there is a problem with UDP port 520 and rip44d, I am monitoring it but I see no data arriving here at all.
............... -- Regards ..... Peter ZL2BAU
On 04/05/14 21:23, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hi Peter,
All seems up and running, broadcasts arrive as they should. Ping to your ham gw (44.147.210.26) and access to your node (BAUNODE) is ok.
Could you detail more what/how you monitor?
Marius, YO2LOJ
Hi Marius,
All was working well until I changed the system for bridged routers, one to connect to the ISP and the other running dd-wrt ahead of the linux box.
I start rip with *./rip44d -s -p passwd &* (Password is the correct one used)
And I monitor with *tcpdump -i eth0 -f port 520*
This was working perfect so I am unsure at this stage if it`s a config problem with the two routers altho as I said, 5 UDP port 520 frames were sent from another ISP and they were received 100 percent.
Maybe I need more coffee, Hi
Hello Peter,
Pinged 44.147.210.26 and telnetted successfully Xrouter as well.
Best regards. Tom - sp2lob
Hi Peter,
You should monitor your tunnel interface for the rip packets, not your ethernet iterface: "tcpdump -i tunl0 -f port 520"
The RIP broadcasts are sent IPIP encapsulated and emerge only on your tunnel interface.
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 Peter - ZL2BAU Sent: Sunday, May 04, 2014 12:54 To: AMPRNet working group Subject: Re: [44net] rip44d
I start rip with *./rip44d -s -p passwd &* (Password is the correct one used)
And I monitor with *tcpdump -i eth0 -f port 520*
On 05/05/14 01:32, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hi Peter,
You should monitor your tunnel interface for the rip packets, not your ethernet iterface: "tcpdump -i tunl0 -f port 520"
The RIP broadcasts are sent IPIP encapsulated and emerge only on your tunnel interface.
Marius, YO2LOJ
Hi Marius,
Thank you for that, I found the problem, well it`s not actually a problem but something I was unaware of, I am using DD-WRT V24 *Standard* which does not support "tcpdump" thus it never worked when I ssh`ed to the router.
I tested on the Linux box and it worked thus my confusion.
When I originally tested this, I was using a different router with DD-WRT V24 *Mega* installed which does support "tcpdump"
Thank again for your suggestion.
-
Marius Petrescu -
Peter - ZL2BAU -
sp2lob