16 Jan
2013
16 Jan
'13
10:03 p.m.
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
16 Jan
16 Jan
10:12 p.m.
Ping from my home PC to 44.60.44.1 works
JNOS shows the route to 44.60.44.1 as 98.252.61.22 & unable to ping via encap
Ping and HTTP access to the 3 addresses works fine
(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
--
Charles J. Hargrove - N2NOV
NYC ARECS/RACES Citywide Radio Officer/Skywarn Coord.
NYC-ARECS/RACES Net Mon. @ 8:30PM 147.360/107.2 PL
http://www.nyc-arecs.org and http://www.nyc-skywarn.org
NYDXA SWL & Scanner Net Wed. @ 9PM 147.360/107.2 PL
http://www.n2nov.net
"Information is the oxygen of the modern age. It seeps through the walls topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying
(The work praises the man.)
"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan
11:19 p.m.
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(a)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(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
11:37 p.m.
Did you submit the change to the gateway?
73, Don - ve3zda
On Wed, Jan 16, 2013 at 6:19 PM, Bob Tenty <bobtenty(a)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(a)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
list44Net@hamradio.ucsd.eduhttp://hamradio.ucsd.edu/mailman/listinfo/44nethttp://www.ampr.org/donate.html
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
18 Jan
18 Jan
11:04 a.m.
Here's what I see.
I watch the trace screen usually on a regular basis and the following is
what happens....
When I ping your addresses I see the encap to you using 98.252.61.22 but I
do not see your end encaping back to me.
Are you sure your end is actually encaping back?
I can ping 98.252.61.22 however and do see the return which is un encaped
as it should be.
73, Don - ve3zda
On Wed, Jan 16, 2013 at 5:03 PM, <lleachii(a)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(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
4264
days inactive
4266
days old
4 comments
4 participants
participants (4)
-
Bob Tenty -
Charles Hargrove -
Don Moore -
lleachii＠aol.com