To create a fixed address:
netsh int ipv6 add address Internet 2600:6c88:8c40:5b:f1do:1:103:705
For incoming you should create a pinhole for port 24554 and maybe port 23.
netsh int ipv6 add address Internet 2600:6c88:8c40:5b:f1do:1:103:705
That worked (after changing 'o' to '0' of course).
For incoming you should create a pinhole for port 24554 and maybe
port 23.
With the DMZ set, no pin-holes needed.
^
Again! ;-)
Hello Rob,
On Tuesday April 04 2023 15:18, you wrote to me:
netsh int ipv6 add address Internet 2600:6c88:8c40:5b:f1do:1:103:705
And your binkp server answers on that address:
+ 09:37 [3496] outgoing session with 2600:6c88:8c40:5b:f1d0:1:103:705:24554
So all you have to do to earn your 'f' in the list is update the DNS for the mew IPv6 address.
Binkd has the possibility to specify the address to use for outgoing calls. It overrides the OS preference.
bindaddr 2600:6c88:8c40:5b:f1do:1:103:705
I don't know about BinkIT.
For incoming you should create a pinhole for port 24554 and maybe
port 23.
With the DMZ set, no pin-holes needed.
I am still a bit puzzled about your setup. Do you have /any/ barrier between the big bad InterNet and your Fido Machine?
So all you have to do to earn your 'f' in the list is update the
DNS for the mew IPv6 address.
It probably makes more sense to just create a new hostname for fido traffic and have that point to that IPv6 address.
Is this just a vanity address or does it have some functional puporse?
Binkd has the possibility to specify the address to use for
outgoing calls. It overrides the OS preference.
bindaddr 2600:6c88:8c40:5b:f1do:1:103:705
I don't know about BinkIT.
Maybe. Outbound IPv6 interface control isn't very strong in Synchronet right now.
I am still a bit puzzled about your setup. Do you have /any/
barrier between the big bad InterNet and your Fido Machine?
Just the Windows firewall.
Hello Rob,
On Wednesday April 05 2023 10:08, you wrote to me:
So all you have to do to earn your 'f' in the list is update the
DNS for the mew IPv6 address.
It probably makes more sense to just create a new hostname for fido traffic and have that point to that IPv6 address.
Yes. Always a good idea to have different host names for different services. Then you have the option to split the services over different machines without having to change host names if the need arises. Most DNS providers have no limit on the number of subdomains.
Is this just a vanity address or does it have some functional puporse?
It is just vanity, it serves no technical purpose. But it is quit popular among the Fidonet IPv6 sysops. Over a third of them have such a vanity address.
Binkd has the possibility to specify the address to use for
outgoing calls. It overrides the OS preference.
bindaddr 2600:6c88:8c40:5b:f1do:1:103:705
I don't know about BinkIT.
Maybe. Outbound IPv6 interface control isn't very strong in Synchronet right now.
You can always discuss it with the author. ;-)
I am still a bit puzzled about your setup. Do you have /any/
barrier between the big bad InterNet and your Fido Machine?
Just the Windows firewall.
So you can configure it to pass ICMP6 Ping so that your binkp server address becomes pingable...
I'm my own DNS provider, so yeah, no limit. :-) I added
binkp.synchro.net for the f1d0 address and updated my _binkp._src SRV record as well.
Next up, the Fidonet nodelist.
Is this just a vanity address or does it have some functional
puporse?
It is just vanity, it serves no technical purpose. But it is quit
popular among the Fidonet IPv6 sysops. Over a third of them have
such a vanity address.
It's showing off a "feature" of IPv6. :-)
You can always discuss it with the author. ;-)
I didn't write most of the IPv6 support in Synchronet, that was
Stephen Hurd, but I can certainly look into it.
Next up, the Fidonet nodelist.
We will see in a day or two...
https://1drv.ms/i/s!ApZPvWcrEaRQ5_wrKOnYR4bZu_jJ3Q?e=8f5cy5
There are also options for Port Forwarding, Firewall, IPv6 Pin-holing, IPv6 DMZ, but I've never used any of those (or similar) features for
Does anyone know what software clients actually support IPv6
Pin-holing?
I would think Bittorrent clients and utilities like syncthing should (because they support UPnP for IPv4), but I guess they don't do IPv6 Pin-holing. Maybe some games?
Hello Victor,
On Thursday April 06 2023 18:30, you wrote to Rob Swindell:
Does anyone know what software clients actually support IPv6
Pin-holing?
I am not sure what you mean by "software clients" in this context.
IPv6 pin-holing is something that is applied to a firewall. Firewalls
are found in routers and OSs.
I would think Bittorrent clients and utilities like syncthing
should (because they support UPnP for IPv4), but I guess they
don't do IPv6 Pin-holing. Maybe some games?
Does anyone know what software clients actually support IPv6
Pin-holing?
I am not sure what you mean by "software clients" in this context.
IPv6 pin-holing is something that is applied to a firewall. Firewalls
are found in routers and OSs.
I would think Bittorrent clients and utilities like syncthing
should (because they support UPnP for IPv4), but I guess they
don't do IPv6 Pin-holing. Maybe some games?
Please eleborate...
Does anyone know what software clients actually support IPv6
Pin-holing?
I am not sure what you mean by "software clients" in this context.
IPv6 pin-holing is something that is applied to a firewall.
Firewalls are found in routers and OSs.
I would think Bittorrent clients and utilities like syncthing
should (because they support UPnP for IPv4), but I guess they
don't do IPv6 Pin-holing. Maybe some games?
I think he means software that uses uphp to open ports on a firewall
as and when they are needed, and the firewalls that respond to
such requests by opening the port. Therefore the app is poking a
pinhole through the firewall.
Please eleborate...
The Transmission torrent client, and the syncthing file
synchronization utility can use the UPnP protocol to request a
firewall to pass *IPv4* incoming traffic (and create a port porwarding
for IPv4 NAT). They cannot however (at least to my knowledge) use UPnP
or any other protocol to request a router to open a hole for incoming traffic in an *IPv6* firewall.
Please eleborate...
The Transmission torrent client, and the syncthing file
synchronization utility can use the UPnP protocol to request a
firewall to pass *IPv4* incoming traffic (and create a port
porwarding for IPv4 NAT). They cannot however (at least to my
knowledge) use UPnP or any other protocol to request a router to
open a hole for incoming traffic in an *IPv6* firewall.
I see. Or so I think. You ask for some kind of "IPv6 equivalent" for
UPnP. But why would you want that? UpNP is a questionable idea anyway.
For IPv4 it creates an entry in de NAT table and as a side effect
creates a hole in the firewall.
But why would you need that for IPv6?
For IPv6 there (normally) is no NAT, so no need to create an entry in
a NAT table.
In IPv6 avery device has a Unique Global Address, so one
can simply create pinholes in advance as needed for the address in question.
Please eleborate...
The Transmission torrent client, and the syncthing file
synchronization utility can use the UPnP protocol to request a
firewall to pass *IPv4* incoming traffic (and create a port
porwarding for IPv4 NAT). They cannot however (at least to my
knowledge) use UPnP or any other protocol to request a router to
open a hole for incoming traffic in an *IPv6* firewall.
I see. Or so I think. You ask for
for some kind of "IPv6 equivalent" for
UPnP. But why would you want that? UpNP is a questionable idea anyway.
For IPv4 it creates an entry in de NAT table and as a side effect
creates a hole in the firewall.
But why would you need that for IPv6?
For IPv6 there (normally) is no NAT, so no need to create an entry in
a NAT table.
In IPv6 avery device has a Unique Global Address, so one
can simply create pinholes in advance as needed for the address in question.
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.
Usually an IPv6 address on the home LAN is dynamic (SLAAC),
and the port in peer-to-peer applications, VoIP applications etc is
often dynamic too.
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.
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,096 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 47:58:46 |
| Calls: | 14,060 |
| Calls today: | 1 |
| Files: | 187,100 |
| D/L today: |
10,638 files (3,266M bytes) |
| Messages: | 2,486,019 |