Unable to connect to VDSL - Timeout waiting on PADO packets

Networking
1

Hello All,

after struggling with this problem for some time, I decided to ask for help.

I am running a network of three IPFire connected by VPN for about 2 years now, before that I used IPCop for more than 10 years until the development of IPCop was stopped.

Our 3 locations were connected to internet by Telekom VDSL (location A and B) and M-Net ADSL (location C). Beginning of this year M-Net told me that they had to switch my connection to VDSL because the old was based on ISDN.

This was done with the two Telekom connections already without greater problems before, because oft that I did not worry about it.

The only thing that I had to change was to replace the old ADSL modem with a modem that was capable of VDSL2. I bought the successor of my Zyxel VMG1312-B30A, the Zyxel VMG3006-D70A and set it to modem mode. I tested it with IPCop A and VDSL A and it was working fine.

After the connection change on Location C I replaced the old modem with the new one and tried to connect, but it did not work, the connection daemon could not connect, in the messages file there were entries like this: (It was every time the timeout waiting for PADO packets, this log entry is from a later connect try):

Apr 5 11:02:40 Gatekeepix pppd[22081]: Plugin rp-pppoe.so loaded.
Apr 5 11:02:40 Gatekeepix pppd[22081]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Apr 5 11:02:40 Gatekeepix connectd[22083]: Connectd (start) started with PID 22083
Apr 5 11:02:40 Gatekeepix pppd[22081]: pppd 2.4.7 started by root, uid 0
Apr 5 11:02:42 Gatekeepix kernel: tg3 0000:03:00.1 red0: Link is up at 100 Mbps, full duplex
Apr 5 11:02:42 Gatekeepix kernel: tg3 0000:03:00.1 red0: Flow control is on for TX and on for RX
Apr 5 11:02:42 Gatekeepix kernel: tg3 0000:03:00.1 red0: EEE is disabled
Apr 5 11:02:42 Gatekeepix unbound: [22119:0] notice: init module 0: validator
Apr 5 11:02:42 Gatekeepix unbound: [22119:0] notice: init module 1: iterator
Apr 5 11:02:42 Gatekeepix unbound: [22119:0] info: start of service (unbound 1.8.1).
Apr 5 11:03:55 Gatekeepix pppd[22081]: Timeout waiting for PADO packets
Apr 5 11:03:55 Gatekeepix pppd[22081]: Unable to complete PPPoE Discovery
Apr 5 11:03:55 Gatekeepix pppd[22081]: Exit.
Apr 5 11:03:55 Gatekeepix connectd[22083]: No pppd is running. Trying reconnect.

After that I took the modem again back to Location A and tested it again. It worked fine. I took the old modem, that was in use for many years to Location C and tried to connect – same error.

I carried Router C and the modem to Location A and tried to connect – same error.

Both modems were tested with IPFire A and worked without problems.

I replaced the hard disk of Router C with a new one and installed the most recent copy of IPFire with connection to the new VDSL modem – same error

I installed the Router C with Windows 10 to test the LAN interfaces. Both LAN Interfaces work without problems.

Hardware:
A & B: Supermicro Mainboard A2SDi-2C-HLN4F, 2018
C: HP Proliant Microserver Gen 8, 2015

Now I am running out of ideas what to do next and I am very thankful for every hint.

Best regards
Zauberlehrling

2

Have you changed the VLAN ID. Telekom VDSL connections use “7” and M-Net at my informations “40”

3

Hi,

thank you for the quick answer. I checked it. My Working IPFire A has set VLAN in IPTV/VLAN to 7
The other (new installed IPFire C) says under IPTV/VLAN: No IPTV possible install addon igmpproxy.
I do not use any IPTV functionality and because of that I thought that does not matter.
Today evening I cannot test - my son has very important quests to do :wink: I will try tomorrow

Best regards
Wolfram

4

This IPTV option is usually for VLAN8 and need igmpproxy installed. The PPPoE VLAN doesn’t need the addon.

