MadaMada
@madamada@snac.void.my
- 2001:: = Global Unique Address
- fd00:: = Unique Local Address
- fe80:: = Link Local Address
Knowing those 3 is enough to get you going in most cases..
ARP is for IPv4 what NDP is for IPv6..
There is no broadcast address in IPv6..
IPv6 is a completely different protocol and addressing..looking at it from an IPv4 mindset just complicates things..
@madamada @leean00
Changing prefix and FW rules is easy to handle with #OpenWrt as FW4 allows for negative subnet masks. e.g. ::a1/-64
If you run services on a dynamic prefix delegation, you need to update your DNS records in a dynamic way, Depending what is at your disposal.
If you have a dyndns provider which allows only for a prefix update and updates all RRs is the easiest.
As @madamada said, forget you legacy protocol mind set. And start with a clean sheet.
However most of us live with dynamic prefixes, and this becomes a problem..luckily one way around this is to use ULA addressing internally, and map those addresses in DNS.
Then combine that with DynDNS or nsupdate if you are using your own domain name for the WAN side and configure port forwarding or a reverse proxy. You could also probably use NPTv6 to deal with dynamic prefix mapping but that's another beast all together..
@leean00
Negative network masks with the FW4 in #OpenWrt works the way that you allow whatever network prefix you have this rule will allow access to the host with the ::a1 host address.
DynDNS or nsupdate depending on your setup works. There are a few DynDNS providers that allow to update only the prefix and all AAAA RRs are updated automatically. Meaning that the router could run a script or ddnsclient and no need on the hosts.
My take on ULAs: use only where necessary.
@madamada Are adhock network connection possible?
@madamada When I was younger, I used to take my wiki on the train with me and I'd create a direct IPv4 connection between the laptop and the Raspberry Pi.
It required that you set the gateway and the netmask the same as to that of the other machine. No router involved, but a cross over cable.
Then I'd use the routing percentage thing to make sure I was equally connected between the ethernet to the pi and the wifi of the train (MTU, I think).
And I could access both the raspberry pi and the wifi internet.
@madamada okay thanks again, I'll have to try that out too
In IPv6, it's the same, for example:
pi
- fdaa::1/64
Laptop
- fdaa::2/64
On Laptop, after connecting cable, ping fdaa::1, if you get reply, then proceed to route -6n add default fdaa::1 and update /etc/resolv.conf to use fdaa::1 as default nameserver
@madamada One more ... sorry, if I want to redo the HE.net Cert, any idea what domains it will accept?
Already tried Gmail and protonmail