miniupnpd

[Francisco Obispo]

I've been banging my head against the wall using miniupmpd at home.

for some reason, when using NAT-PMP, my computer sends a request to open a port, lets say port 22, and the miniupmpd discovers that the port is a privileged port, which is ok, it then assigns a mapping that looks like this:

DNAT       tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:2022 to:192.168.255.160:2022 


The target IP should be pointing to port 22, and not 2022, somehow it just maps SPT=DPT, which is very stupid on their side, because the NAT-PMP protocol does not allow contemplate a change on the service port on the client.

what ends up happening, is that requests to my public ip on port 2022 get forwarded to my internal LAN IP on port 2022, where there is no SSH server running :-(.

This is very annoying.. I've also tried natpmpd and it seems to have a similar behavior..

Does anyone know what's going on?

Francisco







On Feb 22, 2012, at 8:57 AM, Francis Dupont wrote:

>> as noted I updated to a mildly later version, I'm easy as to what is
>> actually used, but generally prefer moving forward rather than
>> backward.
> 
> => usually it is pretty easy to update the code as the changes from the
> miniupnp team are very orthogonal to what needed for the PCP support.
> I can open a ticket for an update to 1.6.20120207 (last) version
> if you prefer...
> 
> Regards
> 
> Francis Dupont <fdupont at isc.org>
> _______________________________________________
> sdcpe-devel mailing list
> sdcpe-devel at lists.isc.org
> https://lists.isc.org/mailman/listinfo/sdcpe-devel

Francisco Obispo 
email: fobispo at isc.org
Phone: +1 650 423 1374 || INOC-DBA *3557* NOC
PGP KeyID = B38DB1BE