rohc team mailing list archive

[Didier Barvaux <didier.barvaux@xxxxxxxxxxxxxxxxxxxx>]

Josephine,

> > 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:*
> 
> :~/rohc-1.2.0# 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 137.158.131.84/27 brd 137.158.131.95 scope global eth0
> 5: rohc0: <POINTOPOINT,MULTICAST,NOARP> mtu 1500 qdisc noop qlen 500
>     inet 10.0.0.1/24 scope global rohc0

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


> ~/rohc-1.2.0# ip -4 route
> 137.158.131.64/27 dev eth0  proto kernel  scope link  src
> 137.158.131.84 169.254.0.0/16 dev eth0  scope link  metric 1000
> default via 137.158.131.65 dev eth0

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.

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 ?

Didier Barvaux
Viveris Technologies