I brought a BT Home Hub 5A model from online which as the newest stable version of OpenWrt (18.06.1).
I am wanting to use it as the sole router and have it connect to BT just like my Home Hub 6 does. I have been searching around online now for around three days and tried all different configurations. Please see screenshots below, I am convinced it is trying to connect to BT but they are refusing the connection.
I was going to post this in an already created BT PPPOE topic I found on here but it was closed, so apologies for the new post.
There is a mistake with the WAN interface having a green colour, which means you have assigned it to the lan zone in firewall.
Could you post the contents of /etc/config/network and /etc/config/firewall ?
Suggest factory resetting the HH5a as described in section 8 to resolve the issue described by @trendy
Then start at section 7.5 which will redirect you to the relevant section 9.x for setting up the internet connection for FTTC fibre, FTTP fibre or upto 17mb ADSL broadband services.
If you have BT Infinity FTTC fibre, have you configured the VLAN 101 tag (ie. dsl0.101) in the Physical Intertaces section, which is described in section 9.1 ?
I have rebooted the router and started fresh using the instructions on your guide. I feel I am still missing something I don't have infinity. I have super fast fibre unlimited, live out in the countryside so..... interner speeds are not the best!
config defaults
option syn_flood 1
option input ACCEPT
option output ACCEPT
option forward REJECT
# Uncomment this line to disable ipv6 rules
# option disable_ipv6 1
config zone
option name lan
list network 'lan'
option input ACCEPT
option output ACCEPT
option forward ACCEPT
config zone
option name wan
list network 'wan'
list network 'wan6'
option input REJECT
option output ACCEPT
option forward REJECT
option masq 1
option mtu_fix 1
config forwarding
option src lan
option dest wan
# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
option name Allow-DHCP-Renew
option src wan
option proto udp
option dest_port 68
option target ACCEPT
option family ipv4
option input ACCEPT
option output ACCEPT
option forward REJECT
# Uncomment this line to disable ipv6 rules
# option disable_ipv6 1
config zone
option name lan
list network 'lan'
option input ACCEPT
option output ACCEPT
option forward ACCEPT
config zone
option name wan
list network 'wan'
list network 'wan6'
option input REJECT
option output ACCEPT
option forward REJECT
option masq 1
option mtu_fix 1
config forwarding
option src lan
option dest wan
# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
option name Allow-DHCP-Renew
option src wan
option proto udp
option dest_port 68
option target ACCEPT
option family ipv4
option src wan
option proto icmp
option icmp_type echo-request
option family ipv4
option target ACCEPT
config rule
option name Allow-IGMP
option src wan
option proto igmp
option family ipv4
option target ACCEPT
# Allow DHCPv6 replies
# see https://dev.openwrt.org/ticket/10381
config rule
option name Allow-DHCPv6
option src wan
option proto udp
option src_ip fc00::/6
option dest_ip fc00::/6
option dest_port 546
option family ipv6
option target ACCEPT
config rule
option name Allow-MLD
option src wan
option proto icmp
option src_ip fe80::/10
list icmp_type '130/0'
list icmp_type '131/0'
list icmp_type '132/0'
list icmp_type '143/0'
option family ipv6
option target ACCEPT
# Allow essential forwarded IPv6 ICMP traffic
config rule
option name Allow-ICMPv6-Forward
option src wan
option dest *
option proto icmp
list icmp_type echo-request
list icmp_type echo-reply
list icmp_type destination-unreachable
list icmp_type packet-too-big
list icmp_type time-exceeded
list icmp_type bad-header
list icmp_type unknown-header-type
option limit 1000/sec
option family ipv6
option target ACCEPT
config rule
option name Allow-IPSec-ESP
option src wan
option dest lan
option proto esp
option target ACCEPT
config rule
option name Allow-ISAKMP
option src wan
option dest lan
option dest_port 500
option proto udp
option target ACCEPT
# include a file with users custom iptables rules
config include
option path /etc/firewall.user
I also have some sort of connection up and running:
In Network config, on interface wan, option ifname is wrong. it should be DSL0.101 not DS10.101 (small letters).
Other than that, better follow the guide in the site that @bill888 posted and report here if something doesn't work.
Follow exactly what it says in section 7.5/9.1 of the guide for PPPoE for FTTC. (PPPoA is only used for ADSL upto 17mb connections)
I notice you didn't delete the ATM bridge section as instructed in the guide, but that does not usually affect FTTC connections if left in, so I'm wondering how far you deviated from the instructions?
Perhaps factory resetting the hub to erase all settings again, and start from scratch.
Repost the /etc/config/network file if you still have issues, but the one you posted earlier looked correct except for ifname typo error, and perhaps wrong BT username. As far as I'm aware, BT has not changed the username - check your BT Smart Hub for what is used?
There is no need to post the /etc/config/firewall file.
I presume you are a consumer customer of BT Retail and not a BT Business customer ?
You need to provide any non-empty password with the login. As it seems your current configuration does not have any pap/chap password, causing your peer to rejects the connection. In Bill's manual the recommended password is ' ' (a space), which can cause confusion. Anything non-empty should work, e.g. 'BT'.
Also, if you have ssh access to the router, try adding to your wan section of /etc/config/network the line option pppd_options 'debug'
It will provide more detailed information about the pppoe connection process.
Do you log into the Smart hub and press a button to disconnect 'cleanly' from BT internet, or are you just powering off the Smart hub and swapping over to HH5A?
The /e/c/network seems to look correct.
I note there is no 'option password' entry in 'interface wan' section is only anomaly. Perhaps try any password, then try again after deleting it.
I will login via SSH and use Vim to place an empty password in savostyanov, good thinking!
I will also add the debug line whilst in there, thanks buddy.
Bill, I actually do not connect or disconnect it at all I literally just pull the DSL line from the router and plug it into the Hub 5A did not think it would make a difference to be honest with you.
I did try both passwords yes and still the same, but I will try again now with both of your methods and see if that does the trick. Fingers Crossed
Great, thanks for confirming! I suspect that Luci web interface wipes one-space password before it is passed to the configuration? Perhaps, it's best to change the example password to anything non-empty in @bill888's manual?
