Problem with pppoe over vlan

fireodo

Hi there,

I am on 2.4.5-RELEASE-p1 and I have a similar issue as in this thread: pfsense 2.4.4 fails all pppoe's after disabling one. The WAN (pppoe) is on igb1.7 (igb1 with Vlan 7).
If I only save the settings (for example) on the Wireless (ath0_wlan0) Interface (without changing anything) the Wan goes down and don't come up same as in all the examples in this thread pfsense 2.4.4 fails all pppoe's after disabling one. What has the Wireless interface to do with the Wan pppoe connection?
In the log file I found that in the moment I saved the settings on the wireless interface something caused this:
"vlan0: changing name to 'igb1.7' " (the vlan seems to be deleted and remade) It seems that in this moment the pppoe is "in the air" (it tries to keep connection to an inexistent interface). When I manually hit the "Connect" button the pppoe-connection get back without problems. I have done this a few times to be sure it is reproductible.

Regards,
fireodo

stephenw10

Hmm, that was exactly what that patch should have fixed. I use PPPoE over VLANs and am not seeing that.....

You see the same errors, like?:

Nov 26 12:23:44	ppp		[wan_link0] can't remove hook mpd63022-0 from node "[52]:": No such file or directory
Nov 26 12:23:44	ppp		[wan_link0] PPPoE: can't connect "[52]:"->"mpd63022-0" and "[8d]:"->"left": No such file or directory

Is your wifi interface bridged to igb1 maybe?

Steve

fireodo

@stephenw10 said in Problem with pppoe over vlan:

Hmm, that was exactly what that patch should have fixed. I use PPPoE over VLANs and am not seeing that.....

You see the same errors, like?:
Nov 26 12:23:44	ppp		[wan_link0] can't remove hook mpd63022-0 from node "[52]:": No such file or directory
Nov 26 12:23:44	ppp		[wan_link0] PPPoE: can't connect "[52]:"->"mpd63022-0" and "[8d]:"->"left": No such file or directory

Yes, this kind of errors has brought me to my initial search (where I found the threads in my original post).

Aug  8 15:30:40  ppp: [wan_link0] PPPoE: can't connect "[25c]:"->"mpd82722-0" and "[25a]:"->"left": No such file or directory
Aug  8 15:30:40  ppp: [wan_link0] can't remove hook mpd82722-0 from node "[25c]:": No such file or directory

Is your wifi interface bridged to igb1 maybe?

No, the wifi (ath0_wlan0) is bridged to igb0 (Lan)
There is nothing else bound to igb1 (except vlan7 and of course pppoe)

Steve

Thanks,
fireodo

stephenw10

Hmm, do you see the code from that patch on your system?
https://github.com/pfsense/pfsense/commit/433a8e71f3b68c39634e11b62d8bf3d9e8ec878c.patch

fireodo

@stephenw10 said in Problem with pppoe over vlan:

Hmm, do you see the code from that patch on your system?
https://github.com/pfsense/pfsense/commit/433a8e71f3b68c39634e11b62d8bf3d9e8ec878c.patch

Yes - i checked that in the interfaces.inc before posting my issue!

stephenw10

Hmm, curious. Something you have configured must be matching the code that requires the parent to be re-configured. You have anything else on igb1?

fireodo

@stephenw10 said in Problem with pppoe over vlan:

Hmm, curious. Something you have configured must be matching the code that requires the parent to be re-configured. You have anything else on igb1?

No, only vlan7 and the pppoe bound on vlan7.

stephenw10

Hmm, is it any change to any other interface that triggers it?

fireodo

@stephenw10 said in Problem with pppoe over vlan:

Hmm, is it any change to any other interface that triggers it?

Yes, I made a test now, only saving the LAN Settings (without changing anything) and I had the same behaviour and this also:

Aug 17 18:22:39	ppp		[wan_link0] can't remove hook mpd72282-0 from node "[13]:": No such file or directory
Aug 17 18:22:39	ppp		[wan_link0] PPPoE: can't connect "[13]:"->"mpd72282-0" and "[6fa]:"->"left": No such file or directory

and here (from dmesg) in order of actions:

I save the lan settings:

igb0: link state changed to DOWN
igb0: link state changed to UP

after that came this:
vlan0: changing name to 'igb1.7'
I hit the Connect Button (without hitting the Button the connection dont get back) in interfaces:
ng0: changing name to 'pppoe0'
and internet connection came back.

stephenw10

Hmm, I can't replicate that. Though interestingly the box I'm testing on (my home edge device) has all its interfaces, including pppoe, as VLANs on the same lagg0 parent. You might expect it to force a vlan reload in the situation but it does not....

fireodo

@stephenw10 said in Problem with pppoe over vlan:

