Network watchdog has expired....

General support for the Pi-Star System
Post Reply
VA3UV
Posts: 17
Joined: Tue Apr 09, 2019 5:02 pm

Network watchdog has expired....

Post by VA3UV » Sat May 25, 2019 2:09 am

Hi All:

I replaced the last of my legacy systems with a Pi-Star install earlier today. All has been working pretty well until a few moments ago, during our weekly Net.

Symptom - I am only seeing / hearing a quick transmission showing the header of the remote station, but no audio.

This is what I am seeing in the ircddbgateway log file:

M: 2019-05-25 02:01:09: Network header received - My: VE7GGK /5100 Your: CQCQCQ Rpt1: VA3PMO G Rpt2: VA3PMO B Flags: 00 00 00
M: 2019-05-25 02:01:09: Transmitting to - My: VE7GGK /5100 Your: CQCQCQ Rpt1: VA3PMO G Rpt2: VA3PMO B Flags: 00 00 00
M: 2019-05-25 02:01:11: Network watchdog has expired
M: 2019-05-25 02:01:11: Stats for VE7GGK Frames: 1.8s, Loss: 100.0%, Packets: 92/92
M: 2019-05-25 02:01:24: Network header received - My: VA3WM /7100 Your: CQCQCQ Rpt1: VA3PMO G Rpt2: VA3PMO B Flags: 00 00 00
M: 2019-05-25 02:01:24: Transmitting to - My: VA3WM /7100 Your: CQCQCQ Rpt1: VA3PMO G Rpt2: VA3PMO B Flags: 00 00 00
M: 2019-05-25 02:01:26: Network watchdog has expired
M: 2019-05-25 02:01:26: Stats for VA3WM Frames: 1.8s, Loss: 100.0%, Packets: 92/92


Ideas?

Thanks,

Ramesh.
VA3UV, WA3UV, G4PNQ

VA3UV
Posts: 17
Joined: Tue Apr 09, 2019 5:02 pm

Re: Network watchdog has expired....

Post by VA3UV » Sat May 25, 2019 2:41 pm

Some additional info...

On this particular system (and it is only happening on this system!)... the dashboard shows BOTH an outgoing connection to say REF001 C (dplus) AND also an incoming dplus connection to VA3UV.

When I transmit, I am not seeing my activity on the REF001 C dashboard.... so I am wondering whether the outgoing packets are being reflected back at itself???

Ramesh.
VA3UV, WA3UV, G4PNQ

VA3UV
Posts: 17
Joined: Tue Apr 09, 2019 5:02 pm

Re: Network watchdog has expired....

Post by VA3UV » Sat May 25, 2019 7:35 pm

More info!

This is a Pi 3 B+ (running Pi-Star:4.0.0-RC3). I am led to believe that this problem, may be peculiar to this RC3 candidate)? - is there a solution?

All of my other installs have been on Pi 2 and even a Pi 1.

Ramesh.

VA3UV
Posts: 17
Joined: Tue Apr 09, 2019 5:02 pm

Re: Network watchdog has expired....

Post by VA3UV » Mon May 27, 2019 3:04 pm

More info!!

Ran some basic network tests to confirm network connectivity / firewall settings:

