With massive thanks to people on the forum I managed to get my BT HomeHub5 into a bridge mode.
I'm stuck on my next step now! (doh!)
Does anyone know how to use Network Manager (Kubuntu latest) to authenticate against the UK Vlan system? On my modem running OpenWRT I had to set up a vlan of 1.101 and then it would connect to my Vodafone VDSL account. However while the modem is showing a connected line now, and bridged to enp9s0 on my PC, I can't work out the Network Manager or nmcil settings to auth against the DSL connection.
I might be misunderstanding your set-up, but when I was in your shoes I bridged dsl0.7 to lan1.7 and then connected that to my OpenWrt mainrouter running PPPoE over wan.7. Initially I wanted to set things up as trunk, so any VLAN tag emitted from wan would be passed to dsl0, but since I failed to get that going in the time I allotted (and since my ISP is not going to change away from VLAN7 anytime soon) I just hard-coded that on the BT HH5A....
I also set up lan1 to accept VLAN2 so I can access the BT HH5A's LuCI GUI... to get information about the modem.
Please note that on my line the lantiq modem in the BTHH5A proved to be very unstable so I switched this out for a broadcom based zyxel modem (also in bridge mode) which was recommended as harmonizing better to my ISP's linecards and usage of bi-directional vectoring and G.INP, but I assume that this should not be an issue in the UK given that BT should have little appetite for replacing all HH5A units in the field....
Moeller0, thanks for the response. i think I'm a bit confused about the VLAN situation. I've basically got the HH5 forwarding the connection over the red port to enp9s0 on the server. Now I want the server to do the VDSL registration against my Voda account and for it to put the external IP address onto the enp9s0 interface. What I can't figure out is having netplan on Ubuntu supply the ISP with my account details over this weird 1.101 vlan the UK network seems to need!?
Still nothing though, no IP on enp9s0. Is there a way to put username and PW for pppoe into netplan? I've Googled and Googled, but to no success. All I want is the HH5 bridging to enp9s0 (on BT's vlan of 101) and giving me the extrenal static IP on the PC enp9s0 interface!
cat /etc/ppp/peers/provider
user ################@businessbroadband.vodafone.co.uk
plugin rp-pppoe.so
enp9s0.101
noipdefault
defaultroute
hide-password
lcp-echo-interval 20
lcp-echo-failure 3
noauth
persist
maxfail 0
mtu 1492
noaccomp
default-asyncmap
+ipv4
+ipv6
linkname pppoe
cat /etc/ppp/chap-secrets
# Secrets for authentication using CHAP
# client server secret IP addresses
* * ################
Because I did RTFM and put those in! Still no connection? Do I need to be using vlan tagging in the netplan do you think, or is OpenWRT handling that? I've tried changing the interface between enp9s0 and enp9s0.101 and it still doesn't go out and auth.
Does anyone know if there is a way to check the OpenWRT on the BT HH5 is forwarding the connection to the red wlan port? IP A shows link up on both enp9s0 and enp9s0.101, but I'm not convinced the modem is forwarding properly yet. Surely I should have had some messages in my PC's syslog or dmesg from ppp about failed connection, or refused auth ? There is nothing though.
In my logs, all I get is messages about PADO packets, which makes me thing the modem is not bridging properly? Can anyone please send me a copy of their config files from /etc/config (with private data redacted of course) to compare?
Thanks,
Ian B
Aug 19 09:07:59 MC pppd[3129]: Plugin rp-pppoe.so loaded.
Aug 19 09:07:59 MC pppd[3130]: pppd 2.4.7 started by bon, uid 0
Aug 19 09:08:35 MC pppd[3130]: Timeout waiting for PADO packets
Aug 19 09:08:35 MC pppd[3130]: Unable to complete PPPoE Discovery
Aug 19 09:09:15 MC pppd[3130]: Timeout waiting for PADO packets
Aug 19 09:09:15 MC pppd[3130]: Unable to complete PPPoE Discovery
Aug 19 09:09:43 MC pppd[3160]: Plugin rp-pppoe.so loaded.
The HH5a if configured correctly as a bridge modem by following my guide, should mimic the old Openreach VDSL2 modems. So No, you should not be using vlan tagging in kubuntu.
sorry, I don't know kubuntu.
Do you have ANY generic (Dlink, Tplink, Linksys etc) cable router (ie. no built in modem) which should offer PPPoE, which you can simply plug into the HH5a 'bridge modem' to confirm the HH5a is configured correctly, by simply entering username & password?
(fwiw, as alternative to HH5a in 'bridge mode', there are also the 'old' Huawei or ECI Openreach VDSL modems - beware of failing capacitors due to age. TP-link TD-W9970 offers 'bridge' mode and can be picked up on eBay UK very cheaply)
ps. last time I tested 'bridge mode' was with LEDE 17 on HH5a, and on ECI modems running OpenWrt 18 snapshot. No reason why it should not work with OpenWrt 19 and later.
Well "Timeout waiting for PADO packets" just tells you that your client sent a PADI packet and failed to get the expected response packet in time. The cause for this can be almost anything related to the network path between the ppp termination points. (This very much includes not having the DSL cable properly put into its socket (or a broken socket), as I once found out)....
I believe you already checked the DSL sync.
The next culprits often are VLAN tags, but in your case you VLSN tag the dsl interface and bridge with an untagged LAN port on the BTHH5A, so your PPPoE client should not even need to set aVLAN tag at all.
**Line State:**UP [0x0]
**Line Mode:**G.993.2 (VDSL2)
**Line Uptime:**1d 5h 21m 13s
**Annex:**B
**Profile:**17a
**Data Rate:**76.344 Mb/s / 19.978 Mb/s
**Max. Attainable Data Rate (ATTNDR):**100.444 Mb/s / 30.882 Mb/s
**Latency:**0.16 ms / 0.0 ms
**Line Attenuation (LATN):**9.1 dB / 8.7 dB
**Signal Attenuation (SATN):**9.1 dB / 8.6 dB
**Noise Margin (SNR):**11.6 dB / 12.0 dB
**Aggregate Transmit Power (ACTATP):**-6.3 dB / 12.8 dB
**Forward Error Correction Seconds (FECS):**0 / 0
**Errored seconds (ES):**0 / 25904
**Severely Errored Seconds (SES):**0 / 328
**Loss of Signal Seconds (LOSS):**3 / 0
**Unavailable Seconds (UAS):**154 / 154
**Header Error Code Errors (HEC):**0 / 0
**Non Pre-emptive CRC errors (CRC_P):**0 / 0
**Pre-emptive CRC errors (CRCP_P):**0 / 0
**ATU-C System Vendor ID:**Broadcom 164.161
**Power Management Mode:**L0 - Synchronized
So I've got VDSL. Now I just want to bridge that over the red port on the HH5 to the PC, which can auth and get the external IP address (I've got a static ipv4).
On ports 1-4 I have the internal br-lan bridge going, with an ip I can access when I plug in to it. I've detached (I believe) the red port from that vlan. The lights on the PC interface shows its live, and shows traffic when I plug it in. However I'm loosing the connection somewhere, as the PC cannot find the PPPOE connection.
IIRC correctly I had it set up such, that via VLAN2 I could access the modem's GUI, and via VLAN7 the bridged DSL-link (my ISP requires VLAN7). That way I only need one cable between router and modem....
I'm on 6.5 hours on this today, and it's still not playing! It's now bugging me!!
Bill suggested I follow his guide, so I've reset the modem to factory (openwrt) defaults and restored my original config files. The modem connected to the DSL account on pppoe. So the DSL is fine. Then I followed Bill's guide and changed modem settings according to that, and on 2 different PC's (one on Mint Linux, one on Kubuntu) I've tried to get them talking on the vlan 101 to the modem to auth. Nothing. pppoeconf finds nothing. I'm utterly stuck!
I'm sure Bill's openwrt config guide must be right, so why can't any of my computers find the vdsl concentrator? Any ideas? I think I must be screwing up the PC side of things, not the modem.
If the HH5a is configured as described in my guide, do NOT configure vlan 101 on any router (or computer in your case) you subsequently connect to the HH5a bridge modem.
Only 3 parameters are needed to set up any generic router (without modem) wired to a bridge modem used on Openreach supplied VDSL2 superfast broadband services. ie. select PPPoE protocol, and enter username, and password. No other parameters required.
I know bridge mode worked with LEDE 17 and I think OpenWrt 18. Not personally tested with Openwrt 19 or 20.
Try a generic router to verify the bridge modem is working?
Perhaps post your /etc/config/network file? (The one you posted earlier today does not show any bridge between DSL and ethernet ports)
I think the wan section of your earlier posted 'network' file should read:
config interface 'wan'
option proto 'none'
option delegate '0'
option type 'bridge'
option ifname 'dsl0.101 eth0.2' # bridged
