Thanks. I am interested in this dialog, as I have a similar problem. I've been able to setup my gateway to the point that I can receive the RIPv2 44 table, and ampr-rip is dutifully adding the information to the routing table. I can ping 44.0.0.1, but that's it. Erik, N7FYO -----Original Message----- From: 44Net <44net-bounces+traderbeckola=tahoma.com(a)mailman.ampr.org> On Behalf Of CJ Kelley via 44Net Sent: Thursday, February 18, 2021 10:19 AM To: 44net(a)mailman.ampr.org Cc: CJ Kelley <debiani386(a)gmail.com> Subject: [44net] Question about setting up 44net connection on BPQ Hi Everyone, I am trying to set up a BPQ node for access over the 44net and I have been running into trouble getting the connection working. I am running into an issue where I am not able to ping any 44 nodes. I can ping the local 44net interface, but can't ping past that. The host is in a DMZ, so it should be receiving the rip44 table. Even though the IPs are internal, I scrubbed them. What am I missing here? I am not able to ping any 44net nodes. I pulled 44.44.6.33 for sample: ping 44.44.6.33 PBSNOD:W7PBS-7} OK My arp table: arp PBSNOD:W7PBS-7} x.x.x.191 70:2a:d5:4a:29:9d 255 E 2770 The portion of bpq32.cfg for configuring the 44net connection. Port 1 is AXIP and Port 3 is the telnet port. IPGATEWAY Adapter \Device\NPF_{64EA23A4-79E1-4342-83E5-E92D65C2CA3D} 44ENCAP x.x.x.147 # Enable AMPRNET Tunnels and RIP44. I used 148 as the Tunnel Enpoint IPAddr 44.124.1.17 #This is the first IP in your AMPRnet allocation. IPNetmask 255.255.255.248 #AMPRnet netmask (Why is this 248 ? This is for your AMPRnet subnet. Your AMPRnet subnet is /29) IPPorts 1,3 ARP 44.124.1.17 x.x.x.147 3 D route 44.124.1.16/29 44.124.1.17 ; AMPRnet routes. route addprivate 44.124.1.16/29 encap 70.167.209.246 ; Arizona routes route addprivate 44.124.9.0/24 encap 65.49.149.125 route addprivate 44.124.7.0/25 encap 174.74.248.93 route addprivate 44.124.10/30 encap 50.116.8.127 route addprivate 44.124.1.8/29 encap 107.2.6.33 Thank you for your time, Christopher Kelley KG7UJH _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

So long as ipr 44.0.0.1 shows a route ping should work ipr 44.0.0.1 POGO4:G8BPQ-9} 797 Entries 44.0.0.1/32 3 T 1 3560 encap 169.228.34.84 ping 44.0.0.1 POGO4:G8BPQ-9} OK Ping Response from 44.0.0.1 Though I had to ping a couple of times to get it to work. Does a Wireshark trace show the ping being sent as an encapsulated packet to your isp router? 73, John On 19/02/2021 10:33, CJ Kelley via 44Net wrote: routing On been an 44net for _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

So long as ipr 44.0.0.1 shows a route ping should work ipr 44.0.0.1 POGO4:G8BPQ-9} 797 Entries 44.0.0.1/32 3 T 1 3560 encap 169.228.34.84

ping 44.0.0.1 POGO4:G8BPQ-9} OK Ping Response from 44.0.0.1 Though I had to ping a couple of times to get it to work.

I had the 44ENCAP address set to the IP address of the PC. I changed it to an unused IP and put that IP in the DMZ as well, but no change. I still see these messages in wireshark *44.0.0.1* *224.0.0.9* RIPv2 386 Response *192.168.1.147 169.228.34.84* ICMP 414 Destination unreachable (Protocol unreachable) I am able to ping .34.84 from the PC, but can't ping it from BPQ. I found https://groups.io/g/bpq32/topic/accessing_ampr_portal_when/78850768?20,0,0,… and added both routes to BPQ, but no difference. Anything else I need to check? Here is my configuration as of now IPGATEWAY Adapter \Device\NPF_{64EA23A4-79E1-4342-83E5-E92D65C2CA3D} 44ENCAP 192.168.1.254 # Enable AMPRNET Tunnels and RIP44. I used 148 as the Tunnel Enpoint IPAddr 44.124.1.17 #This is the first IP in your AMPRnet allocation. IPNetmask 255.255.255.248 #AMPRnet netmask (This is your AMPRnet subnet. AMPRnet subnet is /29) IPPorts 1,3 Christopher Kelley KG7UJH