Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - fanski

#1
Quote from: franco on November 12, 2026, 08:38:54 PMThe order of the patching is wrong though:

> 4. upgraded to 26.7.9

As soon as you upgrade the local patches get lost.  The sequence is:

1. Update to 26.7.9.
2. run patch command once which does everything for you: # opnsense-patch 39cca4ca785

Yes, I didn't run the patch at all, I just did a dry-run to see the output (output was hunk 2 did not work in 26.7.1) and then did the upgrade and it directly worked but as I said, I did the same update yesterday and the result was different so I'm totally confused.

I installed the patch now and it still works.

Regards,

Fanski
#2
Hi Franco,

so I don't know how to say this but yes. It's working now, but I don't really know why, because I didn't install the patch...
I did this:

1. download the patch with opnsense-patch -d 39cca4ca785
2. copied the patch from /var/cache/opnsense-patch/core-39cca4ca785 to /root/39cca4ca785.patch
3. checked if the patch is working with  patch -d /usr/local -p2 --dry-run < /root/39cca4ca785.patch
4. upgraded to 26.7.9
5. reload
6. PPPoE working again

I have no idea why it works now because I did the upgrade to 26.7.9 yesterday and it didn't work. I checked the /usr/local/etc/inc/interfaces.inc and searched for example for "PPP start deferred" which was not in it so I guess I didn't have the patch installed, except it is somehow used during boot in a cache???

But hey: YES!! it's working :D
I also did some reboots to be sure that it will still work and everything is fine now.

I checked the logs and maybe the source of the problem is here:

not working
<13>1 2026-11-11T19:49:05+01:00 fw-KG.XYZ opnsense 441 - [meta sequenceId="213"] /usr/local/etc/rc.bootup: Device vlan0.35 required by WAN(wan), configuring now
<13>1 2026-11-11T19:49:05+01:00 fw-KG.XYZ kernel - - [meta sequenceId="214"] <118>[30] Configuring Uplink_switch_KG_10G interface...done.
<13>1 2026-11-11T19:49:05+01:00 fw-KG.XYZ kernel - - [meta sequenceId="215"] <6>[30] ix1: link state changed to UP
<13>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ kernel - - [meta sequenceId="216"] <6>[30] igb0: link state changed to DOWN
<13>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ kernel - - [meta sequenceId="217"] <6>[30] vlan0: changing name to 'vlan0.35'
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="218"] Multi-link PPP daemon for FreeBSD
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="219"]
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="220"] process 54366 started, version 5.9
<13>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ kernel - - [meta sequenceId="221"] <118>[31] Configuring WAN interface...
<13>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ kernel - - [meta sequenceId="222"] <6>[31] igb1: link state changed to UP
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="223"] web: web is not running
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="224"] [wan] Bundle: Interface ng0 created
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="225"] [wan_link0] Link: OPEN event
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="226"] [wan_link0] LCP: Open event
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="227"] [wan_link0] LCP: state change Initial --> Starting
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="228"] [wan_link0] LCP: LayerStart
<13>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ kernel - - [meta sequenceId="229"] <6>[31] ng0: changing name to 'pppoe0'
<29>1 2026-11-11T19:49:06+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="230"] [wan_link0] PPPoE: Connecting to ''
<13>1 2026-11-11T19:49:10+01:00 fw-KG.XYZ kernel - - [meta sequenceId="231"] <6>[35] igb0: link state changed to UP
<13>1 2026-11-11T19:49:10+01:00 fw-KG.XYZ kernel - - [meta sequenceId="232"] <6>[35] vlan0.35: link state changed to UP
<29>1 2026-11-11T19:49:15+01:00 fw-KG.XYZ ppp 54366 - [meta sequenceId="233"] [wan_link0] PPPoE connection timeout after 9 seconds

