I don't know exactly what's wrong, it's been a while since I setup the network for this.
I have a VLAN on 201 and PPPoE setup (century link ISP).
This has worked fine for some time, and it works with kernel:
vmlinuz-6.2.9-200.fc37.x86_64
But fails with the most recent kernel:
vmlinuz-6.2.10-200.fc37.x86_64
Any hints or pointers to open issues for this?
My redacted nmcli config file /etc/NetworkManager/system-connections/pppoe-clpppoe.nmconnection has:
My [connection] id=pppoe-clpppoe uuid=cc4f254d-9a7c-43de-8096-74d9c5eb6946 type=pppoe interface-name=clpppoe timestamp=1673535574 zone=umbrella_wan
[ethernet]
[ppp] mtu=1492
[pppoe] parent=vlan201 password=redacted username=redacted@centurylink.net
[ipv4] dns=127.0.0.1; dns-search=example.org; ignore-auto-dns=true method=auto
[ipv6] addr-gen-mode=stable-privacy ip6-privacy=0 method=disabled
[proxy]
Thanks ...
-- Patrick
On Mon, Apr 17, 2023 at 08:02:34AM -0700, Patrick Mansfield via users wrote:
I don't know exactly what's wrong, it's been a while since I setup the network for this.
I have a VLAN on 201 and PPPoE setup (century link ISP).
This has worked fine for some time, and it works with kernel:
vmlinuz-6.2.9-200.fc37.x86_64But fails with the most recent kernel:
vmlinuz-6.2.10-200.fc37.x86_64Any hints or pointers to open issues for this?
Opened a bug for this:
https://bugzilla.redhat.com/show_bug.cgi?id=2187869
-- Patrick
On Tue, Apr 18, 2023 at 07:40:40PM -0700, Patrick Mansfield via users wrote:
On Mon, Apr 17, 2023 at 08:02:34AM -0700, Patrick Mansfield via users wrote:
I don't know exactly what's wrong, it's been a while since I setup the network for this.
I have a VLAN on 201 and PPPoE setup (century link ISP).
This has worked fine for some time, and it works with kernel:
vmlinuz-6.2.9-200.fc37.x86_64But fails with the most recent kernel:
vmlinuz-6.2.10-200.fc37.x86_64Any hints or pointers to open issues for this?
Opened a bug for this:
It looks like network naming got fixed with kernel v6.2.10: I had previously setup to name a particular interface but apparently that was not working, so I used the default name.
Kernel v6.2.10 looks to have fixed the problem, so I had to switch back to my now properly named network interface and it's now working.
Closed the bug.
-- Patrick