Did you submit the change to the gateway?

73, Don - ve3zda

On Wed, Jan 16, 2013 at 6:19 PM, Bob Tenty <bobtenty@gmail.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________

I can't ping your amprnet addresses  from the 44.135.85/24 subnet but I can ping
98.252.61.22.
I hope my entry is in your encap.txt.

73,

Bob VE3TOK


On 13-01-16 05:03 PM, lleachii@aol.com wrote:
(Please trim inclusions from previous messages)
_______________________________________________


All,

I'm experiencing a technical issue that began when my dynamic WAN address obtained a new lease. I am no longer able to communicate with other 44 subnets after my WAN obtained a new IP address. My gateway is saved in the Portal with a dynamic domain name, and the IP is correctly displayed on the portal.ampr.org website. In addition, I have also updated my IP under the rip44d -a parameter.

I am still able to receive the RIP44 announcements from 44.0.0.1 and communicate with the Internet via the tunnel thru AMPRGW; but I am no longer able to reach other AMPR networks. My WAN IP changed on 11JAN2013.

Please feel free to perform any of the following, or let me know if I am reachable via AMPR:

Ping/traceroute Router 44.60.44.1
Ping and DNS 44.60.44.3
Ping and HTTP at 44.60.44.10, 44.60.44.11 and 44.60.44.12


Regards,


Lynwood
KB3VWG
44.60.44.0/24



_________________________________________
44Net mailing list
44Net@hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html


_________________________________________
44Net mailing list
44Net@hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html