7 Aug
2015
7 Aug
'15
3:15 a.m.
As per Brian message, unfortunately the problem to
reach the hamwan.org remain unsolved here.
Hope to solve this dilemma soon
However that Marius, Rob et al can rightly address
this problem.
About the routing/interface status:
root@ir0rm-7:/# ip route|grep 44.0.0
44.0.0.1 via 169.228.66.251 dev tunl0 onlink window 840
44.0.0.0/8 dev tunl0 proto kernel scope link src 44.134.32.240
the tunnel source address is 44.134.32.240 and the tunl0 interface
shows:
root@ir0rm-7:/# ifconfig tunl0
tunl0 Link encap:IPIP Tunnel HWaddr
inet addr:44.134.32.240 Mask:255.0.0.0
UP RUNNING NOARP MULTICAST MTU:1480 Metric:1
RX packets:732341 errors:0 dropped:0 overruns:0 frame:0
TX packets:46177 errors:671646 dropped:0 overruns:0 carrier:0
collisions:671646 txqueuelen:0
RX bytes:66262509 (63.1 Mb) TX bytes:4506125 (4.2 Mb)
note that (I'm not aware why) on the tunl0 interface there are
many errors/collisions on the TX tunnel side.
Ping to hamwan.org gave (since now) no result.
root@ir0rm-7:/# ping hamwan.org -c 5
PING hamwan.org (44.24.241.98) 56(84) bytes of data.
--- hamwan.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms
gus
On 08/07/2015 01:38 AM, Brian Kantor wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Testing shows that traffic between encap'd and BGP'd subnets of
network 44 is now possible. There was a bug in the ipfw rules
that fed the encapsulator that has been corrected and it seems
to work now.
- Brian