Good day all,
I am wondering if my setup is fully operational, can you guy's take 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
Hello Jean,
Checked all IP's - there is NO RESPONSE to pings at all.
Best regards. Tom - sp2lob
Following my test request, can you include your IP addresse to see if I can ping you?
Thank you!.
On Sun, Dec 15, 2013 at 7:51 AM, sp2lob sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello Jean,
Checked all IP's - there is NO RESPONSE to pings at all.
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Jean,
I see your subnet in my routing table:
44.135.49.0/24 via 173.0.201.101 dev tunl0 proto static onlink
My IP's: 44.165.2.2 FPAC-node / linux.sp2lob.ampr.org 344.165.2.3 JNOS-2.0j4
Best regards. Tom - sp2lob
Hi Tom, when is last time you updated yopur encap.txt, 3 months agoo I change for my static IP
Jean
On Sun, Dec 15, 2013 at 7:59 AM, sp2lob sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Jean,
I see your subnet in my routing table:
44.135.49.0/24 via 173.0.201.101 dev tunl0 proto static onlink
My IP's: 44.165.2.2 FPAC-node / linux.sp2lob.ampr.org 344.165.2.3 JNOS-2.0j4
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Jean,
You're right... It was from my desktop, Hi! Now, from my Raspberry Pi: 44.135.49.0/27 via 209.169.172.211 dev tunl0 proto 44 onlink window 840
But even now, I do not get any response while pinging your IP's.
You may telnet to my IP's: telnet 44.165.2.2 - FPAC-node telnet 44.165.2.2 3694 - URONode telnet 44.165.2.3 - JNOS-2.0j4
You may NOT get response while pinging my addresses, beacuse there is something broke in RIP44v2 broadcasts from amprgw and block of 44.165 adresses is not icluded.
By what means you're making your routing table, please?
Best regards. Tom - sp2lob
Jean,
Checked right now - I'm getting responses to my pings!
Best regards. Tom - sp2lob
Ok, I will wait for few more replies, I think this confirm my tought. My firewall is not working propely. until I will ping you, you wont be able to ping me back, then after thet you will be OK for about 15 minutes, then you are blocked again. try again in 30 minutes or so, I am sure you won't be able to ping me back.
Thanks for your time.
Jean
On Sun, Dec 15, 2013 at 8:13 AM, sp2lob sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Jean,
Checked right now - I'm getting responses to my pings!
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
I can ping 1,2,and 4 from 44.131.244.1 13:45 GMT de Paul
Hi Tom, I am not sure, I think it's RIP44v2, I did not set my station, Brian (N1URO) did 99% of the work, I think I was making more dommage then good, so what I am doing now it's learning. I was able to connect your Jnos.
Jean
On Sun, Dec 15, 2013 at 8:09 AM, sp2lob sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Jean,
You're right... It was from my desktop, Hi! Now, from my Raspberry Pi: 44.135.49.0/27 via 209.169.172.211 dev tunl0 proto 44 onlink window 840
But even now, I do not get any response while pinging your IP's.
You may telnet to my IP's: telnet 44.165.2.2 - FPAC-node telnet 44.165.2.2 3694 - URONode telnet 44.165.2.3 - JNOS-2.0j4
You may NOT get response while pinging my addresses, beacuse there is something broke in RIP44v2 broadcasts from amprgw and block of 44.165 adresses is not icluded.
By what means you're making your routing table, please?
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Hey Jean, I can only ping 44.135.49.1
Don - ve3zda
On Sun, Dec 15, 2013 at 8:02 AM, Jean Létourneau ve2pkt@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hi Tom, when is last time you updated yopur encap.txt, 3 months agoo I change for my static IP
Jean
On Sun, Dec 15, 2013 at 7:59 AM, sp2lob sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Jean,
I see your subnet in my routing table:
44.135.49.0/24 via 173.0.201.101 dev tunl0 proto static onlink
My IP's: 44.165.2.2 FPAC-node / linux.sp2lob.ampr.org 344.165.2.3 JNOS-2.0j4
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
--
Sysop de: VE2PKT (BBS), VE2PKT-3 (URONode),VE2PKT-4, VE2RAJ (XRouter) : VE2RCN-1, VE2RDL-1, VE2RGC-1, VE2RVA-1, (The-Net) : VE2PKT-9 (DXCluster), VE2PKT-10 (Winlink Gateway) RF: 147.435 Mhz (1200 Bps)
Internet: Telnet xrouter-ve2pkt.dyndns.org port 23 (Network Node) Telnet fbb-ve2pkt.dyndns.org port 6300 (FBB BBS) Telnet ve2pkt.dyndns.org port 9000 (DXCluster)
E-Mail: packet: ve2pkt@ve2pkt.#qbc.qc.can.noam ampr net: ve2pkt@ve2pkt.ampr.org Inet: ve2pkt@amsat.org or ve2pkt@gmail.com
n1uro@n1uro:~$ ping.pl 44.135.49.0/29 info 44.135.49.1 is alive info 44.135.49.2 is alive info 44.135.49.3 info 44.135.49.4 is alive info 44.135.49.5 info 44.135.49.6 info 3 out of 6 (50%) are alive n1uro@n1uro:~$
Użytkownik Brian Rogers napisał:
(Please trim inclusions from previous messages) _______________________________________________
n1uro@n1uro:~$ ping.pl 44.135.49.0/29 info 44.135.49.1 is alive info 44.135.49.2 is alive info 44.135.49.3 info 44.135.49.4 is alive info 44.135.49.5 info 44.135.49.6 info 3 out of 6 (50%) are alive n1uro@n1uro:~$
Check pings me because I do not have to you me 44-net IP: 44.165.25.233 and 44.165.25.232 and 'telnet 44.165.25.233' or 'telnet 62.69.192.233' route to me: addprivate 44.165.25/24 encap 62.69.192.233
the .1 and .2 ping fine for me.
Bob VA3RJS
________________________________ From: Jean Létourneau ve2pkt@gmail.com To: AMPRNet working group 44net@hamradio.ucsd.edu Sent: Sunday, December 15, 2013 7:45:02 AM Subject: [44net] Tester requested.
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy's take 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
I guess you are making changes on the fly, I can now ping 44.135.49.2 as well so that only leaves 44.135.49.4
Don
On Sun, Dec 15, 2013 at 8:14 AM, Bob Scanferla va3rjs@yahoo.ca wrote:
(Please trim inclusions from previous messages) _______________________________________________ the .1 and .2 ping fine for me.
Bob VA3RJS
From: Jean Létourneau ve2pkt@gmail.com To: AMPRNet working group 44net@hamradio.ucsd.edu Sent: Sunday, December 15, 2013 7:45:02 AM Subject: [44net] Tester requested.
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy'stake 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
--
Sysop de: VE2PKT (BBS), VE2PKT-3 (URONode),VE2PKT-4, VE2RAJ (XRouter) : VE2RCN-1, VE2RDL-1, VE2RGC-1, VE2RVA-1, (The-Net) : VE2PKT-9 (DXCluster), VE2PKT-10 (Winlink Gateway) RF: 147.435 Mhz (1200 Bps)
Internet: Telnet xrouter-ve2pkt.dyndns.org port 23 (Network Node) Telnet fbb-ve2pkt.dyndns.org port 6300 (FBB BBS) Telnet ve2pkt.dyndns.org port 9000 (DXCluster)
E-Mail: packet: ve2pkt@ve2pkt.#qbc.qc.can.noam ampr net: ve2pkt@ve2pkt.ampr.org Inet: ve2pkt@amsat.org or ve2pkt@gmail.com
Hi Bob, What is ou are your IP Addresses? I'd like to se if I can ping you back.
Thanks.
On Sun, Dec 15, 2013 at 8:14 AM, Bob Scanferla va3rjs@yahoo.ca wrote:
(Please trim inclusions from previous messages) _______________________________________________ the .1 and .2 ping fine for me.
Bob VA3RJS
From: Jean Létourneau ve2pkt@gmail.com To: AMPRNet working group 44net@hamradio.ucsd.edu Sent: Sunday, December 15, 2013 7:45:02 AM Subject: [44net] Tester requested.
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy'stake 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
--
Sysop de: VE2PKT (BBS), VE2PKT-3 (URONode),VE2PKT-4, VE2RAJ (XRouter) : VE2RCN-1, VE2RDL-1, VE2RGC-1, VE2RVA-1, (The-Net) : VE2PKT-9 (DXCluster), VE2PKT-10 (Winlink Gateway) RF: 147.435 Mhz (1200 Bps)
Internet: Telnet xrouter-ve2pkt.dyndns.org port 23 (Network Node) Telnet fbb-ve2pkt.dyndns.org port 6300 (FBB BBS) Telnet ve2pkt.dyndns.org port 9000 (DXCluster)
E-Mail: packet: ve2pkt@ve2pkt.#qbc.qc.can.noam ampr net: ve2pkt@ve2pkt.ampr.org Inet: ve2pkt@amsat.org or ve2pkt@gmail.com
Hi Jean,
44.135.49.1 is no reachable from my gateway, 44.129.192.1. I’m not running rip44d daemon and using a newest encamp.txt. I guess my gateway is not entered in your routing table. My routing table is maybe OK.
% ping 44.135.49.1 PING 44.135.49.1 (44.135.49.1): 56 data bytes --- 44.135.49.1 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss
% route get 44.135.49.1 route to: ve2pkt.ampr.org destination: 44.135.49.0 mask: 255.255.255.224 gateway: 209-169-172-211.ubr03.labaie.derytele.com interface: nostun0 if address: jm1wbb.ampr.org
73 Isao / JM1WBB
Jean, work fine now. Isao
% ping 44.135.49.1 PING 44.135.49.1 (44.135.49.1): 56 data bytes 64 bytes from 44.135.49.1: icmp_seq=0 ttl=253 time=242.133 ms 64 bytes from 44.135.49.1: icmp_seq=1 ttl=253 time=239.333 ms 64 bytes from 44.135.49.1: icmp_seq=2 ttl=253 time=239.336 ms --- 44.135.49.1 ping statistics --- 4 packets transmitted, 3 packets received, 25.0% packet loss round-trip min/avg/max/std-dev = 239.333/240.267/242.133/1.378 ms
2013/12/15 23:48、Isao SEKI - JM1WBB iseki@gongon.com のメール:
(Please trim inclusions from previous messages) _______________________________________________ Hi Jean,
44.135.49.1 is no reachable from my gateway, 44.129.192.1. I’m not running rip44d daemon and using a newest encamp.txt. I guess my gateway is not entered in your routing table. My routing table is maybe OK.
% ping 44.135.49.1 PING 44.135.49.1 (44.135.49.1): 56 data bytes --- 44.135.49.1 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss
% route get 44.135.49.1 route to: ve2pkt.ampr.org destination: 44.135.49.0 mask: 255.255.255.224 gateway: 209-169-172-211.ubr03.labaie.derytele.com interface: nostun0 if address: jm1wbb.ampr.org
73 Isao / JM1WBB _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Jean it does not work from ve2uqh 44.135.52.33
73, Michel ve2bcw
2013/12/15 Isao SEKI - JM1WBB iseki@gongon.com
(Please trim inclusions from previous messages) _______________________________________________ Jean, work fine now. Isao
% ping 44.135.49.1 PING 44.135.49.1 (44.135.49.1): 56 data bytes 64 bytes from 44.135.49.1: icmp_seq=0 ttl=253 time=242.133 ms 64 bytes from 44.135.49.1: icmp_seq=1 ttl=253 time=239.333 ms 64 bytes from 44.135.49.1: icmp_seq=2 ttl=253 time=239.336 ms --- 44.135.49.1 ping statistics --- 4 packets transmitted, 3 packets received, 25.0% packet loss round-trip min/avg/max/std-dev = 239.333/240.267/242.133/1.378 ms
2013/12/15 23:48、Isao SEKI - JM1WBB iseki@gongon.com のメール:
(Please trim inclusions from previous messages) _______________________________________________ Hi Jean,
44.135.49.1 is no reachable from my gateway, 44.129.192.1. I’m not running rip44d daemon and using a newest encamp.txt. I guess my gateway is not entered in your routing table. My routing table is maybe OK.
% ping 44.135.49.1 PING 44.135.49.1 (44.135.49.1): 56 data bytes --- 44.135.49.1 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss
% route get 44.135.49.1 route to: ve2pkt.ampr.org destination: 44.135.49.0 mask: 255.255.255.224 gateway: 209-169-172-211.ubr03.labaie.derytele.com interface: nostun0 if address: jm1wbb.ampr.org
73 Isao / JM1WBB _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
I can ping .2 and .4 but not .1
73 jerry
-----Original Message----- From: 44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu [mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of Jean Létourneau Sent: Sunday, December 15, 2013 7:45 AM To: AMPRNet working group Subject: [44net] Tester requested.
(Please trim inclusions from previous messages) _______________________________________________
Good day all,
I am wondering if my setup is fully operational, can you guy's take 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
Try me My net44 subnet 44.48.0.41 uronode.n9lya.ampr.org uronode.n9lya 44.48.0.42 k9bbs.ampr.org k9bbs 44.48.0.45 w9bbs.ampr.org w9bbs 44.48.0.46 n9lya.ampr.org n9lya n9lya-3
-----Original Message----- From: 44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu [mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of Jean Létourneau Sent: Sunday, December 15, 2013 7:45 AM To: AMPRNet working group Subject: [44net] Tester requested.
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy's take 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
n1uro@n1uro:~$ ping.pl 44.48.0.40/29 info 44.48.0.41 is alive info 44.48.0.42 is alive info 44.48.0.43 info 44.48.0.44 info 44.48.0.45 is alive info 44.48.0.46 is alive info 4 out of 6 (66%) are alive n1uro@n1uro:~$
Jerry,
All addresses you mentioned starting at 44.48.0.41 are pingable from the Swiss HAMNET (44.142.0.0/24)
73 de Markus HB9CTB
-----Ursprüngliche Nachricht----- Von: 44net-bounces+hb9ctb=bluewin.ch@hamradio.ucsd.edu [mailto:44net-bounces+hb9ctb=bluewin.ch@hamradio.ucsd.edu] Im Auftrag von Jerry Gesendet: Sonntag, 15. Dezember 2013 14:48 An: 'AMPRNet working group' Betreff: Re: [44net] Tester requested.
(Please trim inclusions from previous messages) _______________________________________________ Try me My net44 subnet 44.48.0.41 uronode.n9lya.ampr.org uronode.n9lya 44.48.0.42 k9bbs.ampr.org k9bbs 44.48.0.45 w9bbs.ampr.org w9bbs 44.48.0.46 n9lya.ampr.org n9lya n9lya-3
-----Original Message----- From: 44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu [mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of Jean Létourneau Sent: Sunday, December 15, 2013 7:45 AM To: AMPRNet working group Subject: [44net] Tester requested.
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy's take 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
Jean, the only one that does not work for me is 44.135.49.4
73, Don - ve3zda
On Sun, Dec 15, 2013 at 2:09 PM, Markus Mueller hb9ctb@bluewin.ch wrote:
(Please trim inclusions from previous messages) _______________________________________________ Jerry,
All addresses you mentioned starting at 44.48.0.41 are pingable from the Swiss HAMNET (44.142.0.0/24)
73 de Markus HB9CTB
-----Ursprüngliche Nachricht----- Von: 44net-bounces+hb9ctb=bluewin.ch@hamradio.ucsd.edu [mailto:44net-bounces+hb9ctb=bluewin.ch@hamradio.ucsd.edu] Im Auftrag von Jerry Gesendet: Sonntag, 15. Dezember 2013 14:48 An: 'AMPRNet working group' Betreff: Re: [44net] Tester requested.
(Please trim inclusions from previous messages) _______________________________________________ Try me My net44 subnet 44.48.0.41 uronode.n9lya.ampr.org uronode.n9lya 44.48.0.42 k9bbs.ampr.org k9bbs 44.48.0.45 w9bbs.ampr.org w9bbs 44.48.0.46 n9lya.ampr.org n9lya n9lya-3
-----Original Message----- From: 44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu [mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of Jean Létourneau Sent: Sunday, December 15, 2013 7:45 AM To: AMPRNet working group Subject: [44net] Tester requested.
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy'stake 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
--
Sysop de: VE2PKT (BBS), VE2PKT-3 (URONode),VE2PKT-4, VE2RAJ (XRouter) : VE2RCN-1, VE2RDL-1, VE2RGC-1, VE2RVA-1, (The-Net) : VE2PKT-9 (DXCluster), VE2PKT-10 (Winlink Gateway) RF: 147.435 Mhz (1200 Bps)
Internet: Telnet xrouter-ve2pkt.dyndns.org port 23 (Network Node) Telnet fbb-ve2pkt.dyndns.org port 6300 (FBB BBS) Telnet ve2pkt.dyndns.org port 9000 (DXCluster)
E-Mail: packet: ve2pkt@ve2pkt.#qbc.qc.can.noam ampr net: ve2pkt@ve2pkt.ampr.org Inet: ve2pkt@amsat.org or ve2pkt@gmail.com
Jean,
44.135.49.1/44.135.49.2/44.135.49.2
Are not reachable from here.
Bob VE3TOK
On 13-12-15 05:30 PM, Don Moore wrote:
(Please trim inclusions from previous messages) _______________________________________________ Jean, the only one that does not work for me is 44.135.49.4
73, Don - ve3zda
Le 15/12/13 07:45, Jean Létourneau a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy'stake 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
Hello Jean, It does'nt work from here
Pascal, essei encore SVP
On Sun, Dec 15, 2013 at 9:48 AM, ve2hom Pascal ve2hom@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Le 15/12/13 07:45, Jean Létourneau a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy'stake 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
Hello Jean,
It does'nt work from here-- Meilleur 73' de Pascal ve2hom
Le 15/12/13 07:45, Jean Létourneau a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy'stake 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
Hello Jean, It now work
On 16/12/13 01:45, Jean Létourneau wrote:
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy'stake 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
Hi Jean,
I can not ping any of your addresses from here.
Regards ..... Peter ( ZL2BAU-3 44.147.210.26 )
No luck on my end.
03:06:50.900200 IP 10.252.48.194 > 209.169.172.211: IP 44.4.36.1 > 44.135.49.1: ICMP echo request, id 14358, seq 1, length 64 (ipip-proto-4) 03:06:51.908287 IP 10.252.48.194 > 209.169.172.211: IP 44.4.36.1 > 44.135.49.1: ICMP echo request, id 14358, seq 2, length 64 (ipip-proto-4) 03:06:52.916287 IP 10.252.48.194 > 209.169.172.211: IP 44.4.36.1 > 44.135.49.1: ICMP echo request, id 14358, seq 3, length 64 (ipip-proto-4)
03:05:43.482466 IP 10.252.48.194 > 209.169.172.211: IP 44.4.36.1 > 44.135.49.2: ICMP echo request, id 14356, seq 1, length 64 (ipip-proto-4) 03:05:44.482208 IP 10.252.48.194 > 209.169.172.211: IP 44.4.36.1 > 44.135.49.2: ICMP echo request, id 14356, seq 2, length 64 (ipip-proto-4) 03:05:45.482216 IP 10.252.48.194 > 209.169.172.211: IP 44.4.36.1 > 44.135.49.2: ICMP echo request, id 14356, seq 3, length 64 (ipip-proto-4)
03:09:15.904472 IP 10.252.48.194 > 209.169.172.211: IP 44.4.36.1 > 44.135.49.4: ICMP echo request, id 14366, seq 1, length 64 (ipip-proto-4) 03:09:16.912281 IP 10.252.48.194 > 209.169.172.211: IP 44.4.36.1 > 44.135.49.4: ICMP echo request, id 14366, seq 2, length 64 (ipip-proto-4) 03:09:17.920269 IP 10.252.48.194 > 209.169.172.211: IP 44.4.36.1 > 44.135.49.4: ICMP echo request, id 14366, seq 3, length 64 (ipip-proto-4)
Blaine, K1QV
On Sun, Dec 15, 2013 at 4:45 AM, Jean Létourneau ve2pkt@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Good day all,
I am wondering if my setup is fully operational, can you guy'stake 2 minute of your time and try to ping the following adddresses from your ampr.org network and reporte them back to me:
44.135.49.1, 44.135.49.2 and 44.135.49.4
thank you!
73 de Jean,
--
Sysop de: VE2PKT (BBS), VE2PKT-3 (URONode),VE2PKT-4, VE2RAJ (XRouter) : VE2RCN-1, VE2RDL-1, VE2RGC-1, VE2RVA-1, (The-Net) : VE2PKT-9 (DXCluster), VE2PKT-10 (Winlink Gateway) RF: 147.435 Mhz (1200 Bps)
Internet: Telnet xrouter-ve2pkt.dyndns.org port 23 (Network Node) Telnet fbb-ve2pkt.dyndns.org port 6300 (FBB BBS) Telnet ve2pkt.dyndns.org port 9000 (DXCluster)
E-Mail: packet: ve2pkt@ve2pkt.#qbc.qc.can.noam ampr net: ve2pkt@ve2pkt.ampr.org Inet: ve2pkt@amsat.org or ve2pkt@gmail.com