3 ms·
You don't actually need to use Local:Address:A as a source to connect to Local:Address:B, you can connect from Global:Address:A. To make it more specific: if y
by Dagger2 3y ago
You don't actually need to use Local:Address:A as a source to connect to Local:Address:B, you can connect from Global:Address:A.
To make it more specific: if you advertise both 2001:db8:1::/64 and fd00::/64 as on-link on your network, a host can connect from 2001:db8:1::a to fd00::b, and fd00::b can reply to 2001:db8::a. Because both ranges are on-link, all communication is on-link and is never sent to the router. (This is just the normal behavior for on-link ranges.)
- LegionMammal978 3y agoWhat if the two hosts have no link-level connection, and the router is the only thing connecting them? Would I need to have a fiddly rule in my router's firewall allowing connections to and from Host B only if the other host has either the local range or the proper global range?
- Dagger2 3y agoDo you mean, say, one device that's on Ethernet and one that's on WiFi? Most people have their Ethernet and WiFi setups bridged so they count as the same link. If you actually mean two separate networks, where traffic has to be routed via the router... obviously there's a lot of ways of setting up firewall rules, and it depends on exactly what you want to do, but the simplest approach is to say "deny new connections coming in via the WAN interface". This will allow new connections going out the WAN interface, and also allow all connections between the two local networks in both directions, with no need to specify any IP ranges in the firewall at all.