Have you reconfigured the dailin from PPPoE to VDSL ? Only in VDSL mode you can set the VLAN ID.

Maybee the PPPoE VLAN is set in the Modem and not in the IPFire.

5

Hello & Sorry this was my fault. I made a new installation and did not configure it correctly. I have fixed that, but it is still not working.
I even got worse, because after some tests today morning my working IPFire A has the same error:

This are the settings in Dialup. I did not change anything there. I only disconnect the ethernet intefrace of the modem and connected it IPFire C. After reconnecting to IPFire A it came up with same error.

Attached a screenshot of the Dialup settings and logs from kernel and pppd

Kernel:
10:25:08 kernel: <27>udevd[26816]: Error changing net interface name red0.7 to red0: File exists
10:23:22 kernel: <27>udevd[26402]: Error changing net interface name red0.7 to red0: File exists
10:21:36 kernel: <27>udevd[26071]: Error changing net interface name red0.7 to red0: File exists
10:19:49 kernel: <27>udevd[25654]: Error changing net interface name red0.7 to red0: File exists
10:18:03 kernel: <27>udevd[25344]: Error changing net interface name red0.7 to red0: File exists
10:16:17 kernel: <27>udevd[25013]: Error changing net interface name red0.7 to red0: File exists
10:14:31 kernel: <27>udevd[24599]: Error changing net interface name red0.7 to red0: File exists
10:12:45 kernel: <27>udevd[24268]: Error changing net interface name red0.7 to red0: File exists
10:10:59 kernel: <27>udevd[23937]: Error changing net interface name red0.7 to red0: File exists
10:09:16 kernel: ixgbe 0000:05:00.1 red0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
10:09:13 kernel: <27>udevd[23324]: Error changing net interface name red0.7 to red0: File exists
10:09:13 kernel: 8021q: adding VLAN 0 to HW filter on device red0
10:09:13 kernel: ixgbe 0000:05:00.1: registered PHC device on red0
10:09:11 kernel: ixgbe 0000:05:00.1: removed PHC on red0
10:07:54 kernel: <27>udevd[23012]: Error changing net interface name red0.7 to red0: File exists
10:06:29 kernel: ixgbe 0000:05:00.1 red0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
10:06:25 kernel: ixgbe 0000:05:00.1 red0: NIC Link is Down
10:06:22 kernel: ixgbe 0000:05:00.1 red0: NIC Link is Up 1 Gbps, Flow Control: None

pppd:

