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(a)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(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net