During my tests yesterday (to get RIP working with a multicast socket) there was an extended period where there was only a default route in my table 44 which is used to send network-44 traffic. This default route sends the traffic to amprgw as tunneled traffic (ipip). This route is normally used only for traffic leaving net 44 to the internet, and more specific tunnels are used for all gateway stations. But this temporarily did not work while I was debugging and the RIP packets were not being processed.
What I noticed was that I lost connectivity to the other network-44 stations during that interval. I would expect that amprgw would forward the traffic to the other stations. Of course this is not a desirable permanent situation, but I think it worked in the past.
Has this forwarding been blocked in amprgw? Or is this something that must be caused by a local configurarion error here? (like a firewall issue)
Rob
Hi Ron,
Ampr-gw doesn't route anything to other ampr hosts. It allows only the routing to internet hosts. To reach ampr hosts you need to have a tunnel established with each host... So the behavior is as expected.
Marius, YO2LOJ
Hello Rob Firewall are totally open on the PC (no firewall), router have 192.168.1.2 as DMZ please rob confirm this is OK because 192.168.1.2 are the ip from the Ethernet card André ON4HU
Le 06/10/13 12:02, Rob Janssen a écrit :
(Please trim inclusions from previous messages) _______________________________________________ During my tests yesterday (to get RIP working with a multicast socket) there was an extended period where there was only a default route in my table 44 which is used to send network-44 traffic. This default route sends the traffic to amprgw as tunneled traffic (ipip). This route is normally used only for traffic leaving net 44 to the internet, and more specific tunnels are used for all gateway stations. But this temporarily did not work while I was debugging and the RIP packets were not being processed.
What I noticed was that I lost connectivity to the other network-44 stations during that interval. I would expect that amprgw would forward the traffic to the other stations. Of course this is not a desirable permanent situation, but I think it worked in the past.
Has this forwarding been blocked in amprgw? Or is this something that must be caused by a local configurarion error here? (like a firewall issue)
Rob _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
-
Marius Petrescu -
on4hu -
Rob Janssen