IPv6 is necessary. You can take credit for having activated IPv6 at Swisscom Wireline for over 10 years.

And exactly this plug and play still works. 19 out of 20 problems here were never related to IPv6. Although it has always been recommended to deactivate.

But whatever. The last question was how to work with dynamic prefixes or how the PD works on a subrouter.

Functions that fortunately are not dependent on the stalled development of Internet boxes. You now have a native IP, but you don’t know what to do with it.

Whether you can then make progress with people who ask themselves why they want third-party routers or ask themselves why IPv6 is even necessary because it “works” without it has already been answered.

Absolutely. The only reason to deactivate IPv6 is to use the Internet Booster, as there is no IPv6 in the mobile network and problems can then arise. I also never understood why someone recommends disabling IPv6.

@Tux0ne

I never claimed that, viewed as a whole, the introduction or The rapid nationwide spread of IPv6 is not urgently necessary, but rather that the “normal” end user doesn’t care because he either doesn’t know what IPv6 is or because he has no personal benefit from it and doesn’t notice any disadvantage if IPv6 is deactivated. Even as an expert and technology freak, you should also put on the glasses of a run-of-the-mill user when considering and arguing, because this is exactly what Swisscom primarily addresses with its products and services in the RES segment.

@5018

For example, in the early days I had to deactivate IPv6 because three ancient devices were causing problems “thanks to IPv6” (1x Samsung TV, 1x Zyxel NIC, 1x HP printer). However, all three devices are no longer in operation in the meantime. And there were also a few users in the forum whose problems disappeared after turning off IPv6 on the IB. It is only logical that when there are nebulous problems in the forum, it is still occasionally recommended to temporarily switch off IPv6 in order to narrow down the error after the elimination process.

P.S.:

The same discussion happens every now and then, for example in the area of ​​WPA2/3. Even if theory says otherwise, for example for iPhone 5 and older the setting must be WPA2only.

So I found two very entertaining threads about this here.

