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