TZUTC: -0600
MSGID: 2734.ipv6@1:154/700 2d762e15
REPLY: 1851.fido_ipv6@1:135/115 2d75f661
PID: Synchronet 3.21a-Linux master/cb44b2ab5 Nov 01 2025 GCC 15.2.1
TID: SBBSecho 3.31-Linux master/cb44b2ab5 Nov 01 2025 GCC 15.2.1
BBSID: PHARCYDE
CHRS: UTF-8 4
FORMAT: flowed
NOTE: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko
20100101Thunderbird/140.4.0
Hey Dan!

On Sun, Nov 09 2025 09:54:14 -0600, you wrote:

> Yes, it is always kept up to date.

Then I agree, it's surprising you don't have any obvious settings that would
include IPv6. If it is indeed mentioned anywhere, it may start with enabling
it prior to it showing you all of the other settings.

> I imagine they would support it, and if they don't (being an open 
> source project) I would be extremely surprised. They seem to have
> been posting blogs about they themselves using it since 2013 or even 
> earlier:

> https://www.ipfire.org/blog/infrastructure-2-ipv6-pushing-the-button

> I think that link says they are using v6 to allow access to *their* 
> *site*, not that it's functioning in their firewall product.

That's exactly what I said with "blogs about they themselves using it". ;)

> I have done further research and confirmed that it is NOT currently 
> available in the firewall.  That does seem strange, but it's backed
> up by the fact that I see no sign of any v6 options/choices in the 
> configuration of the firewall.  :-(

Odd that they boast that they're using it for all of their services, but don't
include it in their product. It seems IPFire 3 "is a major rewrite of IPFire
2" and "is at a very early stage of development and there is no definite
release date, yet." Which also includes "Full-Stack IPv6 Support". That's a
bummer, and kinda wayu behind the times seeing as though most other routers
(including store bought) already fully support it.

> I'm gonna learn some more about all this, and am currently pretty
> loaded up with real life/work stuff, so it may wait until after the
> holidays. Thanks for your input/help!
No worries, at least the interest in looking into it is (kinda) there, now!

First step would be to see if it is even there from the ISP, with the
possibility of IPFire blocking it from reaching the rest of your network.

Regards,
Nick

... Sarcasm, because beating people up is illegal.
--- SBBSecho 3.31-Linux
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
SEEN-BY: 1/19 100 16/0 19/10 37 104/117 119 105/81 106/201 114/10
SEEN-BY: 123/130 128/187 129/14 142/104 153/757 7715 154/10 30 50
SEEN-BY: 154/110 700 201/0 203/0 218/700 840 220/20 30 221/1 6 360
SEEN-BY: 226/18 30 44 50 227/114 229/110 112 206 317 400 426 428 470
SEEN-BY: 229/616 664 700 705 230/0 240/1120 5832 266/512 280/464 5003
SEEN-BY: 280/5555 291/111 292/854 301/1 320/119 219 319 2119 322/757
SEEN-BY: 322/762 335/364 341/66 234 342/200 396/45 423/81 460/58 633/280
SEEN-BY: 902/26 2320/105 5020/1042
PATH: 154/700 10 221/6 1 320/219 229/426