No docs on how "Interface-ID IPv4" in related hosts is supposed to work?

[Moonbase59]

trafficstars

Thanks for the wonderful (and really useful) project!

I’ve set up two machines in my network as "related hosts" and only filled their "Interface-ID IPv6", which works fine when using IPv6, but not at all when using IPv4.

So how is a "Interface-ID IPv4" supposed to work? What should be put in there, and what about the netmasks? (I assume I should put my provider’s prefix length (56) in there?)

My assumption is that if you DNS resolve a related host, it should build its complete address by using whatever prefix is current plus the given IPv6 interface id (which seems to work). If using IPv4 (I think), it should resolve to the one IPv4 address I get from my provider, so it actually resolves to the router’s IPv4 address and can get NATed, right?

I’m using a Fritz!Box 7490 and have German Telekom as provider.

[ThomasWaldmann]

it's somehow the same idea as for v6, just for v4.

for a lot of users it is not super useful, because they do not get multiple v4 addresses from their provider.

if you only get 1 ipv4 address:

if-id ipv4:

• if you put nothing there, it won't get an A record.
• if you put 0 there, it will get the main v4 address + 0, so guess that is what you want.

netmask ipv4 (on the main host):

• should be 32

in general, the computation is: rel_addr = main_addr & mask + if_id

[Moonbase59]

Ah, I see … Cheers for the explanation and fast response, I’ll try :-)

[Moonbase59]

Just one more question regarding the netmask: Which part of the IP address does it mask?

So, if I get a 56-bit IPv6 prefix from my provider (in effect, a 72-bit subnet), does it mask the leftmost part, i.e. should I put "56" in it, or does it mask the subnet part (i.e., I put "72" in there)?

[ThomasWaldmann]

iirc it masks the leftmost part.

[Moonbase59]

Ok, thanks, trying.

[gschintgen]

* if you put 0 there, it will get the main v4 address + 0, so guess that is what you want.

Hi, I'd kindly suggest to add this single phrase to the docs. It's so helpful! Otherwise, nsupdate.info is just perfect. Thanks a lot!

[ThomasWaldmann]

reopening so we add something about this to the docs.