[SOLVED] Since upgrade to 22.1.8 PPPoe not working anymore

[rcmcronny]

Hi,

i use this dsl line only as backup and noticed, that it was down. The mpd shows only tries, but not response. So i thought, its the fault of the isp.  But no infos on this. The sync is there, all seems right. I configured my vigor 130 to use its own pppoe client and this worked immedially. 
Searched the logs and its really since the update to 22.1.8 , bevor the pppoe session worked.

The night bevor the update (around 2am) all worked:

Code: [Select]

<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="141"] [wan] IFACE: Up event
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="142"] [wan] IFACE: Rename interface ng0 to pppoe0
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="143"] [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="144"] [wan]   IPADDR xx.xx.xx.xxx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="145"] [wan]     xx.xx.xx.xx is OK
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="146"] [wan]   PRIDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="147"] [wan]   SECDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="148"] [wan] IPCP: SendConfigReq #3
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="149"] [wan]   IPADDR xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="150"] [wan]   PRIDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="151"] [wan]   SECDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="152"] [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="153"] [wan]   IPADDR xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="154"] [wan]   PRIDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="155"] [wan]   SECDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="156"] [wan] IPCP: state change Ack-Sent --> Opened
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="157"] [wan] IPCP: LayerUp
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="158"] [wan]   xx.xx.xx.xx -> xx.xx.xx.xx
<30>1 2022-05-25T22:26:18+02:00 OPNsense.local ppp 57539 - [meta sequenceId="1"] [wan] error writing len 12 frame to b0: Network is down

The last line is caused from the update (i think), i did it right at that time.
And now, nothing works. From this point, it goes right that.

Code: [Select]

<30>1 2022-05-25T22:27:10+02:00 OPNsense.local ppp 57539 - [meta sequenceId="30"] [wan_link0] LCP: SendTerminateReq #4
<30>1 2022-05-25T22:27:10+02:00 OPNsense.local ppp 57539 - [meta sequenceId="31"] [wan_link0] LCP: LayerDown
<30>1 2022-05-25T22:27:14+02:00 OPNsense.local ppp 57539 - [meta sequenceId="32"] [wan_link0] LCP: SendTerminateReq #5
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="33"] [wan_link0] LCP: state change Stopping --> Stopped
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="34"] [wan_link0] LCP: LayerFinish
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="35"] [wan_link0] PPPoE: connection closed
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="36"] [wan_link0] Link: DOWN event
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="37"] [wan_link0] LCP: Down event
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="38"] [wan_link0] LCP: state change Stopped --> Starting
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="39"] [wan_link0] LCP: LayerStart
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="40"] [wan_link0] Link: reconnection attempt 1 in 2 seconds
<30>1 2022-05-25T22:27:18+02:00 OPNsense.local ppp 57539 - [meta sequenceId="41"] [wan_link0] Link: reconnection attempt 1
<30>1 2022-05-25T22:27:18+02:00 OPNsense.local ppp 57539 - [meta sequenceId="42"] [wan_link0] PPPoE: Connecting to ''
<30>1 2022-05-25T22:27:27+02:00 OPNsense.local ppp 57539 - [meta sequenceId="43"] [wan_link0] PPPoE connection timeout after 9 seconds
<30>1 2022-05-25T22:27:27+02:00 OPNsense.local ppp 57539 - [meta sequenceId="44"] [wan_link0] Link: DOWN event
<30>1 2022-05-25T22:27:27+02:00 OPNsense.local ppp 57539 - [meta sequenceId="45"] [wan_link0] LCP: Down event
<30>1 2022-05-25T22:27:27+02:00 OPNsense.local ppp 57539 - [meta sequenceId="46"] [wan_link0] Link: reconnection attempt 2 in 1 seconds
<30>1 2022-05-25T22:27:28+02:00 OPNsense.local ppp 57539 - [meta sequenceId="47"] [wan_link0] Link: reconnection attempt 2

I did downgrade the kernel to 22.1 and opnsense to 22.1.7, but it does not helped, this persists as it is.
I also tried to configure the old way with VLAN7 and on this the pppoe session (and disabled the vlan tag 7 addition in the vigor130), does not help, sadly.

Any hints on this ?

Thanks,
Ronny

Setup is:  APU2 with Vigor130 on the igb1 port, vlan 7 tag insserts the vigor130. The cable is directly from vigor130 to the apu2 on this port. I have an alias on this interface for the management address, that works flawlesse since ages. What is suspicious,  is that the counters only show out but NO in pakets since then:

Code: [Select]

Interfaces Overview for this:
Status up
PPPoE
up 
Uptime 00:00:0
MAC address 00:00:00:00:00:00 - XEROX CORPORATION
MTU 1492
IPv4 address pppoe/
IPv6 link-local fe80::20d:b9ff:fe4c:464/64
IPv6 address
In/out packets 0 / 36 (0 bytes / 3 KB)
In/out packets (pass) 0 / 36 (0 bytes / 3 KB)
In/out packets (block) 0 / 0 (0 bytes / 0 bytes)
In/out errors 0 / 0
Collisions 0

[meyergru]

Since your installation seems older and now it does not work anymore - but also back on 22.1.7: You know that since 22.1.something, you have to define parent interfaces for VLANs (and probably for PPPoE as well)?
You can leave them unconfigured IP-wise, but they must exist for sub-interfaces to work.

Also, there is a problem with aliases on 22.1.8 that has been fixed by 22.1.8_1.

[rcmcronny]

Since your installation seems older and now it does not work anymore - but also back on 22.1.7: You know that since 22.1.something, you have to define parent interfaces for VLANs (and probably for PPPoE as well)?
You can leave them unconfigured IP-wise, but they must exist for sub-interfaces to work.

I dont use vlans for the pppoe connection. It is a simple igb1 Port without anything, the vigor130 does the needed vlan7 tagging on itself. That makes my setup simpler. I have vlans for internal seperating devices, that work as they should and have the parent interface.
Sidenote, i also tried setting up the needed vlan and pppoe config and of course change the modem config, does either not help, problem exists.

Also, there is a problem with aliases on 22.1.8 that has been fixed by 22.1.8_1.

Thanks, i am already on the latest (and greatest) 22.1.8_1

Thanks,
Ronny

[rcmcronny]

Ok,

got it solved. The cause was the firmware update of the vigor130 dsl modem, i did that in the same timeframe (2.8.4 -> 2.8.5) no special things mentioned only minor things.

As i also did test my linux maschine with ppp and it did not work and also my mint laptop dit not work, there were not much things left. So i tried the downgrade of the firmware and viola, session up all good.

Really weird, perhaps it helps someone in the future. Seems the 2.8.4.1 and 2.8.5 did show this behavior on my site.

Thanks for helping
Ronny

[Foxtrot]

I have to revieve this thread, as it did cost me one day of trial and error before findeing this

I can CONFIRM that latest FW for Vigor 130 does NOT work with OPNsense (and pfsense).

@rcmcronny
Thanks for sharing this, it just took me way to long to find your comment on this.

I was running:

• 3.8.5.1_modem7 NOT WORKING
• 3.8.1.1_modem7 WORKING

[Ramalama]

Hey, 3.8.4 is the last one that works, just fyi