10:53:25 pppd[1734]: pppd 2.4.7 started by root, uid 0
10:53:25 pppd[1734]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:53:25 pppd[1734]: Plugin rp-pppoe.so loaded.
10:52:54 pppd[1127]: Exit.
10:52:54 pppd[1127]: Unable to complete PPPoE Discovery
10:52:54 pppd[1127]: Timeout waiting for PADO packets
10:51:39 pppd[1127]: pppd 2.4.7 started by root, uid 0
10:51:39 pppd[1127]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:51:39 pppd[1127]: Plugin rp-pppoe.so loaded.
10:51:08 pppd[443]: Exit.
10:51:08 pppd[443]: Unable to complete PPPoE Discovery
10:51:08 pppd[443]: Timeout waiting for PADO packets
10:49:53 pppd[443]: pppd 2.4.7 started by root, uid 0
10:49:53 pppd[443]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:49:53 pppd[443]: Plugin rp-pppoe.so loaded.
10:49:22 pppd[32332]: Exit.
10:49:22 pppd[32332]: Unable to complete PPPoE Discovery
10:49:22 pppd[32332]: Timeout waiting for PADO packets
10:48:07 pppd[32332]: pppd 2.4.7 started by root, uid 0
10:48:07 pppd[32332]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:48:07 pppd[32332]: Plugin rp-pppoe.so loaded.
10:47:36 pppd[31735]: Exit.
10:47:36 pppd[31735]: Unable to complete PPPoE Discovery
10:47:36 pppd[31735]: Timeout waiting for PADO packets
10:46:21 pppd[31735]: pppd 2.4.7 started by root, uid 0
10:46:21 pppd[31735]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:46:21 pppd[31735]: Plugin rp-pppoe.so loaded.
10:45:50 pppd[31057]: Exit.
10:45:50 pppd[31057]: Unable to complete PPPoE Discovery
10:45:50 pppd[31057]: Timeout waiting for PADO packets
10:44:35 pppd[31057]: pppd 2.4.7 started by root, uid 0
10:44:35 pppd[31057]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:44:35 pppd[31057]: Plugin rp-pppoe.so loaded.
10:44:04 pppd[30461]: Exit.
10:44:04 pppd[30461]: Unable to complete PPPoE Discovery
10:44:04 pppd[30461]: Timeout waiting for PADO packets
10:42:49 pppd[30461]: pppd 2.4.7 started by root, uid 0
10:42:48 pppd[30461]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:42:48 pppd[30461]: Plugin rp-pppoe.so loaded.
10:42:18 pppd[30053]: Exit.
10:42:18 pppd[30053]: Unable to complete PPPoE Discovery
10:42:18 pppd[30053]: Timeout waiting for PADO packets
10:41:02 pppd[30053]: pppd 2.4.7 started by root, uid 0
10:41:02 pppd[30053]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:41:02 pppd[30053]: Plugin rp-pppoe.so loaded.
10:40:31 pppd[29640]: Exit.
10:40:31 pppd[29640]: Unable to complete PPPoE Discovery
10:40:31 pppd[29640]: Timeout waiting for PADO packets
10:39:16 pppd[29640]: pppd 2.4.7 started by root, uid 0
10:39:16 pppd[29640]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:39:16 pppd[29640]: Plugin rp-pppoe.so loaded.
10:38:45 pppd[29309]: Exit.
10:38:45 pppd[29309]: Unable to complete PPPoE Discovery
10:38:45 pppd[29309]: Timeout waiting for PADO packets
10:37:30 pppd[29309]: pppd 2.4.7 started by root, uid 0
10:37:30 pppd[29309]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:37:30 pppd[29309]: Plugin rp-pppoe.so loaded.
10:36:59 pppd[28977]: Exit.
10:36:59 pppd[28977]: Unable to complete PPPoE Discovery
10:36:59 pppd[28977]: Timeout waiting for PADO packets
10:35:44 pppd[28977]: pppd 2.4.7 started by root, uid 0
10:35:44 pppd[28977]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:35:44 pppd[28977]: Plugin rp-pppoe.so loaded.
10:35:13 pppd[28564]: Exit.
10:35:13 pppd[28564]: Unable to complete PPPoE Discovery
10:35:13 pppd[28564]: Timeout waiting for PADO packets
10:33:58 pppd[28564]: pppd 2.4.7 started by root, uid 0
10:33:58 pppd[28564]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:33:58 pppd[28564]: Plugin rp-pppoe.so loaded.
10:33:27 pppd[28254]: Exit.
10:33:27 pppd[28254]: Unable to complete PPPoE Discovery
10:33:27 pppd[28254]: Timeout waiting for PADO packets
10:32:12 pppd[28254]: pppd 2.4.7 started by root, uid 0
10:32:12 pppd[28254]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:32:12 pppd[28254]: Plugin rp-pppoe.so loaded.
10:31:41 pppd[27922]: Exit.
10:31:41 pppd[27922]: Unable to complete PPPoE Discovery
10:31:41 pppd[27922]: Timeout waiting for PADO packets
10:30:26 pppd[27922]: pppd 2.4.7 started by root, uid 0
10:30:26 pppd[27922]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:30:26 pppd[27922]: Plugin rp-pppoe.so loaded.
10:29:55 pppd[27489]: Exit.
10:29:55 pppd[27489]: Unable to complete PPPoE Discovery
10:29:55 pppd[27489]: Timeout waiting for PADO packets
10:28:40 pppd[27489]: pppd 2.4.7 started by root, uid 0
10:28:40 pppd[27489]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:28:40 pppd[27489]: Plugin rp-pppoe.so loaded.
10:28:09 pppd[27158]: Exit.
10:28:09 pppd[27158]: Unable to complete PPPoE Discovery
10:28:09 pppd[27158]: Timeout waiting for PADO packets
10:26:54 pppd[27158]: pppd 2.4.7 started by root, uid 0
10:26:54 pppd[27158]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:26:54 pppd[27158]: Plugin rp-pppoe.so loaded.
10:26:23 pppd[26847]: Exit.
10:26:23 pppd[26847]: Unable to complete PPPoE Discovery
10:26:23 pppd[26847]: Timeout waiting for PADO packets
10:25:08 pppd[26847]: pppd 2.4.7 started by root, uid 0
10:25:08 pppd[26847]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:25:08 pppd[26847]: Plugin rp-pppoe.so loaded.
10:24:37 pppd[26433]: Exit.
10:24:37 pppd[26433]: Unable to complete PPPoE Discovery
10:24:37 pppd[26433]: Timeout waiting for PADO packets
10:23:22 pppd[26433]: pppd 2.4.7 started by root, uid 0
10:23:22 pppd[26433]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:23:22 pppd[26433]: Plugin rp-pppoe.so loaded.
10:22:51 pppd[26102]: Exit.
10:22:51 pppd[26102]: Unable to complete PPPoE Discovery
10:22:51 pppd[26102]: Timeout waiting for PADO packets
10:21:36 pppd[26102]: pppd 2.4.7 started by root, uid 0
10:21:36 pppd[26102]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:21:36 pppd[26102]: Plugin rp-pppoe.so loaded.
10:21:05 pppd[25685]: Exit.
10:21:05 pppd[25685]: Unable to complete PPPoE Discovery
10:21:05 pppd[25685]: Timeout waiting for PADO packets
10:19:50 pppd[25685]: pppd 2.4.7 started by root, uid 0
10:19:50 pppd[25685]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:19:50 pppd[25685]: Plugin rp-pppoe.so loaded.
10:19:19 pppd[25375]: Exit.
10:19:19 pppd[25375]: Unable to complete PPPoE Discovery
10:19:19 pppd[25375]: Timeout waiting for PADO packets
10:18:04 pppd[25375]: pppd 2.4.7 started by root, uid 0
10:18:04 pppd[25375]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:18:04 pppd[25375]: Plugin rp-pppoe.so loaded.
10:17:33 pppd[25044]: Exit.
10:17:33 pppd[25044]: Unable to complete PPPoE Discovery
10:17:33 pppd[25044]: Timeout waiting for PADO packets
10:16:18 pppd[25044]: pppd 2.4.7 started by root, uid 0
10:16:18 pppd[25044]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:16:18 pppd[25044]: Plugin rp-pppoe.so loaded.
10:15:47 pppd[24630]: Exit.
10:15:47 pppd[24630]: Unable to complete PPPoE Discovery
10:15:47 pppd[24630]: Timeout waiting for PADO packets
10:14:32 pppd[24630]: pppd 2.4.7 started by root, uid 0
10:14:32 pppd[24630]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:14:32 pppd[24630]: Plugin rp-pppoe.so loaded.
10:14:01 pppd[24299]: Exit.
10:14:01 pppd[24299]: Unable to complete PPPoE Discovery
10:14:01 pppd[24299]: Timeout waiting for PADO packets
10:12:45 pppd[24299]: pppd 2.4.7 started by root, uid 0
10:12:45 pppd[24299]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:12:45 pppd[24299]: Plugin rp-pppoe.so loaded.
10:12:15 pppd[23968]: Exit.
10:12:15 pppd[23968]: Unable to complete PPPoE Discovery
10:12:14 pppd[23968]: Timeout waiting for PADO packets
10:10:59 pppd[23968]: pppd 2.4.7 started by root, uid 0
10:10:59 pppd[23968]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:10:59 pppd[23968]: Plugin rp-pppoe.so loaded.
10:10:28 pppd[23576]: Exit.
10:10:28 pppd[23576]: Unable to complete PPPoE Discovery
10:10:28 pppd[23576]: Timeout waiting for PADO packets
10:09:13 pppd[23576]: pppd 2.4.7 started by root, uid 0
10:09:13 pppd[23576]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:09:13 pppd[23576]: Plugin rp-pppoe.so loaded.
10:09:10 pppd[23043]: Exit.
10:09:10 pppd[23043]: Unable to complete PPPoE Discovery
10:09:10 pppd[23043]: Timeout waiting for PADO packets
10:07:55 pppd[23043]: pppd 2.4.7 started by root, uid 0
10:07:55 pppd[23043]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:07:55 pppd[23043]: Plugin rp-pppoe.so loaded.
10:07:24 pppd[22729]: Exit.
10:07:24 pppd[22729]: Unable to complete PPPoE Discovery
10:07:24 pppd[22729]: Timeout waiting for PADO packets
10:06:09 pppd[22729]: pppd 2.4.7 started by root, uid 0
10:06:09 pppd[22729]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
10:06:09 pppd[22729]: Plugin rp-pppoe.so loaded.

