So, this is what I get in wireshark when I try to ping 44.0.0.1:
11552 1391.581656 *44.124.1.17* *44.0.0.1* ICMP 82 Echo (ping) request id=0x0000, seq=0/0, ttl=127 (no response found!)
I also notice some RIP activity as well:
11488 1381.431009 *44.0.0.1* *224.0.0.9* RIPv2 386 Response 11489 1381.431145 *192.168.1.147 169.228.34.84* ICMP 414 Destination unreachable (Protocol unreachable)
Looks as though it is receiving the RIP password, but when BPQ tries to get the routes, it is unable to.
the ipr table is not populating either, except for some local IPs:
ipr PBSNOD:W7PBS-7} 6 Entries
- Christopher Kelley KG7UJH
On Fri, Feb 19, 2021 at 4:01 AM John Wiseman via 44Net < 44net@mailman.ampr.org> wrote:
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:
so I have confirmed that I am receiving rip44, so I removed the static routes. Does it take some time for the gateway to update? my ipr table is populated but I can't ping 44.0.0.1
-Christopher Kelley KG7UJH
On Thu, Feb 18, 2021 at 1:42 PM n7fyo Erik Beck via 44Net < 44net@mailman.ampr.org> wrote:
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@mailman.ampr.org
On
Behalf Of CJ Kelley via 44Net Sent: Thursday, February 18, 2021 10:19 AM To: 44net@mailman.ampr.org Cc: CJ Kelley debiani386@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net