20 Feb
2021
20 Feb
'21
9:38 a.m.
Corrected the DMZ configuration (it was pointing to the wrong IP. DOH!) and
its working now. Thanks all for the help!
73
Christopher Kelley
KG7UJH
On Sat, Feb 20, 2021 at 4:51 AM John Wiseman via 44Net <
44net(a)mailman.ampr.org> wrote:
Normally only one address can be put in the DMZ. Are
you sure
192.168.1.254 is there?
What does Wireshark capturing 192.168.1.254 show?
73,
John
On 20/02/2021 11:17, CJ Kelley via 44Net wrote:
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
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net