Next up, the Fidonet nodelist.
We will see in a day or two...
Hello Rob,
Wednesday April 05 2023 23:22, I wrote to you:
Next up, the Fidonet nodelist.
We will see in a day or two...
Hmmm.... it seems to take a bit longer than just a couple of days. Almost two weeks later and still no binkp.synchro.net in the nodelist for 1:103/705. :(
In IPv6 avery device has a Unique Global Address, so one
can simply create pinholes in advance as needed for the address
in question.
Only when you know the IPv6 address and port beforehand.
When runing servers you normally do...
Usually an IPv6 address on the home LAN is dynamic (SLAAC),
No. SLAAC addresses are not dynamic. They are derived from the MAC address.
and the port in peer-to-peer applications, VoIP applications etc
is often dynamic too.
VOIP normally uses standard ports.
The situation is different of course when you are hosting an IPv6
web-server or something like that. It would have a fixed IPv6
address and port anyway, so there is no need for punch-holing the
firewall.
Indeed.
Only when you know the IPv6 address and port beforehand.
When runing servers you normally do...
P2P apps like Transmission are not really servers.
Well they are in the strict sense of the word, but people just start
them up and hope for them to work out of the box,
and they are often configured by default to randomize port numbers on
each start.
Usually an IPv6 address on the home LAN is dynamic (SLAAC),
No. SLAAC addresses are not dynamic. They are derived from the
MAC address.
Not any more. AFAIK the recent implementation of SLAAC uses the
privacy extensions which do not use the MAC address but some random numbers to derive the IPv6 host address.
and the port in peer-to-peer applications, VoIP applications etc
is often dynamic too.
VOIP normally uses standard ports.
SIP (the signalling protocol) does, but the RTP uses random ports. A firewall has no way to know the RTP dynamic port numbers unless it inspects the SIP protocol.
The situation is different of course when you are hosting an
IPv6 web-server or something like that. It would have a fixed
IPv6 address and port anyway, so there is no need for
punch-holing the firewall.
Indeed.
I don't really understand your point. If we decide that UPnP (think "automatic firewall configuration from the inside") is desirable for
IPv4,
then it's desirable for IPv6 too. If we decide that UPnP is not
desirable, you can do without it in IPv4: just configure a static
RFC1918 address and port on your internal "server" and create a static NAT/portmapping entry on the router.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,114 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492507:18:00 |
| Calls: | 14,267 |
| Calls today: | 3 |
| Files: | 186,320 |
| D/L today: |
16,623 files (5,077M bytes) |
| Messages: | 2,518,275 |