working
<13>1 2026-11-12T18:59:11+01:00 fw-KG.XYZ opnsense 435 - [meta sequenceId="213"] /usr/local/etc/rc.bootup: Device vlan0.35 required by WAN(wan), configuring now
<13>1 2026-11-12T18:59:11+01:00 fw-KG.XYZ kernel - - [meta sequenceId="214"] <118>[32] Configuring Uplink_switch_KG_10G interface...done.
<13>1 2026-11-12T18:59:11+01:00 fw-KG.XYZ kernel - - [meta sequenceId="215"] <6>[32] ix1: link state changed to UP
<13>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ kernel - - [meta sequenceId="216"] <6>[32] igb0: link state changed to DOWN
<13>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ kernel - - [meta sequenceId="217"] <6>[32] vlan0: changing name to 'vlan0.35'
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="218"] Multi-link PPP daemon for FreeBSD
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="219"]
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="220"] process 62154 started, version 5.9
<13>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ kernel - - [meta sequenceId="221"] <6>[33] igb1: link state changed to UP
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="222"] web: web is not running
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="223"] [wan] Bundle: Interface ng0 created
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="224"] [wan_link0] Link: OPEN event
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="225"] [wan_link0] LCP: Open event
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="226"] [wan_link0] LCP: state change Initial --> Starting
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="227"] [wan_link0] LCP: LayerStart
<13>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ kernel - - [meta sequenceId="228"] <118>[33] Configuring WAN interface...
<13>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ kernel - - [meta sequenceId="229"] <6>[33] ng0: changing name to 'pppoe0'
<29>1 2026-11-12T18:59:12+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="230"] [wan_link0] PPPoE: Connecting to ''
<13>1 2026-11-12T18:59:16+01:00 fw-KG.XYZ kernel - - [meta sequenceId="231"] <6>[37] igb0: link state changed to UP
<13>1 2026-11-12T18:59:16+01:00 fw-KG.XYZ kernel - - [meta sequenceId="232"] <6>[37] vlan0.35: link state changed to UP
<29>1 2026-11-12T18:59:18+01:00 fw-KG.XYZ ppp 62154 - [meta sequenceId="233"] PPPoE: rec'd ACNAME "Bras-gare-100g"

The part "Configuring WAN interface" now starts later, after we have some wan/wan_link0 messages.

If needed I can provide more logs. But for now many many thanks for your help!

Regards,

Fanski
#3
Hi Franco,

I tested it with 26.7.9 and it still has the same behavior. So if I can help with testing just give me a hint what to do :)

Many thanks,

Fanski
#4
Quote from: franco on October 13, 2026, 12:15:51 PMHi fanski,

> In 26.7.1 the vlan0.35 was not the first VLAN to be created.

Previously the VLANs were created in a batch before interfaces were brought up, but that changed in .3 with the support of VLANs on top of bridges.

We haven't seen many oddities, but there were a few.  Some hidden in the old code and some apparently in drivers.  I need to recheck the code I gave you, but it feels like the kernel is lying to us here.

At the moment I need to release 26.7.7 though so I'll try to get back to this later this week.


Cheers,
Franco

Hi Franco,

