miniupnp.tuxfamily.org Forum Index miniupnp.tuxfamily.org
The forum about miniupnp and libnatpmp
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

MiniUPnPd 2.2.0 PCP maps to IPv6 link-level address!

 
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpd Bugs
View previous topic :: View next topic  
Author Message
BrucePerens



Joined: 12 Apr 2022
Posts: 1
Location: Berkeley, California, USA

PostPosted: Fri May 13, 2022 1:02 am    Post subject: MiniUPnPd 2.2.0 PCP maps to IPv6 link-level address! Reply with quote

Hi,

I have a Turris Omnia router running MiniUPnPd, package version 2.2.0-5. Turris runs an OpenWRT derivative. I'd appreciate if you could give me a clue or two to help me to debug this. As you can see from the log below, MiniUPnPd makes a mapping to the outward-facing IPv6 link-local address of the router in response to my PCP client, rather than the global IPv6 address I would expect. This might be RFC-compliant but it's not very useful Confused . The code is a bit difficult to read for a newbie, and I haven't figured out where it got this address. Could this be due to a misconfiguration on OpenWRT or Turris's part? Is this a known bug and there's a need for an upgrade? Or is my PCP client (my own creation) somehow _asking_ for this when it sets the requested address to 16 bytes of zeroes? If not, where in the MiniUPnPd code should I look for what's going wrong?

Thanks

Bruce

May 13 00:12:11 turris miniupnpd[7088]: ReceiveNATPMPOrPCPPacket: packet destination: fe80::6f0:21ff:fe31:914b scope_id=21
May 13 00:12:11 turris miniupnpd[7088]: PCP request received from [fe80::a6e5:7cff:fee8:bf20%br-lan]:5351 60bytes
May 13 00:12:11 turris miniupnpd[7088]: get_lan_for_peer() looking for LAN interface index=21
May 13 00:12:11 turris miniupnpd[7088]: ifname=br-lan index=21 str=192.168.10.1 addr=c0a80a01 mask=ffffff00
May 13 00:12:11 turris miniupnpd[7088]: updating pinhole to fe80::a6e5:7cff:fee8:bf20:8080 TCP
May 13 00:12:11 turris miniupnpd[7088]: PCP MAP: added mapping TCP 8080->fe80::a6e5:7cff:fee8:bf20:8080 'PCP MAP 09ff6be04521aa34a5971dc8'
Back to top
View user's profile Send private message Send e-mail
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1548

PostPosted: Sat May 14, 2022 10:24 am    Post subject: Reply with quote

I think the mapping is done to the originating PCP command IP.

Code:
May 13 00:12:11 turris miniupnpd[7088]: ReceiveNATPMPOrPCPPacket: packet destination: fe80::6f0:21ff:fe31:914b scope_id=21
May 13 00:12:11 turris miniupnpd[7088]: PCP request received from [fe80::a6e5:7cff:fee8:bf20%br-lan]:5351 60bytes

The PCP packet is from fe80::a6e5:7cff:fee8:bf20 to fe80::6f0:21ff:fe31:914b so that's logical the mapping is added to fe80::a6e5:7cff:fee8:bf20

could you try to change your client to send to/from global IPv6 addresses ?
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpd Bugs All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
Protected by Anti-Spam ACP
© 2007 Thomas Bernard, author of MiniUPNP.