rohc team mailing list archive
-
rohc team
-
Mailing list archive
-
Message #00014
Re: Tunnel tool ping error
Hi Didier,
> > What is the output of the following commands on the 2 machines on
> > > which you run the rohctunnel commands ?
> > > # ip -4 addr
> > > # ip -4 route
> > > # iptables -L -vn
> > > # ping <IPv4 address of the other endpoint>
> >
> > *Machine B:*
> > [...]
>
> Machine B seems OK.
>
> > *Machine A:*
> > [...]
>
> Machine A is not OK. The rohc0 interface is not UP and RUNNING, use the
> following command to fix that:
> # ip link set rohc0 up
>
> > [...]
>
> The route toward network 10.0.0.0/24 is not present. It should be setup
> when the rohc0 interface will become UP and RUNNING. Please check that
> the route is present after running the 'ip link set rohc0 up' command.
>
Thanks, I set up the interface correctly, but still could not ping - the
output was:
:~# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
> There is an additional thing that looks strange to me. The ping from
> machine A to machine B gets a TTL of 57. The ping from B to A gets a
> TTL of 63. Beside the fact they are different (is there different paths
> to go from one machine to the other in your network ?), it shows that
> you have at least one router between the 2 machines. They could be the
> root of the problem. Could you please test the tunnel tool with 2
> machines on the same Ethernet link to see if it works ?
>
I still couldn't ping even when they were directly connected:
*Machine A:*
# ip -4 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
100
inet 192.168.0.20/24 brd 192.168.0.255 scope global eth0
6: rohc0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast qlen 500
inet 10.0.0.1/24 scope global rohc0
# ip -4 route
10.0.0.0/24 dev rohc0 proto kernel scope link src 10.0.0.1
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.20
# iptables -L -vn
Chain INPUT (policy ACCEPT 6274 packets, 3995K bytes)
pkts bytes target prot opt in out source
destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 6428 packets, 621K bytes)
pkts bytes target prot opt in out source
destination
# ping 192.168.0.21
PING 192.168.0.21 (192.168.0.21) 56(84) bytes of data.
64 bytes from 192.168.0.21: icmp_seq=1 ttl=64 time=0.404 ms
64 bytes from 192.168.0.21: icmp_seq=2 ttl=64 time=0.404 ms
64 bytes from 192.168.0.21: icmp_seq=3 ttl=64 time=0.233 ms
# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
*Machine B:*
# ip -4 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
inet 192.168.0.21/24 brd 192.168.0.255 scope global eth0
3: rohc0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast qlen 500
inet 10.0.0.2/24 scope global rohc0
# ip -4 route
10.0.0.0/24 dev rohc0 proto kernel scope link src 10.0.0.2
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.21
# iptables -L -vn
Chain INPUT (policy ACCEPT 1345 packets, 79487 bytes)
pkts bytes target prot opt in out source
destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 1343 packets, 75775 bytes)
pkts bytes target prot opt in out source
destination
# ping 192.168.0.20
PING 192.168.0.20 (192.168.0.20) 56(84) bytes of data.
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=4.82 ms
64 bytes from 192.168.0.20: icmp_seq=2 ttl=64 time=0.374 ms
64 bytes from 192.168.0.20: icmp_seq=3 ttl=64 time=0.183 ms
# ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
Regards,
Josephine
Follow ups
References