Hmm, I can't replicate that. Though interestingly the box I'm testing on (my home edge device) has all its interfaces, including pppoe, as VLANs on the same lagg0 parent. You might expect it to force a vlan reload in the situation but it does not....

Its strange because I have nothing special here and i have not made any change to the pfsense Installation - its a simply firewall-router with a few packages (see signature). The vlan7 on the pppoe is required by the Internet-Provider.
Hmmmm

PS. Until a few weeks I have used my pfsense without vlan7 thats why the problem had not occured in the past (I suppose).

PPS. I have now, made an extra check of the patch pppoe-patch
and it confirms that the patch is allready on the system.

stephenw10

On other test systems where I have VLANs on different parent interfaces they are not rebuilt:

Aug 18 14:10:46 	check_reload_status 	425 	Syncing firewall
Aug 18 14:10:53 	check_reload_status 	425 	Restarting ipsec tunnels
Aug 18 14:10:56 	check_reload_status 	425 	updating dyndns lan
Aug 18 14:10:58 	check_reload_status 	425 	Reloading filter

That's resaving LAN with no changes.....

Either not all that patch code is in your system somehow or you config is triggering the VLAN rebuild with something. Hmm

fireodo

@stephenw10 said in Problem with pppoe over vlan:

On other test systems where I have VLANs on different parent interfaces they are not rebuilt:
Aug 18 14:10:46 	check_reload_status 	425 	Syncing firewall
Aug 18 14:10:53 	check_reload_status 	425 	Restarting ipsec tunnels
Aug 18 14:10:56 	check_reload_status 	425 	updating dyndns lan
Aug 18 14:10:58 	check_reload_status 	425 	Reloading filter 
That's resaving LAN with no changes.....

Either not all that patch code is in your system somehow or you config is triggering the VLAN rebuild with something. Hmm

Hi Steve, would you mind to send me your interfaces.inc and interfaces.php? Thanks a lot!

stephenw10

Hmm, one thing I notice here is that the igb0 link goes down when you saved that. That would not normally happen if you save an interface without changing anything.
I assume igb0 is your LAN there? What settings do you have on that interface?

Steve

fireodo

@stephenw10 said in Problem with pppoe over vlan:

Hmm, one thing I notice here is that the igb0 link goes down when you saved that. That would not normally happen if you save an interface without changing anything.
I assume igb0 is your LAN there? What settings do you have on that interface?

Steve

Look:
Lan.png.jpg

I also downloaded the original files from github

https://github.com/pfsense/pfsense/blob/RELENG_2_4_5/src/etc/inc/interfaces.inc

https://github.com/pfsense/pfsense/blob/RELENG_2_4_5/src/usr/local/www/interfaces.php

and have compared with mine and they are identical.

stephenw10

Do you have Snort or Suricata running? That can cause interfaces to reconnect sometimes. In in-line mode perhaps.

If you assign/enable igb1 does that also go down/up when you resave LAN?

Steve

fireodo

@stephenw10 said in Problem with pppoe over vlan:

Do you have Snort or Suricata running? That can cause interfaces to reconnect sometimes. In in-line mode perhaps.

Yes, i have Snort but not in in-line mode.

If you assign/enable igb1 does that also go down/up when you resave LAN?

igb1 is assigned to vlan7 and to pppoe ...

Steve

PS. Its only the vlan that get renewed, igb1 is left untouched.
In conclusion - when settings are applied (in my case) on LAN (igb0) or WiFi (ath0_wlan0) only the vlan gets affected! (When applying settings on LAN (igb0) its normal that igb0 go down/up)

stephenw10

Right, but I'm saying if you assign igb1 as a new interface and enable it with no config but just so it's up does that also go down when you make a change. That would explain why the vlan is rebuilt, but not why igb1 goes down.

Steve

fireodo

@stephenw10 said in Problem with pppoe over vlan:

Right, but I'm saying if you assign igb1 as a new interface and enable it with no config but just so it's up does that also go down when you make a change. That would explain why the vlan is rebuilt, but not why igb1 goes down.

Steve

Yes it also goes down, here the dmesg output:

igb1: link state changed to DOWN
igb1.7: link state changed to DOWN
igb1: link state changed to UP
igb1.7: link state changed to UP
vlan0: changing name to 'igb1.7'

PS. Maybe its helpful to know that my system was continuously updatet from 2.4.3 (I'm using pfsense longer but 2.4.3 was a fresh install with config recovery)

PPS. Another Idea: Snort needs interfaces in promiscuous mode - could that be a possible culprit?

stephenw10

Mmm, exactly Snort applies promiscuous mode when it starts.

What happens if you just restart Snort?

What interfaces do you have Snort running on?

It looks like the VLAN here is correctly being recreated because the parent interface is brought down. That's why I can't replicate it here. I'll try with Snort....

Steve