rohc team mailing list archive

[Edvar Afonso Luciano Filho <question245813@xxxxxxxxxxxxxxxxxxxxx>]

Question #245813 on rohc changed:
https://answers.launchpad.net/rohc/+question/245813

    Status: Answered => Open

Edvar Afonso Luciano Filho is still having a problem:
Hi Didier,

Thank you for your explanation. I'll take a look in the IP/ROHC tunnel.
I discovered that the rohc tunnel over ethernet can give me better results
than UDP one.

In my lab, I'm trying to create a ROHC tunnel between two Openflow (OF)
switches. My topology is linear (2 hosts and 2 switches):

Host A <-------> Switch 1 (S1) <--------> Switch 2 (S2) <-------> Host B

I'm using two PCs for the OF switches, each one with two ethernet cards
(eth0 and eth1).
I'm using the eth1 of S1 and eth1 of S2 to connect both switches.

On both switches, I created the rohc0 virtual interfaces (associated with
eth1)  and attached them to the openflow switch.
The switches are prepared to forward L2 frames and they work fine with icmp
packets (pings) from host A to host B, when I'm not using the ROHC tunnel.

When I tried to ping Host B (from Host A), using the ROHC tunnel, I see the
following:
1- The first switch S1 received ICMP the packets;
2- The packets are forwarded to S1's rohc0 interface. All ARP packets are
compressed;
3- The ROHC (compressed) packets arrived at S2 through eth1 but not reach
rohc0 (of S2);
4- The S2's decompressor didn't see any ROHC packet;

The major question is that using switches I can't attach interfaces with
associated ip address. So my rohc tunnel doesn't have any ip address
associated. I think that's the problem of my experiment.

Do you have any idea about how can I make the rohc tunnel using
switches?

Thanks in advance!

Edvar


2014-03-23 11:36 GMT-03:00 Didier Barvaux <
question245813@xxxxxxxxxxxxxxxxxxxxx>:

> Your question #245813 on rohc changed:
> https://answers.launchpad.net/rohc/+question/245813
>
> Didier Barvaux posted a new comment:
> Hello again,
>
> I have just decided to deprecate the ROHC over UDP tunnel. I don't use
> it for testing for a long time. I now use the sniffer and fuzzer tools
> for that. They are much better. For the tunnel features, the IP/ROHC
> tunnel now supersedes the ROHC over UDP tunnel: the IP/ROHC tunnel is
> designed for efficiency and may be used in production.
>
> So, next 1.7.0 version of the ROHC library will still contain the ROHC
> over UDP tunnel but a deprecation warning will be present in the wiki,
> in the sources, in the configure script, in the program usage, and in
> the program man page. The version after will completely remove the ROHC
> over UDP tunnel from the sources.
>
> Regards,
> Didier
>
> Deprecation commit:
> http://bazaar.launchpad.net/~didier-barvaux/rohc/main/revision/1017
> ROHC over tunnel (deprecated):
> https://rohc-lib.org/wiki/doku.php#rohc_over_udp_tunnel
> IP/ROHC (replacement): https://rohc-lib.org/wiki/doku.php#ip_rohc_tunnel
>
> --
> You received this question notification because you asked the question.
>

-- 
You received this question notification because you are a member of ROHC
Team, which is an answer contact for rohc.