[MIP6D-NG Support] TCP over RO does not work!
BOKOR Laszlo
goodzi at mcl.hu
Thu Sep 3 10:53:00 CEST 2015
Dear Vahid,
sorry for the big holiday silence. Have you managed to solve the problem?
We have experienced similar issues with umip, but they were solved after a
kernel change (maybe it was a downgrade to an older veresion, I do not
remember clearly).
Anyway, mip6d-ng is completely independent from umip: please try to reach
umip developers in umip (mip6d) matters. mip6d-ng is available from
http://www.mip6d-ng.net/, but its features are different from umip's
features. E.g., umip provides RO, mip6d-ng does not; umip does not provide
flow bindings and X-layer API, mip6d-ng does; etc.
Best regards,
goodzi
--
László BOKOR, Ph.D.
Budapest University of Technology and Economics (BME)
Department of Networked Systems and Services (HIT)
Tel: +36-1-463-2048, Fax: +36-1-463-3263
web: http://medianets.hu/staff/laszlo-bokor/
On Mon, 6 Jul 2015, Vahid Heydari wrote:
>
> I am using mip6d in ubuntu 15.04. I did all steps as mentioned in: http://www.umip.org/docs/umip-install.html with kernel 4.0.5.
>
>
>
> Everything (Mobile Node, Home Agent, Corresponding Node) works perfectly. When mobile node is in foreign network, ping6 and telnet from CN works good (packets are sent to HA and
> encapsulated to mobile node). The problem is Routing Optimization. When I enable RO, CN and MN start to use "type 2 routing header" and "destination option header". after RO, CN can send
> ping6 to MN (packet is forwarded to CoA and HoA will be in destination option header) and receive answer. However, TCP connection does not work between CN and MN. I mean, when RO is
> used, telnet from CN to MN is received by MN's IP layer (as I saw in wireshark) but the packet is not forwarded to TCP layer! I can not see any error message or "connection refused". I
> think IP layer does not forward a packet with type 2 routing header to TCP layer. Not that ping6 works good between CN and MN. I disabled ufw and do not have any rules in ip6tables.
>
>
>
> So, destination host receives a packet with "home address" and shows in wireshark but does not forward the packet to tcp layer.
>
>
>
> Any suggestion?
>
>
>
More information about the Support
mailing list