Hey John, I've tried to telnet to both addresses and get the same result on both...unreachable protocol This is from the linux trace screen.... 21:11:16.086099 IP 192.168.1.150 > 83.71.213.122: IP 44.135.90.2.3970 > 44.155.6.226.23: S 1402888192:1402888192(0) win 2048 <mss 512> (ipip-proto-4) 21:11:16.225955 IP 83.71.213.122 > 192.168.1.150: ICMP 83.71.213.122 protocol 4 port 44 unreachable, length 72
73, Don - ve3zda
-----Original Message----- From: 44net-bounces+ve3zda=gmail.com@hamradio.ucsd.edu [mailto:44net-bounces+ve3zda=gmail.com@hamradio.ucsd.edu] On Behalf Of John Ronan Sent: Saturday, June 09, 2012 3:43 PM To: 'AMPRNet working group' Subject: [44net] Quick Test Request
(Please trim inclusions from previous messages) _______________________________________________ Hi,
I've got two machines running here on the, 44.155.6.225 and 44.155.6.226. I'd appreciate if someone on the 44-net could just check they can reach 44.155.2.226 for me please (it could be slow, machine is going an apt-get update at the moment).
Also, would anyone be in a position to tell me what the best wireless mesh protocol to use is at the moment. These are two Icom ID-1 D-star radios. I've two more that two local hams are going to put running for me on high points and I'd like to run something 'mesh' on the nodes to allow me to get back to the gateway (225) from anywhere within range of any three?
Regards John EI7IG
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net