I am not allowd to uplaod the logs.

Settings_IPFire
Settings_IPFire859×657 15.7 KB

Thank you in advance

Best regards
Wolfram

6

I forgot to mention: Atm I am connected to the internet with a Fritzbox 7590, that I have in case of problems like this. So it is no problem on provider side.

Regards
Wolfram

7

Fritzboxes are very special. If they are not in “fullbridge” Mode thay internally add the vlan ID.

There are two ways to connect with a VLAN.
If the moden internally add a vlan ID in the IPFire must choosen PPPoE and no VLAN.
In this case you have to reconfigure the Modem from VLAN 7 to 40 to switch to the MNet connection.

If the modem not add the ID in the IPFire must coosen VDSL and VLAN7 or 40 depending from the ISP.
Also keep in mind that a created VLAN device cannot removed. If you change this in the GUI you have to reboot to remove the VLAN Interface.

8

First problem solved:
Zyxel3006-D70A
Port 1 = Console Port only for configuration!
Prot 2-4 take any of this for connecting the router

Second problem was a faulty cable. I replaced every cable that was used there with new cables and now Router C an connect at Location A (Telekom, VLAN ID 7)

I will go to location C tomorrow and try there with VLAN ID 40 (M-NET).

Thank you for your help. I will post the outcome.

