20 Feb
2021
20 Feb
'21
6:17 a.m.
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
On Fri, Feb 19, 2021 at 6:41 AM Lee D Bengston via 44Net <
44net(a)mailman.ampr.org> wrote:
On Fri, Feb 19, 2021, 5:02 AM John Wiseman via 44Net
<
44net(a)mailman.ampr.org>
wrote:
_________________________________________
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
Isn't that a static tunnel route that was added to bpq32.cfg as opposed to
a route received via RIP? I'm thinking the OP needs to add that in order
to ping 44.0.0.1.
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.
73,
Lee K5DAT