Funny, oracular and busted all in one. The second thread in particular actually deserves the legendary status 😂
[https://community.swisscom.ch/t5/Archiv-Internet/Vorteile-IPv6-als-Konsument/td-p/326025](https://community.swisscom.ch/t5/Archiv-Internet/Vorteile- IPv6-as-consumer/td-p/326025)

[https://community.swisscom.ch/t5/Archiv-Internet/Internet-Box-IPV6-aktivieren-deaktivieren/td-p/540066](https://community.swisscom.ch/t5/Archiv-Internet/ Internet-Box-IPV6-activate-deactivate/td-p/540066)

Have you ever looked at the date in the first thread, times change.

And in the second thread, even 3 years later, I still fully stand by my core statements. Only in the statement in post #11 would I now write “for at least 10 years” instead of “20-30 years”.

Yes, a very long time in which you could develop enormous practical know-how if you always look for solutions and don’t capitulate and deactivate.

That means for me.

• Activate IPv6 as soon as possible via Swisscom Labs, i.e. with a Google 6rd script on an Open WRT.
• Enabling IPv6 on Centro Grande
• Switching from RES to SMEs because there is a standstill on this topic and a lot of ignorance or other interests
• Enable IPv6 on the SMB CPE
• PPPoE passthrough, DMZ LAN1 on downstream router with full IPv6 support
• Notice that somehow it doesn’t quite work
• Swisscom support cannot help
• I contact Martin Gysi directly
• After much back and forth, this really verifies a bug on the SME CPE
• These fix it afterwards, my interventions came to nothing, it took the network architect to do it…
• Since then made many applications and situations with pfSense and IPv6. Privately as well as in business. (Really a lot. By far only a fraction of the IPv6 applications/solutions and hurdles were asked about in this community.)
• Swisscom doesn’t go any further, services become irrelevant for me, so I change ISP
• Swisscom (Hoi Ivan, how are you? good luck with your J search!) demoted me from Super User because mümümü 😂
• Commissioning of the latest SME CPE (at the request of Swisscom) in a productive environment because, as I said, there is no longer any Swisscom privately
• Activation of IPv6 of course again in the DMZ LAN 1
• Report after 1 hour that there is a packet loss in the DMZ via IPv6. IPv4 OK

So you can use the time or not. Everyone should know that for themselves. This is practical know-how every day and not just theory.

Written via IPv6 VPN because there is only 4G access with legacy IP in the beautiful Pampas.

@Tux0ne

For professionals/experts (and those who want to become one) as well as for all people interested in technology, this is all right, necessary and praiseworthy.

But again, from the perspective of a 08:15 customer who doesn’t even know how to write IP and doesn’t want to know, this has, at least superficially, zero relevance. And if I examine certain topics from the perspective of this clientele, that doesn’t mean that I have anything against IPv6 or that I don’t see the importance and necessity of IPv6.

Ultimately, the engineers, network technicians, network equipment suppliers and telcos also have to take responsibility if IPv6 has still not reached the awareness of end customers because they have missed out on successfully promoting IPv6 to business customers with appropriate use cases and marketing campaigns. and promote residential customers.

I don’t understand what you’re getting at. IPv6 is a necessary protocol now and for the future. There is no need for advertising for end customers. It works perfectly. With activated connections, depending on the type of service you use, over 50% of the traffic is transmitted via IPv6 without the customer noticing. That’s enough advertising and proof of the record. Now also available natively for Swisscom customers, without having to be packaged in IPv4 and routed via boarder gateways. So even more direct and better. Nobody advertises IPv6, HTTP/3, TLS 1.3, etc. These are simply newer protocols that replace older ones, faster or slower, until the tipping point at which the old version is no longer supported or very poorly.

Don’t put your hope in NAT, Synfuel or whatever. These are just expensive workarounds that can be considered for special cases.

But what is needed on the CPE is support for the few customers who are already doing port forwarding with IPv4. These are a smart local DNS resolver where you can manage the clients. They are DDNS services for the servers because the prefix is ​​dynamic. And a more manageable firewall is needed because it replaces NAT. Nothing more is actually needed for the basic requirements of an 08:14 Swisscom customer. You could have been watching this slowly for 10 years.

All the rest doesn’t matter at all. This could also be adapted to IPv4. A lack of support for port forwarding etc. would be just as bad. And here too you can say that hardly anyone needs it.

IB2/¾ still constantly receive new FW and therefore also IPv6 when activated in the network. IBP and IBS probably later, but you should switch to a current router anyway. The IBP is also more than 8 years old and the IBS is de facto too.

@scn

It’s the same for me too.

The cascaded router that accepts the IB3 delegation then has a 62 network.

If /60 is delegated but you only get /62, then that would be a mistake. So not normal. Wrong in the software of these Internetz cans….

scn
How exactly did you set it up?

IPv4 and IPv6 on Pfsense:

I get an IPv6 address like this: fe80::20b:XXXXXXXX but that is not a real IPv6 address.

I have a Zyxel AX7501-B0 as a bridge. IPv4 works and also Live and Replay TV.

@gnome2018

fe:: is the v6 link local. Do you have this address from the dashboard / gateways?

Check status/interfaces to see if v6 really isn’t assigned.

mabu1

Yes, that’s where I got it… as you say, it’s the v6 link local.

So I don’t receive IPv6 yet.

gnome2018

What do your system logs say, DHCP?

Try first with a /62 and then with prefix hint.

pfSenseIPV6DHCP

@mabu1

Unfortunately it didn’t work, no changes to your settings.

Do you have that with you too?

Things don’t look so bad here?

I worked with “Release WAN” under Interfaces and not with a restart in these tests.

@gnome2018

No, I don’t have that with me. For me it runs over DSL and PPPoE with another provider (BBCS).

Do you have IPV6 enabled in pfSense? You can find it via System/Advanced Tab:Networking / Allow IPv6

Here’s a hint about the problem from your log: [https://forum.netgate.com/topic/130805/default-ipv6-deny-rule-in-system-logs-even-tho-default-is-pass/4?lang=en](https:// forum.netgate.com/topic/130805/default-ipv6-deny-rule-in-system-logs-even-tho-default-is-pass/4?lang=de)

Let’s see if @Tux0ne wants to get involved here.