[email protected](ro):pi-star# nc -vz -u 127.0.0.1 40000
Connection to 127.0.0.1 40000 port [udp/*] succeeded!

[email protected](ro):pi-star# nc -vz -u ve3uru-dstar.homelinux.net 40000
Connection to ve3uru-dstar.homelinux.net 40000 port [udp/*] succeeded!

[email protected](ro):pi-star# nc -vz -u xrf021.va3uv.com 30001
Connection to xrf021.va3uv.com 30001 port [udp/*] succeeded!

[email protected](ro):pi-star# nc -vz -u ve3uru-dstar.homelinux.net 40000
Connection to ve3uru-dstar.homelinux.net 40000 port [udp/*] succeeded!

[email protected](ro):pi-star# nc -vz -u ve3uru-dstar.homelinux.net 20001
Connection to ve3uru-dstar.homelinux.net 20001 port [udp/*] succeeded!

[email protected](ro):pi-star# nc -vz -u ve3uru-dstar.homelinux.net 20015 <== Just to confirm that a port that is closed does not allow a connection

[email protected](ro):pi-star# nc -vz -u ve3uru-dstar.homelinux.net 20007
Connection to ve3uru-dstar.homelinux.net 20007 port [udp/*] succeeded!

[email protected](ro):pi-star# nc -vz -u xlx416.va3uv.com 30001
Connection to xlx416.va3uv.com 30001 port [udp/*] succeeded!



Using tcpdump to monitor udp traffic on port 20001, I see a lot of traffic (example snippet below), which confirms that the firewall is allowing traffic in and out....

10:54:52.864965 IP (tos 0x0, ttl 61, id 4062, offset 0, flags [DF], proto UDP (17), length 57)
ssvlon5203w-lp140-01-64-231-96-66.dsl.bell.ca.20001 > va3pmo.20002: [udp sum ok] UDP, length 29
0x0000: 4500 0039 0fde 4000 3d11 caa0 40e7 6042 [email protected][email protected]`B
0x0010: c0a8 0164 4e21 4e22 0025 ec0f 1d80 4453 ...dN!N".%....DS
0x0020: 5654 2000 0000 2000 0000 a2a8 039e 8d32 VT.............2
0x0030: 8826 1a3f 61e8 312b b3 .&.?a.1+.
10:54:52.885099 IP (tos 0x0, ttl 64, id 4063, offset 0, flags [DF], proto UDP (17), length 57)
va3pmo.20001 > unallocated-static.rogers.com.2464: [bad udp cksum 0xbdd6 -> 0x0233!] UDP, length 29
0x0000: 4500 0039 0fdf 4000 4011 6d35 c0a8 0164 [email protected]@.m5...d
0x0010: 4889 b30a 4e21 09a0 0025 bdd6 1d80 4453 H...N!...%....DS
0x0020: 5654 2000 0000 2000 0000 a2a8 049e 8d32 VT.............2
0x0030: 8826 1a3f 61e8 0420 b3 .&.?a....
10:54:52.885790 IP (tos 0x0, ttl 61, id 4063, offset 0, flags [DF], proto UDP (17), length 57)
ssvlon5203w-lp140-01-64-231-96-66.dsl.bell.ca.20001 > va3pmo.20002: [udp sum ok] UDP, length 29
0x0000: 4500 0039 0fdf 4000 3d11 ca9f 40e7 6042 [email protected][email protected]`B
0x0010: c0a8 0164 4e21 4e22 0025 181b 1d80 4453 ...dN!N".%....DS
0x0020: 5654 2000 0000 2000 0000 a2a8 049e 8d32 VT.............2
0x0030: 8826 1a3f 61e8 0420 b3 .&.?a....
10:54:52.905883 IP (tos 0x0, ttl 64, id 4064, offset 0, flags [DF], proto UDP (17), length 57)
va3pmo.20001 > unallocated-static.rogers.com.2464: [bad udp cksum 0xbdd6 -> 0xc53b!] UDP, length 29
0x0000: 4500 0039 0fe0 4000 4011 6d34 c0a8 0164 [email protected]@.m4...d
0x0010: 4889 b30a 4e21 09a0 0025 bdd6 1d80 4453 H...N!...%....DS
0x0020: 5654 2000 0000 2000 0000 a2a8 059e 8d32 VT.............2
0x0030: 8826 1a3f 61e8 3217 c1 .&.?a.2..


Yet the dashboard for VA3PMO continues to show both an outbound connection to XRF416D *AND* an inbound connection from VA3PMO.

The dashboard on XLX416 does not show a connection from VA3PMO.

Am I the only one having this issue????

Ramesh.
VA3UV, WA3UV, G4PNQ

Post Reply