I guess you are really busy at the moment, I just wanted to ask if you think you will have the time to look at this again or if you see another option?
Currently I'm a little bit blocked with my VoIP as it's not working without the siproxd which seems not available in version 26.7.1 (OPNSense tells me to upgrade to get the plugin running again and I need it as my ISP is not really accepting STUN as it seems because I can't login anymore after some time). And additionally I would really like to keep my software up to date, especially the firewall :)

Many thanks,

Fanski
#5
QuoteIt looks like something is broken in LCP/PAP (ppp[72477]: [wan_link0] LCP: auth: peer wants PAP, I want nothing).

Hi GOJ,

not sure if this is really a problem of OPNSense.
I have the same with my 26.7.1 where the connection is working.

The problem is more the "ppp[72477]: [wan_link0]   MESG: Access Denied" message I guess where your provider denies your access for whatever reason.
Also it isn't the same issue I have as my PPPoE doesn't even start, yours is working. At least you are connecting to your provider while mine just times out.
Not sure but maybe there is something wrong with the access to your provider?

Regards,

Fanski
#6
Hi Franco,

still not coming up :(

So I upgraded again to 26.7.6_3, installed patch 3384e551f3 and reboot, then patch d2ad94b38b48 and reboot and then patch 212185a8be and reboot but unfortunately it's still the same behavior.

Maybe just a short question:
In 26.7.1 the vlan0.35 was not the first VLAN to be created. In the following versions it is always is the first one/vlan0, all the other VLANs created later seem to work without a problem. Is there a possibility switch the order again (maybe it's just the first one which is created which has problems)? Or is this a mandatory behavior that the VLAN attached to the WAN interface always needs to be the first to be created?

Regards,

Fanski
#7
Hi Franco,

so I tried with 5, 10 and 15 seconds but no success.
I changed this (log message was just for me to be sure where this happens and if it works :) ):

/* wait for functional parent (only the first) */
    $max = 10;
    $i = 0;
    while ($i < $max) {

        sleep(15);
        log_msg("sleeping", LOG_WARNING);
        if (does_interface_exist($ports[0], 'up')) {
            break;
        }
        $i++;
    }

I'm just curious, do you think this could be hardware related? I use an old firewall for my setup. It was for free so for my home config it was good enough.I thought maybe the old hardware is not working properly with the new firmware/something in the modern architecture is causing this issue with my old hardware.

Regards,

Fanski
#8
No I did it in that order:

1. download the patch with opnsense-patch -d 3384e551f3
2. copied the patch to /root/3384e551f3.patch
3. checked if the patch is working with  patch -d /usr/local -p2 --dry-run < /root/3384e551f3.patch
4. upgraded to 26.7.6_3
5. PPPoE was not working so i used this command patch -d /usr/local -p2 < /root/3384e551f3.patch
6. did a reboot
7. PPPoE was still not working so I checked /usr/local/etc/inc/interfaces.inc if the lines written in the patch are in there. They were there so I guessed the patch was working
8. did a second reboot and reloaded the ONT to be sure it's not another problem, but that didn't help

Maybe I did something wrong or need to activate something additionally?
But back in 26.7.1 the lines aren't in the interfaces.inc anymore so I'm pretty sure it was at least updated.
Is there something else I can check if to see if the patch is correctly installed?

Regards,

Fanski
#9
Hi Franco,

unfortunately it seems the hammer was not big enough?!

The problem still exists after upgrading to 26.7.6_3 and with the patch installed.
Or should I have only upgraded to 26.7.5?

Regards,

Fanski
#10
Hi Franco,

Quote from: franco on October 06, 2026, 11:15:17 AMHmm, I'm assuming your WAN sits on top of igb0?
so yes the ONT is connected to igb0.

Quote from: franco on October 06, 2026, 11:48:51 AMcan you try to set "VLAN Hardware Filtering" on Interfaces: Settings to "Leave default" and reboot.
did that and unfortunately it didn't solve the issue. still the same behavior. I also tested it with 26.7.1 and at first everything was working except the internet traffic because of state violations, but after playing with the 3 different options and 3 or 4 reboots it worked without a problem and also after some reboots.

Quote from: franco on October 06, 2026, 11:15:17 AMCan you try to add igb0 to a new interface and simply enable it without doing any other settings? Then try a reboot and see if the problem persists.
I think I already tried this before once or twice as it was a suggested workaround, but I tried again and also with the VLAN Hardware Filtering disabled or leave default but this also had no positive effect.

I attached the logs with the VLAN Hardware Filtering default option, and the ones with the dummy interface.

Regards,

Fanski
#11
Hello Franco,

I uploaded the old and the new output of this command.

Hope this helps.

Regards,

Fanski
#12
Hi,

I have a very similar problem and hope it's ok to reply to this topic, otherwise I can also open a new one.

So when on 26.7.1 my PPPoE config works fine and the connection comes up. I get an IP from the ISP etc and there is no problem as far as I can see.
But if I'm upgrading to 26.7.5 (I also tried to upgrade to 26.7.4 and 26.7.4_1 before multiple times) the PPPoE always fails. The interfaces are up and if I check the Interface Overview/assignments/etc. everything looks the same for me but I don't get a public IP and the status of the WAN interface on the Dashboard is active but "undefined".

I did some research with AI (in fact Claude, ChatGPT and Gemini) and after I tried all the suggested workarounds the AI always comes to the conclusion this must be a bug.
I'm not sure if this is really true because you know AI always sounds pretty sure about everything but isn't always right and after some research I also read a lot about most problems are more config errors than bugs so I guess this is maybe more my problem.

So from the log I can see that the PPPoE just doesn't work, but I'm not sure why. If I do a diff between 26.7.1 log and 26.7.5 log I can see the order of the log messages regarding the WAN interface and PPPoE is a little different but everything happens at the same second. For the AI this is the root cause as the order has to be different and this is a key problem for my config. But as I already mentioned I'm not really sure about this.

Another potential problem according to the AI is that I have 2 10G interfaces for internal traffic and the WAN interface is only a 1G interface. The AI tells me this is a big problem as the 10G interfaces are seen as priority interfaces and the OPNSense tries to connect via those interfaces instead of the 10G which then fails. But I can't see any hint of that in the log files.

I tried to follow the How To Guide about PPPoE over VLAN but it's already 5 years old and I'm not sure if this is still correct after all those years.

Maybe someone can help me, because I now spent so many hours on that problem that I don't know what options are left to solve this issue.

Many thanks in advance.