15 Dec
2013
15 Dec
'13
5:19 p.m.
Użytkownik Marc, LX1DUC napisał:
Here I have a problem, my command:
[root@server ~]# tcpdump -v -s0 -n proto ipencap | grep 44.165.25
...
23:09:06.745031 IP (tos 0x0, ttl 39, id 30037, offset 0, flags [none], proto: IPIP (4),
length: 104) 169.228.66.251 > 62.69.192.233: IP (tos 0x0, ttl 48, id 0, offset 0,
flags
[DF], proto: ICMP (1), length: 84) 75.80.130.94 > 44.165.25.232: ICMP echo request, id
26187, seq 21126, length 64
...
My server does not respond to such a frame tunnel (Public_IP > 44Net_IP) '
75.80.130.94 >
44.165.25.232:'
Tunnel (44Net_IP > 44Net_IP) I have no problems.
...
23:09:10.556700 IP (tos 0x0, ttl 235, id 16048, offset 0, flags [none], proto: IPIP (4),
length: 60) 213.73.1.100 > 62.69.192.233: IP (tos 0x0, ttl 253, id 20086, offset 0,
flags
[none], proto: TCP (6), length: 40) 44.165.68.254.15928 > 44.165.25.232.14580: ., cksum
0x2cd8 (correct), ack 1031 win 1024
...
Here is my problem with the tunnel (Public_IP > 44Net_IP)
--
73 de Janusz / SP1LOP
===== Janusz J. Przybylski, SP1LOP ==================
Poland AMPRNet Co-ordinator [44.165/16] from Mar 2003
=====================================================
Why me of my
network 44.165.25.0/24 do not have access to all the
>44.0.0.0/8 ??? I use encap.txt and tunnel:
>
>tunl0 Link encap: IPIP Tunnel HWaddr inet addr: 44.165.25.232
>Mask: 255.255.255.255 UP RUNNING NOARP MTU: 1024 Metric: 1 RX
>packets: 100704 errors: 0 dropped: 0 overruns: 0 frame: 0 TX
>packets: 71193 errors: 0 dropped: 0 overruns: 0 carrier: 0
>collisions: 0 txqueuelen: 0 RX bytes: 15150482 (14.4 MiB) TX bytes:
>8963045 (8.5 MiB)
>
I cannot ping 44.165.25.232 nor traceroute towards it.
# ADDRESS LOSS SENT LAST AVG BEST
WORST STD-DEV STATUS
1 100% 1 timeout
2 100% 1 timeout
3 100% 1 timeout
However if I traceroute to any other IP within 44.165.25.0/24 I get at
least a reply from 62.69.192.233.
# ADDRESS LOSS SENT LAST AVG BEST
WORST STD-DEV STATUS
1 62.69.192.233 0% 1 42.3ms 42.3 42.3
42.3 0
2 100% 1 timeout
3 100% 1 timeout
Eventually a routing or firewalling issue...
Can you ping and traceroute towards some 44/8 destinations. Try
44.161.255.3 and let me know the results.