Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No MAP Register with 1.3.0 with NAT traversal on #42

Open
blade5502 opened this issue Apr 25, 2020 · 3 comments
Open

No MAP Register with 1.3.0 with NAT traversal on #42

blade5502 opened this issue Apr 25, 2020 · 3 comments

Comments

@blade5502
Copy link

Hi,

my testbed looks like the following:

  • 3 Debian 10 Servers (MS, xTR, RTR) - all with public routeable RLOC
  • 2 OpenWRT boxes configured as xTR - 1 with public routable RLOC, 1 with NAT
  • EID space are some RFC1918 networks

On the debian servers "master" was self-compiled, for OpenWRT i used the precompiled package from http://www.openoverlayrouter.org/downloads/OpenWrt/

Communication works fine between the EID spaces, except for the OpenWRT box behind NAT which is unable to map-register. According to log output it sends out map-register packets, which don't show up on a tcpdump, which means they never actually get sent.

A downgrade of oor on the OpenWRT box to version 1.2.1 fixed this, map register over RTR is successful and EID space is reachable by others.

@blade5502
Copy link
Author

Maybe has something to do with this commit?

f5a14ac

@albert-lopez
Copy link
Member

Hi,
Thanks for reporting it. Could you send me the logs at level 3 of OpenWRT ? I believe the commit you pointed could not be the reason of the problem. This commit was introduced to not duplicate the map register message which is also sent when receiving the info reply message.

@blade5502
Copy link
Author

blade5502 commented Apr 27, 2020

Hi,

you can find the log here: https://pastebin.com/eeHL8C7A

MS/MR: 92.X.X.42
RTR: 92.X.X.44

I did some further investigation. Seem like map request ECM packages are sent, but with i source port of 0 according to tcpdump > these packets never arrive at the destination router.

OpenWRT tcpdump:

tcpdump: listening on br-lan, link-type EN10MB (Ethernet), capture size 262144 bytes
22:48:28.722932 IP (tos 0x0, ttl 255, id 1, offset 0, flags [DF], proto UDP (17), length 78)
192.168.99.252.4342 > 92.X.X.42.4342: [udp sum ok] unknown-type-7,
22:48:28.757889 IP (tos 0x0, ttl 245, id 7910, offset 0, flags [DF], proto UDP (17), length 108)
92.X.X.42.4342 > 192.168.99.252.4342: [udp sum ok] unknown-type-7,
22:48:28.778887 IP (tos 0x0, ttl 255, id 3, offset 0, flags [DF], proto UDP (17), length 160)
192.168.99.252.0 > 92.X.X.44.4342: [udp sum ok] LISP-Encapsulated-Contol-Message,
22:48:29.536294 IP (tos 0x0, ttl 255, id 4, offset 0, flags [DF], proto UDP (17), length 60)
192.168.99.252.4342 > 92.X.X.44.4342: [udp sum ok] LISP-Map-Request,
22:48:31.534908 IP (tos 0x0, ttl 255, id 6, offset 0, flags [DF], proto UDP (17), length 160)
192.168.99.252.0 > 92.X.X.44.4342: [udp sum ok] LISP-Encapsulated-Contol-Message,
22:48:34.534489 IP (tos 0x0, ttl 255, id 8, offset 0, flags [DF], proto UDP (17), length 160)
192.168.99.252.0 > 92.X.X.44.4342: [udp sum ok] LISP-Encapsulated-Contol-Message,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants