Bug 2187869 - VLAN with PPPoE does not work
Summary: VLAN with PPPoE does not work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 37
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-19 01:15 UTC by Patrick Mansfield
Modified: 2023-04-22 18:56 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-04-22 18:56:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Patrick Mansfield 2023-04-19 01:15:39 UTC
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/112.0
Build Identifier: 

I have a network that uses VLAN 201 and PPPoE, with kernel 6.2.9-200.fc37.x86_64 it works fine, but with kernel 6.2.10-200.fc37.x86_64 the inerface does not come up.

Reproducible: Always

Steps to Reproduce:
1. Setup VLAN 201 and PPPoE on a network interface

My NM config file (with password and email modified) /etc/NetworkManager/system-connections/pppoe-clpppoe.nmconnection has:


[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=example
username=example

[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]



Actual Results:  
Network fails to come up, it fails with:

Apr 17 06:42:14 umbrella NetworkManager[1312]: <info>  [1681738934.9325] audit: op="connection-activate" uuid="cc4f254d-9a7c-43de-8096-74d9c5eb6946" name="pppoe-clpppoe" result="fail" reason="Failed to find a compatible device for this connection"


Expected Results:  
Network comes up and is usable.

I looked for open bugs but didn't find any.

I'm not sure what other config and log files to attach - let me know if other details are needed.

Using the older kernel avoids the problem, so I assume it's a kernel change causing the problem.

The actual network device shows up, so it seems to be an issue with the VLAN or PPPoE.

Comment 1 Patrick Mansfield 2023-04-22 18:54:36 UTC
OK, it was a netork naming issue.

It looks like I had added the file /etc/systemd/network/10-wan0.link a while ago to name a network, but it didn't work so I used the default name.

But now the kernel has changed, and it's renaming the network again - I had to switch to the named network and it worked again.

I don't see anything in the Fedora kernel changelog, it must be a change in the base kernel from v6.2.9 to v6.2.10.

Comment 2 Patrick Mansfield 2023-04-22 18:56:02 UTC
Marking this closed, as it looks like there was an incompatible change that fixed a bug.


Note You need to log in before you can comment on or make changes to this bug.