Re: [44net] SOLVED - Gateways Unreachable after Dynamic IP Update

@Lynwood: RIP44, is a UDP communication, using src and dest port 520, multicast address 224.0.0.9 as destination and source is 44.0.0.1. Before receiving these broadcasts the user have to join a multicast group and enable multicast on the receiving interface. This is why you need a route to 44.0.0.1 on the tunnel interface, so that the group subscribe message gets sent to 44.0.0.1. Feel fre to use a network sniffer like wireshark and see for yourself. @Brian: If it works, lets try not to fix this. 44.0.0.1 doesn't respond to ping via tunnel. I think we can live with this :-) 73's de 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 lleachii(a)aol.com Sent: Tuesday, January 22, 2013 19:48 To: 44net(a)hamradio.ucsd.edu Subject: Re: [44net] SOLVED - Gateways Unreachable after Dynamic IP Update Marius, RIP44 is a TCP connection, in the most simple terms, there MUST be communication BOTH ways (ACK, SYN ACK, the password, EST) via Encapsulation from your station to 44.0.0.1. It is safe to say that the encap route for 44.0.0.1 is operational if you seeded your router with a route to 44.0.0.1 OR with default; and are receiving announcements. Just because a host does not ping telnet, etc doesn't mean it's not operational (more below about how Don and I troubleshooted the issue).