Regards
Wolfram

9

I dont know exactly this model but the old one you use before. Normaly they do default Vlan ID 7. So its not necessary to do it again in IPFire. Its enough you use in the settings PPPoE without Vlan.

btw you can update to new Core 142. It seems you dont use it at the moment.

10

Hi Tulpenkicker,

Today morning I made the mistake to connect the port 1 of Zyxel3006-D70A to the router, this cannot work, because it is console only. After connecting to Port 4 and re-initializing the network it worked again.

The old Zyxel modem VMG1312 had no specific console port.

As Arne posted the Munich Provider M-Net uses VLAN 40. I will try this tomorrow.

“Zuführung in die Whg. über VDSL2 gemäß ITU-T G.993.2 mit VLAN Tagging gemäß IEEE 802.1Q (VLAN 40)”

And about the update - yes I know … but it was very much work the last weeks and we are three here working in home-office / home-schooling … never touch a running system :wink: I will upgrade soon.

Best Regards
Wolfram

11

All what i said before is, its not necessary to do 2 times VLAN ID7.

I dont spoke about your Ports in your Zyxel and i dont spoke about VLAN 40 :wink:

12

All problems solved - a big THANK YOU to Arne. With VLAN ID 40 for MNet it worked.

Best Regards
Wolfram

13

[quote=“arne_f, post:7, topic:1931, full:true”]

Just to clarify this. I did not use the Fritzbox as the DSL Modem for IPFire. I used it in emergency as “the Router” :wink: and the IPFire was taken off the network.

Regards
Wolfram