• 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

  • Netgate Administrator

    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


  • @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

  • Netgate Administrator

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


  • @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!

  • Netgate Administrator

    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?


  • @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.

  • Netgate Administrator

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


  • @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:

    1. I save the lan settings:

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

    1. after that came this:
      vlan0: changing name to 'igb1.7'

    2. I hit the Connect Button (without hitting the Button the connection dont get back) in interfaces:
      ng0: changing name to 'pppoe0'

    3. and internet connection came back.

    ๐Ÿ™„

  • Netgate Administrator

    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....


  • @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.

  • Netgate Administrator

    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


  • @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!

  • Netgate Administrator

    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


  • @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.

  • Netgate Administrator

    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


  • @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)

  • Netgate Administrator

    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


  • @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?

  • Netgate Administrator

    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


  • @stephenw10 said in Problem with pppoe over vlan:

    Mmm, exactly Snort applies promiscuous mode when it starts.

    What happens if you just restart Snort?

    Snort restarts without any issue.

    What interfaces do you have Snort running on?

    WAN interface only.

    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....

    Thanks, a lot!

    Here are all the pkgs I use: Cron, iftop, iperf, LCDproc, nmap, pfBlockerNG-devel, RRD_Summary, Shellcmd, snort

  • Netgate Administrator

    Hmm, I can't replicate seeing the NIC link go down however I try to apply it....


  • @stephenw10 said in Problem with pppoe over vlan:

    Hmm, I can't replicate seeing the NIC link go down however I try to apply it....

    I crashed myself my head - I have no clou where to set the axe ... definitiv clear is that every time I save a interface (without any changes) (LAN or WIFI or the OPT2 igb1-temporary created) the vlan gets remade ... and that kills the pppoe!

  • Netgate Administrator

    Yup. I see it it happening for you I just can't re-create it here...yet.


  • @stephenw10 said in Problem with pppoe over vlan:

    Yup. I see it it happening for you I just can't re-create it here...yet.

    Thanks for not giving up! ๐Ÿ‘ ๐Ÿ‘


  • @stephenw10

    Hi anything new in this problem? Just asking! ๐Ÿ˜Š

    Regards,
    fireodo

  • Netgate Administrator

    No I've been unable to replicate it. Something you have set there is causing the NIC to flap and I'm not sure what.
    We might need to review your config somehow...

    Steve


  • @stephenw10 said in Problem with pppoe over vlan:

    No I've been unable to replicate it. Something you have set there is causing the NIC to flap and I'm not sure what.
    We might need to review your config somehow...

    Steve

    OK, understood!

    Thanks anyway!
    fireodo


  • This post is deleted!

  • @stephenw10

    BTW: I set up a identical machine (APU2C0) with a fresh pfsense 2.4.5-RELEASE-p1 with no other packages and the behavior is exactly like my productive pfsense. Saving the LAN(igb0) or the WIFI(ath0_wlan0) interface without any changes made, make the vlan to be remade! (Vlan is on igb1). Anyway seems I have to live with it ๐Ÿ˜ข

  • Netgate Administrator

    Hmm, wondering if it's because of the bridge maybe... Though without igb1 in the bridge you would not expect that to hit WAN...


  • @stephenw10 said in Problem with pppoe over vlan:

    Hmm, wondering if it's because of the bridge maybe... Though without igb1 in the bridge you would not expect that to hit WAN...

    igb1 is not in the bridge. The bridge is between LAN (igb0) and WIFI (ath0_wlan0). igb1 has no interface assign on it (only the vdsl-modem is connected to it) and is only parent for vlan7 and pppoe connects via vlan7.

    Regards and fine weekend,
    fireodo

  • Netgate Administrator

    Yes, exactly. Without igb1 in the bridge I wouldn't expect to see changes made to the wifi interface affect it.
    But I'm unable to replicate it. The interfaces do not lose link and come back up when you make a change. Even on the interface you apply the change to.
    You must have something in your config that is applying a setting to all interfaces everytime they are reloaded. Like maybe putting them in promiscuous mode for monitoring. I could imagien iftop or snort doing that. I did test Snort though.

    Anyway this is not a problem with PPPoE over VLANs, not specifically at least. The VLAN is being rebuilt here because the parent interface is flapping.

    Steve


  • @stephenw10 said in Problem with pppoe over vlan:

    Yes, exactly. Without igb1 in the bridge I wouldn't expect to see changes made to the wifi interface affect it.
    But I'm unable to replicate it. The interfaces do not lose link and come back up when you make a change. Even on the interface you apply the change to.
    You must have something in your config that is applying a setting to all interfaces everytime they are reloaded. Like maybe putting them in promiscuous mode for monitoring. I could imagien iftop or snort doing that. I did test Snort though.

    Anyway this is not a problem with PPPoE over VLANs, not specifically at least. The VLAN is being rebuilt here because the parent interface is flapping.

    Steve

    This is maybe an explication for my "productivity" pfsense but not for the clean install pfsense on the the secondary machine - there is no snort or anything else like that.

    In the mean time I get a vdsl-modem who is setting the tag 7 (neccessary for getting a connection on my provider) so I dont need the pfsense vlan7 anymore. Now I can store any interface without loosing connection! (but the vlan7 gets still renewed every time - I didnt deleted the vlan7 because I will observe in the future whats going on with it) So this is my personal "workaround".

    Maybe you cannot reproduce the situation because of running pfsense in a VM? Just a supposition ...

    Regards and thanks,
    fireodo

  • Netgate Administrator

    No, I've tested a number of different hardware devices too. No insight at this point.


  • @stephenw10 said in Problem with pppoe over vlan:

    No, I've tested a number of different hardware devices too. No insight at this point.

    That let me "speechless" - as you can imagine I crushed my head long time before writing in the forum because I dont want to steal the time from nobody, with a problem that I can solve myself, but I did not find a hook from where the problem may be get solved.

  • Netgate Administrator

    Try just doing a basic install and testing this. Add the parts of you config one at a time until the issue shows up.

    Steve


  • @stephenw10 said in Problem with pppoe over vlan:

    Try just doing a basic install and testing this. Add the parts of you config one at a time until the issue shows up.

    Steve

    Thats what I have done on the secondary machine - just basic setup and the vlan7 problem was there.

  • Netgate Administrator

    Was it dropping the link on the parent NIC without the VLAN on there? Just a basic WAN and LAN config? And that wasn't on an APU?


  • @stephenw10 said in Problem with pppoe over vlan:

    Was it dropping the link on the parent NIC without the VLAN on there? Just a basic WAN and LAN config? And that wasn't on an APU?

    The parent link wasnt dropped. Only the vlan was renewed. Yes only Lan and Wan. It was a identic APU like my productive system (APU2C0)