Can I Block Specific Devices from getting IPv6 Address?

[Stephen Harrington]

This would null out ipv6 dns for specific mac address but would only be offered as suggestion the device may still overrule it.

I’ll definitely give this a try in the next week or so, thanks!
Your other suggestions re: Netflix are not practical for me as it’s not just Netflix the SmartDNS is spoofing, but thanks anyway.

 

[Stephen Harrington]

I feel your pain as I also live in Australia, the same method applies to other streaming services, just need to find the right domains with a quick google search.

No pain really ... my fallback position is just to leave IPv6 turned off - I haven’t had it up until now anyway and it’s not like it’s stopping me doing anything, in fact as of right now it’s more trouble than it’s worth. Would be nice to work it out though so I can start playing and making the whole home network IPv6 ready - but not at the expense of all the much more useful luxuries

 

[Stephen Harrington]

I don't know if this will work, but can you not use ip6tables to drop all packets from the device? I don't know whether the device will keep trying ipv6 or stick to ipv4 only though.

Possibly yes if I knew what I doing ... much more research needed!

 

[maghuro]

Sorry to bring this thread back from the dead, but it's it possible to block done specific device from getting ipv6 address right now?

 

[SomeWhereOverTheRainBow]

Sorry to bring this thread back from the dead, but it's it possible to block done specific device from getting ipv6 address right now?

I imagine if you know what port dhcp6 uses to assign addressing (maybe port 546 or 547), you could block the flow of traffic to a specific MAC address coming from that port with ip6tables. this would prevent dhcp6 reaching the device.

 

[maghuro]

I imagine if you know what port dhcp6 uses to assign addressing (maybe port 546 or 547), you could block the flow of traffic to a specific MAC address coming from that port with ip6tables. this would prevent dhcp6 reaching the device.

Can you teach me how to?
And how can I find the dhcp6 port? Right now is set to native

 

[DTM]

Running latest Asuswrt-Merlin 384.12 on an RT-AC86U.

My ISP has enabled experimental IPv6 support on their infrastructure and I'd like to have a play with it on my network, mostly as a learning exercise at this point. I got it working fine using "Native" mode and with DHCP-PD "Enabled".

Is there any way through creating/editing Custom Configs or otherwise to block a couple of specific devices from getting an IPv6 address, but still keep getting their (static) IPv4 address "as usual"?

For example, my main media player is an Apple TV 4K. I use DNS Filter feature to give it an alternate DNS address to get around geo-blocking for some streaming services. If I enable IPv6 on the network though, the Apple TV grabs an IPv6 address, and this appears to take precedence over IPv4 and thus the "alternate" IPv4 DNS no longer works to "aid" my streaming services. There seems to be no way to turn off IPv6 on the Apple TV itself.

Thanks in advance, any suggestions or discussion gratefully received.

Connect your Apple TV to a wi-fi access point or ethernet cable from a device with IPV6 disabled. In other words, use another device between your main router and the Apple TV. This could be an access point for Wi-Fi or a switch for ethernet. If the device won't handle IPV6 traffic then it will isolate the TV box.

 

[ColinTaylor]

Connect your Apple TV to a wi-fi access point or ethernet cable from a device with IPV6 disabled. In other words, use another device between your main router and the Apple TV. This could be an access point for Wi-Fi or a switch for ethernet. If the device won't handle IPV6 traffic then it will isolate the TV box.

Necropost, and incorrect.

Switches and access points are layer 2 devices. They have no knowledge of anything at layer 3 which includes IPv4 and IPv6. They merely forward frames from one node to another on the local network.

 

[Viktor Jaep]

Necropost, and incorrect.

Lol just got to love the term "necropost"... makes me crack up every time someone like @DTM tries to reply to a post LITERALLY 5 years old. Seriously... by this time, @Stephen Harrington has already dumped IPv6 for the newer, better, safer and more secure IPv7!

 

[Stephen Harrington]

Seriously... by this time, @Stephen Harrington has already dumped IPv6 for the newer, better, safer and more secure IPv7!

Nah, so far I've gone the low-tech route and leave IPv6 disabled, a philosophy I continued when the RT-AC86 got hit by lightning and I used the insurance payout to get an RT-AX86U. Just hoping the next lightning strike coincides with the release of the RT-BE86U along with @RMerlin announcing support!

 

[Viktor Jaep]

Nah, so far I've gone the low-tech route and leave IPv6 disabled, a philosophy I continued when the RT-AC86 got hit by lightning and I used the insurance payout to get an RT-AX86U. Just hoping the next lightning strike coincides with the release of the RT-BE86U along with @RMerlin announcing support!

This is certainly going to be the year of BE models!

 

[SomeWhereOverTheRainBow]

This is certainly going to be the year of BE models!

I am already feeling your excitement!