Smarthub 2 creates pinhole for wrong IPv6 address

[DavidH7]

Currently Stateless, but I haven't noticed any difference. What difference should it make?

[licquorice]

It might as the hub will be allocating the address rather than the device self-allocating.

[DavidH7]

As far as I can see, the Smarthub assigns the Linux box's name (or sometimes a name based on its MAC address, and I don't know why it does one or the other) to an IPv6 address. Which party assigns the address, though? As I understand it, the router assigns the prefix (the top 64 bits) and the client assigns the rest (the bottom 64 bits), and then performs Duplicate Address Detection to ensure that the address really is unique. At some stage, the router accepts the address. The Smarthub lists the client in "My devices" with the hostname. But there is only one entry, which can be either of the two addresses that the Linux box asks for,

[licquorice]

For IPv4, you can forward ports based on either device name,  or IP address if the device has a static address. For IPv6, you can only create a pinhole to the device name as the IPv6 address is dynamic.

If stateful, the hub allocates the address based on the prefix using DHCP, for stateless the device self configures the address based on the prefix.

Are you sure you are correctly creating the pinhole?

[DavidH7]

To create a pinhole, all anyone can do is pick a device from the list that Smarthub gives, specify a port range, and specify the protocol (TCP, UDP or both). I don't see how anyone can do it incorrectly.

[DavidH7]

I have to set the Smarthub to do either stateless or both, as I have another device on the LAN that can only use SLAAC.

[jmcd-tf1]

also interested to get an answer to this as I'm trying to do something similar.

setting a pinhole to an internal device does not let traffic through the router.

I'm using ssh to test the port, so created an ipv6 pinhole to the device on the lan side.  But no joy in trying to ssh to the device.

SSH to the device ipv6 GUA permanent address on the lan side does work.

I'm no networking professional, but this seems like the BT HUB pinhole doesn't work.

by the way DavidH7 in case it is of help, I use a cron shell script running on a pi that emails me when the router IP address gets changed by BT.  This is v helpful so I can update access to the pi from external services manually.

[DavidH7]

I don't think you've given quite enough information to work out what's going wrong.

Is this a Linux box that you're trying to create a pinhole for?  If so, what does "ip -6 addr" show?  Are you trying to create a pinhole for an IPv6 address that has the "noprefixroute" attribute?  If so, that's not going to work, and it's not the fault of the Smarthub; such an address is not routable from the outside world.

If that's not what you're doing, then I think we need some more detail from you.

If you're using Windows, then I'm sorry, I can't help.