"
Running OPNsense 26.7-amd64 (FreeBSD 15.1-RELEASE-p1) on a Lanner FW-7551A (Intel Atom C2358, Avoton). Fresh install via UFS/MBR (legacy BIOS hardware, no UEFI), serial console.
Symptom: WAN is configured for PPPoE, but the pppoe0 interface never gets created and mpd5 never starts, regardless of method used:
GUI: Interfaces → Devices → Point-to-Point, Link Type PPPoE, Link Interface igb0, valid username/password — created successfully, assigned to WAN under Interfaces → Assignments (confirmed pppoe0 (igb0) - <description> <username> shows correctly there).
configctl interface reconfigure wan returns "OK" but no mpd process starts and ifconfig -a | grep pppoe returns nothing.
Confirmed ng_pppoe.ko was not loaded by default; manually kldload ng_pppoe succeeded, but reconfigure still didn't start mpd.
Ran the full first-boot Setup Wizard (System → Wizard) with PPPoE type + credentials on the WAN step — same result after Apply.
Log evidence (/var/log/system/latest.log, filtered for "ppp"):
opnsense: /usr/local/etc/rc.configure_interface: The command '/sbin/ifconfig pppoe0 inet6 -accept_rtadv -no_dad description 'WAN (wan)' up' returned exit code 1 and the output was "ifconfig: interface pppoe0 does not exist"
opnsense: /usr/local/etc/rc.bootup: [same error]
opnsense: /usr/local/etc/rc.reload_all: Unable to configure nonexistent interface wan (pppoe0)
No mpd-related log entries appear anywhere in the logs — it's as if the step that should generate /var/etc/mpd5.conf and launch mpd5 is silently skipped entirely, even though configd's log shows "Configuring interface wan" being reached.
Confirmed intact:
config.xml has correct <system><primaryconsole> etc. and a valid <ppps><ppp> PPPoE block with working credentials (verified against RB5009's working PPPoE session using the same ISP/credentials)
Physical WAN link is up (igb0 shows carrier when connected)
/var/etc/mpd5.conf never gets created — file doesn't exist even after reconfigure
Has anyone seen mpd5/pppoe0 fail to initialize like this? Any pointers on which backend script is responsible for generating mpd5.conf and starting the daemon so I can check permissions/dependencies directly?
Symptom: WAN is configured for PPPoE, but the pppoe0 interface never gets created and mpd5 never starts, regardless of method used:
GUI: Interfaces → Devices → Point-to-Point, Link Type PPPoE, Link Interface igb0, valid username/password — created successfully, assigned to WAN under Interfaces → Assignments (confirmed pppoe0 (igb0) - <description> <username> shows correctly there).
configctl interface reconfigure wan returns "OK" but no mpd process starts and ifconfig -a | grep pppoe returns nothing.
Confirmed ng_pppoe.ko was not loaded by default; manually kldload ng_pppoe succeeded, but reconfigure still didn't start mpd.
Ran the full first-boot Setup Wizard (System → Wizard) with PPPoE type + credentials on the WAN step — same result after Apply.
Log evidence (/var/log/system/latest.log, filtered for "ppp"):
opnsense: /usr/local/etc/rc.configure_interface: The command '/sbin/ifconfig pppoe0 inet6 -accept_rtadv -no_dad description 'WAN (wan)' up' returned exit code 1 and the output was "ifconfig: interface pppoe0 does not exist"
opnsense: /usr/local/etc/rc.bootup: [same error]
opnsense: /usr/local/etc/rc.reload_all: Unable to configure nonexistent interface wan (pppoe0)
No mpd-related log entries appear anywhere in the logs — it's as if the step that should generate /var/etc/mpd5.conf and launch mpd5 is silently skipped entirely, even though configd's log shows "Configuring interface wan" being reached.
Confirmed intact:
config.xml has correct <system><primaryconsole> etc. and a valid <ppps><ppp> PPPoE block with working credentials (verified against RB5009's working PPPoE session using the same ISP/credentials)
Physical WAN link is up (igb0 shows carrier when connected)
/var/etc/mpd5.conf never gets created — file doesn't exist even after reconfigure
Has anyone seen mpd5/pppoe0 fail to initialize like this? Any pointers on which backend script is responsible for generating mpd5.conf and starting the daemon so I can check permissions/dependencies directly?
