#pppoe — Public Fediverse posts

Halo zu Alles anyone setup an #Openbsd or Better #FreeBSD router for an #PPPoE connection with #vlan835 ?

I have gigabit fiber (up and down) out in rural #Kansas. I remain very thankful for the end to decades of dealing with weird antennas and such.

But today they switched from raw #Ethernet to #PPPoE, and although performance hasn't suffered to a noticeable extent, my #MTU has gone from 1500 to 1492. I am probably irrationally annoyed at this.

But dammit, PPP? In 2025? And going backwards on packet size?

S I G H.

an exciting friday night in debugging this, I now think it is a bug in VyOS that has been there for a while:

https://forum.vyos.io/t/ipv6-does-not-seem-to-be-working-on-pppoe-interfaces-since-1-3rolling/16602

#VyOS
#IPV6
#PPPOE

#VyOS
#ipv6
#pppoe

not critical, but mildly annoying that ipv6 almost works completely proper with VyOS and PPPOE for me.

https://forum.vyos.io/t/pppoe-does-not-get-ipv6-address-but-i-do-get-ipv6-prefix-delegation/16598

This week I will be replacing my router (#Ubiquiti #Edgerouter Lite) with an Alta Labs #Route10. The ERL has been great, but there is one specific condition which causes severe performance issues. The ERL can offload #ipv6, #vlan and #pppoe at 1gbs, but not all at once. So, if you try to transfer a lot of ipv6 traffic, it drops to software and it then affects all traffic passing through. The main "culprit" is Steam which prefers ipv6 (as it should!) The new router should not have that limitation.

This week I will be replacing my router (#Ubiquiti #Edgerouter Lite) with an Alta Labs #Route10. The ERL has been great, but there is one specific condition which causes severe performance issues. The ERL can offload #ipv6, #vlan and #pppoe at 1gbs, but not all at once. So, if you try to transfer a lot of ipv6 traffic, it drops to software and it then affects all traffic passing through. The main "culprit" is Steam which prefers ipv6 (as it should!) The new router should not have that limitation.

This week I will be replacing my router (#Ubiquiti #Edgerouter Lite) with an Alta Labs #Route10. The ERL has been great, but there is one specific condition which causes severe performance issues. The ERL can offload #ipv6, #vlan and #pppoe at 1gbs, but not all at once. So, if you try to transfer a lot of ipv6 traffic, it drops to software and it then affects all traffic passing through. The main "culprit" is Steam which prefers ipv6 (as it should!) The new router should not have that limitation.

This week I will be replacing my router (#Ubiquiti #Edgerouter Lite) with an Alta Labs #Route10. The ERL has been great, but there is one specific condition which causes severe performance issues. The ERL can offload #ipv6, #vlan and #pppoe at 1gbs, but not all at once. So, if you try to transfer a lot of ipv6 traffic, it drops to software and it then affects all traffic passing through. The main "culprit" is Steam which prefers ipv6 (as it should!) The new router should not have that limitation.

Hmmmm .... ich glaub meine Fritze macht die Grätsche 🤔

am Tag 2-3 mal PPPOE Fehler ....

Morgen nochmal die config sichern, mal neu starten und bei Bedarf gegen die Ersatzfritze tauschen 🤷

#fritzbox #pppoe #avm

I had a chicken-and-egg #admin problem last week: We have #Vodafone for DSL. They fscked up somewhere on their side, hours before I was about to leave for a short holiday. Instead of screaming into the void hours before leaving I didn‘t call support but waited if it was fixed when I‘m back and just rebooted the router.
It seems #Unifi #USG turns off #pppoe when it‘s not connected and on next reboot doesn‘t load the kernel module.
So Vodafone fixed the problem, but our router did not reconnect.

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?

Es handelt sich um ein bekanntes Phänomen bei FritzBoxen im Zusammenhang mit #IPv6 und #PPPoE

Wenn die IPv6 Einstellungen manuell erfasst werden, funktioniert die #DSL Verbindung stabil.

Danke #Init7 für den schnellen und hilfreichen Support.

Ich habe heute versucht, eine #FritzBox 7582 mit einer FritzBox 7682 abzulösen. Die #DSL Verbindung kommt zu Stande mit der neuen, doch unmittelbar nach Erhalt der IP-Infos erscheint eine Fehlermeldung. Das geht merhmals im Abstand von 5 Sek. so, danach wird die #PPPoE Verbindung gekappt.

Das Firmware-Update hat nicht geholfen.

Mit #FTTH wäre das nicht passiert. Ich mag #FTTS mit #gfast nicht, doch es ist leider das Sinnvollste hier.

Ich werde am Montag bei #Init7 anrufen und um Hilfe fragen.

#PPP 2.5.2 has been released (#pppd / #PointToPointProtocolDeamon / #PointToPointProtocol / #PPPoE / #PPPoA / #PPPoL2TP / #PointToPoint / #InternetProtocol / #IPv4 / #IPv6 / #EAP / #ExtensibleAuthenticationProtocol / #EAPTLS / #EAPMSCHAPv2 / #RADIUS / #SecureRemotePasswordProtocol) https://ppp.samba.org/

#PPP 2.5.2 has been released (#pppd / #PointToPointProtocolDeamon / #PointToPointProtocol / #PPPoE / #PPPoA / #PPPoL2TP / #PointToPoint / #InternetProtocol / #IPv4 / #IPv6 / #EAP / #ExtensibleAuthenticationProtocol / #EAPTLS / #EAPMSCHAPv2 / #RADIUS / #SecureRemotePasswordProtocol) https://ppp.samba.org/

#PPP 2.5.2 has been released (#pppd / #PointToPointProtocolDeamon / #PointToPointProtocol / #PPPoE / #PPPoA / #PPPoL2TP / #PointToPoint / #InternetProtocol / #IPv4 / #IPv6 / #EAP / #ExtensibleAuthenticationProtocol / #EAPTLS / #EAPMSCHAPv2 / #RADIUS / #SecureRemotePasswordProtocol) https://ppp.samba.org/

#PPP 2.5.2 has been released (#pppd / #PointToPointProtocolDeamon / #PointToPointProtocol / #PPPoE / #PPPoA / #PPPoL2TP / #PointToPoint / #InternetProtocol / #IPv4 / #IPv6 / #EAP / #ExtensibleAuthenticationProtocol / #EAPTLS / #EAPMSCHAPv2 / #RADIUS / #SecureRemotePasswordProtocol) https://ppp.samba.org/

New #blog post: Using #OPNsense with 1Gbps FTTP and #PPPoE

We had fiber installed earlier in the week which caused me to unexpectedly need to replace my router.

I switched to a box running OPNsense but ran into some issues with PPPoE throughput

This post talks about how I got our connection running at full-tilt

https://www.bentasker.co.uk/posts/blog/general/opnsense-pfsense-fttp-and-1gbps-pppoe.html

#PPP 2.5.1 has been released (#pppd / #PointToPointProtocolDeamon / #PointToPointProtocol / #PPPoE / #PPPoA / #PPPoL2TP / #PointToPoint / #InternetProtocol / #IPv4 / #IPv6 / #EAP / #ExtensibleAuthenticationProtocol / #EAPTLS / #EAPMSCHAPv2 / #RADIUS / #SecureRemotePasswordProtocol) https://ppp.samba.org/

#PPP 2.5.1 has been released (#pppd / #PointToPointProtocolDeamon / #PointToPointProtocol / #PPPoE / #PPPoA / #PPPoL2TP / #PointToPoint / #InternetProtocol / #IPv4 / #IPv6 / #EAP / #ExtensibleAuthenticationProtocol / #EAPTLS / #EAPMSCHAPv2 / #RADIUS / #SecureRemotePasswordProtocol) https://ppp.samba.org/

#PPP 2.5.1 has been released (#pppd / #PointToPointProtocolDeamon / #PointToPointProtocol / #PPPoE / #PPPoA / #PPPoL2TP / #PointToPoint / #InternetProtocol / #IPv4 / #IPv6 / #EAP / #ExtensibleAuthenticationProtocol / #EAPTLS / #EAPMSCHAPv2 / #RADIUS / #SecureRemotePasswordProtocol) https://ppp.samba.org/

#PPP 2.5.1 has been released (#pppd / #PointToPointProtocolDeamon / #PointToPointProtocol / #PPPoE / #PPPoA / #PPPoL2TP / #PointToPoint / #InternetProtocol / #IPv4 / #IPv6 / #EAP / #ExtensibleAuthenticationProtocol / #EAPTLS / #EAPMSCHAPv2 / #RADIUS / #SecureRemotePasswordProtocol) https://ppp.samba.org/

After explaining the current state of affairs with #IPv6 transition mechanisms, I published a tutorial on how to apply all of that in a real network with @news (#VyOS):

https://blog.daknob.net/ipv6-first-with-vyos/

#IPv6First #IPv6Mostly #PPPoE #DHCPv6PD
https://mastodon.social/@antonis/112246775124361251

Bin ich der Einzige, der sich bei 1&1 seit heute Morgen nicht per DSL einloggen kann?

#1und1 #PPPoE #DSL #Stoerung #Authentifizierung

"Cisco ASR 9000 PPPoE Vulnerability Alert - Denial of Service"

Cisco has identified a high-severity vulnerability (CVE-2024-20327) in the PPPoE feature of IOS XR for ASR 9000 Series Routers, threatening network stability. Unauthenticated attackers can trigger a DoS by sending malformed PPPoE packets to affected routers. Cisco recommends urgent updates as there are no alternative workarounds.🛡️💻

Source: Cisco Security Advisory

Tags: #Cisco #Cybersecurity #DoSVulnerability #NetworkSecurity #PPPoE #CVE2024_20327 #InfoSec #SecurityUpdate

Multiple advisories in March 2024 release of the Cisco IOS XR Software Security Advisory Bundled Publication

https://cdn.marcin-lis.pl/2024/03/th-1442515102.jpg

Multiple advisories in March 2024 release of the Cisco IOS XR Software Security Advisory Bundled Publication:

* Cisco IOS XR Software SSH Privilege Escalation Vulnerability (Security Impact Rating: High)

* Cisco IOS XR Software DHCP Version 4 Server Denial of Service Vulnerability (Security Impact Rating: Medium)

* Cisco IOS XR Software SNMP […]

#cisco #dhcp #DoS #ios #network #pppoe #security #sftp #snmp #ssh #technology #vulnerability

https://marcin-lis.pl/security/multiple-advisories-in-march-2024-release-of-the-cisco-ios-xr-software-security-advisory-bundled-publication/

Ubuntu 上 PPPoE 自動重撥的設定

tl;dr：在設定檔裡面除了 persist 外，還要加上 maxfail 0。

中華 HiNet 家用方案有提供固一動七的 IPv4 address 可以用，我自己因為玩 DevOps/SRE 的項目，有個固定 IPv4 address 弄一台便當盒小主機跑個 Ubuntu 系統當 jump server (跳板機) 總是對於防火牆的設定比較友善。

家用方案的固定 IP 在網

https://blog.gslin.org/archives/2024/02/23/11675/ubuntu-%e4%b8%8a-pppoe-%e8%87%aa%e5%8b%95%e9%87%8d%e6%92%a5%e7%9a%84%e8%a8%ad%e5%ae%9a/

#Computer #Linux #Murmuring #Network #OS #Software #auto #hinet #maxfail #network #persist #pppoe #redial #ubuntu

Ubuntu 上 PPPoE 自動重撥的設定

tl;dr：在設定檔裡面除了 persist 外，還要加上 maxfail 0。

中華 HiNet 家用方案有提供固一動七的 IPv4 address 可以用，我自己因為玩 DevOps/SRE 的項目，有個固定 IPv4 address 弄一台便當盒小主機跑個 Ubuntu 系統當 jump server (跳板機) 總是對於防火牆的設定比較友善。

家用方案的固定 IP 在網

https://blog.gslin.org/archives/2024/02/23/11675/ubuntu-%e4%b8%8a-pppoe-%e8%87%aa%e5%8b%95%e9%87%8d%e6%92%a5%e7%9a%84%e8%a8%ad%e5%ae%9a/

#Computer #Linux #Murmuring #Network #OS #Software #auto #hinet #maxfail #network #persist #pppoe #redial #ubuntu

Ubuntu 上 PPPoE 自動重撥的設定

tl;dr：在設定檔裡面除了 persist 外，還要加上 maxfail 0。

中華 HiNet 家用方案有提供固一動七的 IPv4 address 可以用，我自己因為玩 DevOps/SRE 的項目，有個固定 IPv4 address 弄一台便當盒小主機跑個 Ubuntu 系統當 jump server (跳板機) 總是對於防火牆的設定比較友善。

家用方案的固定 IP 在網

https://blog.gslin.org/archives/2024/02/23/11675/ubuntu-%e4%b8%8a-pppoe-%e8%87%aa%e5%8b%95%e9%87%8d%e6%92%a5%e7%9a%84%e8%a8%ad%e5%ae%9a/

#Computer #Linux #Murmuring #Network #OS #Software #auto #hinet #maxfail #network #persist #pppoe #redial #ubuntu

Ubuntu 上 PPPoE 自動重撥的設定

tl;dr：在設定檔裡面除了 persist 外，還要加上 maxfail 0。

中華 HiNet 家用方案有提供固一動七的 IPv4 address 可以用，我自己因為玩 DevOps/SRE 的項目，有個固定 IPv4 address 弄一台便當盒小主機跑個 Ubuntu 系統當 jump server (跳板機) 總是對於防火牆的設定比較友善。

家用方案的固定 IP 在網

https://blog.gslin.org/archives/2024/02/23/11675/ubuntu-%e4%b8%8a-pppoe-%e8%87%aa%e5%8b%95%e9%87%8d%e6%92%a5%e7%9a%84%e8%a8%ad%e5%ae%9a/

#Computer #Linux #Murmuring #Network #OS #Software #auto #hinet #maxfail #network #persist #pppoe #redial #ubuntu

Ubuntu 上 PPPoE 自動重撥的設定

tl;dr：在設定檔裡面除了 persist 外，還要加上 maxfail 0。

中華 HiNet 家用方案有提供固一動七的 IPv4 address 可以用，我自己因為玩 DevOps/SRE 的項目，有個固定 IPv4 address 弄一台便當盒小主機跑個 Ubuntu 系統當 jump server (跳板機) 總是對於防火牆的設定比較友善。

家用方案的固定 IP 在網

https://blog.gslin.org/archives/2024/02/23/11675/ubuntu-%e4%b8%8a-pppoe-%e8%87%aa%e5%8b%95%e9%87%8d%e6%92%a5%e7%9a%84%e8%a8%ad%e5%ae%9a/

#Computer #Linux #Murmuring #Network #OS #Software #auto #hinet #maxfail #network #persist #pppoe #redial #ubuntu

Ok how does the #sagemcom #gigahub 5689E do 3Gbps wire speed #PPPoE encapsulation when I can't find a 10g #firewall that can do it with less than an i5 in it, at over $1k.

Anyone have a recommendation on a 2 port 10G box for firewall use that can run wire speed PPPoE?

Ok how does the #sagemcom #gigahub 5689E do 3Gbps wire speed #PPPoE encapsulation when I can't find a 10g #firewall that can do it with less than an i5 in it, at over $1k.

Anyone have a recommendation on a 2 port 10G box for firewall use that can run wire speed PPPoE?

Ok how does the #sagemcom #gigahub 5689E do 3Gbps wire speed #PPPoE encapsulation when I can't find a 10g #firewall that can do it with less than an i5 in it, at over $1k.

Anyone have a recommendation on a 2 port 10G box for firewall use that can run wire speed PPPoE?

Ok how does the #sagemcom #gigahub 5689E do 3Gbps wire speed #PPPoE encapsulation when I can't find a 10g #firewall that can do it with less than an i5 in it, at over $1k.

Anyone have a recommendation on a 2 port 10G box for firewall use that can run wire speed PPPoE?

I am considering shifting over from #Rogers #HFC to #Bell #XGSPON

The #PPPoE #ONT noise has given me pause.

I get that #DSL adopted PPPoE because circuit switching underlay (*cough* ATM). It sort of made sense then. Barely.

But what is the justification for continuing PPPoE on *PON networks?

It seems like extra equipment scaling cost & complexity to me.

I am considering shifting over from #Rogers #HFC to #Bell #XGSPON

The #PPPoE #ONT noise has given me pause.

I get that #DSL adopted PPPoE because circuit switching underlay (*cough* ATM). It sort of made sense then. Barely.

But what is the justification for continuing PPPoE on *PON networks?

It seems like extra equipment scaling cost & complexity to me.

I am considering shifting over from #Rogers #HFC to #Bell #XGSPON

The #PPPoE #ONT noise has given me pause.

I get that #DSL adopted PPPoE because circuit switching underlay (*cough* ATM). It sort of made sense then. Barely.

But what is the justification for continuing PPPoE on *PON networks?

It seems like extra equipment scaling cost & complexity to me.

I am considering shifting over from #Rogers #HFC to #Bell #XGSPON

The #PPPoE #ONT noise has given me pause.

I get that #DSL adopted PPPoE because circuit switching underlay (*cough* ATM). It sort of made sense then. Barely.

But what is the justification for continuing PPPoE on *PON networks?

It seems like extra equipment scaling cost & complexity to me.

Spent the last ~week debugging and trying to understand MTU issues with WireGuard on DS-Lite and PPPoE connections with ICMP "black holes", MSS clamping and nftables. Quite the ride! Think I managed to sort of understand things now...

#networking #wireguard #ipv6 #ipv4 #pppoe #dslite