Billion UK Forum

So I bit the bullet and upgraded to 2.32e on my Billion 8800NL - all went smoothly until the day after the upgrade.

My network is split into two main parts - I have a web / email / DHCP etc server and the house runs on one part and my stepson has his own "guest" network which is a simple guest wireless + one port to a network switch using a VLAN to isolate him from the rest of "my" network.

It has been working flawlessly since setting it up a couple of years ago. As my router was using the stock firmware, I foolishly decided to flash to the latest version.

Now my server hands out DHCP addresses in the 192.168.1.x range so DHCP is disabled through the router on the default LAN/Wlan network, his network uses the 8800NL DHCP on a 192.168.2.x range. Group isolation is active and his desktop runs through the switch (VLAN110) and P3 which is grouped on the 8800NL. This works (worked) well and any device on the VLAN110 or Wireless (SJD) gets a 192.168.2.x IP but can't see my 192.168.1.x network.

After the firmware update, for some reason, his desktop has started to ask my server on the different group for DHCP addresses. This is duly handed out but because he can't get any further through the network, his machine then refuses to access the network. My DHCP server also moans that he shoudn't be on this network segment.

This has only started happening after the 2.32e update. I tried flashing down to an earlier firmware but my 8800NL then refused point blank to connect via VDSL and I had to flash back to 2.32e.

Before the upgrade, P3/SJD wireless couldn't see anything on P1/BBD wireless and vice versa. After the upgrade, machines on the P3 port can now ask my server on the P1 port for a DHCP address. Something seems to have changed and no amount of tinkering seems to be able to fix it.

Any ideas ?

Attached screenshot of the grouping

To follow up, for the past 3 years I've had an upload of 20Mb / Download >55Mb

This morning the router had been up for 3 hours and I had a upload sync of 19Mb and download sync of 52.7Mb

Is it possible to revert to an earlier firmware ? Not impressed really.

picbits wrote: ↑Mon Feb 05, 2018 7:07 am To follow up, for the past 3 years I've had an upload of 20Mb / Download >55Mb

This morning the router had been up for 3 hours and I had a upload sync of 19Mb and download sync of 52.7Mb

Is it possible to revert to an earlier firmware ? Not impressed really.

What was your previous firmware version, you can always downgrade if needed

The original firmware version was the one thing I forgot to make a note of. It was bought in April 2015 and had the original firmware that it came with.

I tried downgrading to 2.32d.dh14 when the 2.32e didn't work but the router refused to connect to my ISP.

When I reflashed to 2.32e, it connected again without an issue.

picbits wrote: ↑Mon Feb 05, 2018 5:15 pm The original firmware version was the one thing I forgot to make a note of. It was bought in April 2015 and had the original firmware that it came with.

I tried downgrading to 2.32d.dh14 when the 2.32e didn't work but the router refused to connect to my ISP.

When I reflashed to 2.32e, it connected again without an issue.

Try the attached firmware (latest 2.32e.d14) which has a different DMT code (if you were on 2.32d before you need to upgrade with factory default settings selected and manually reconfigure the device again from scratch, I would also advise taking a backup of your current config if you plan on downgrading to the older firmware (2.32d.dm2), I am attaching a older firmware as we have lots of different firmware I am not sure what you were running before)

Thanks - will give them a go this weekend and let you know how I get on.

On all occasions where I reflashed, I restarted with the default settings. The 2.32d.dh14 just refused point blank to connect to my ISP. Will grab more log files if the others fail.

picbits wrote: ↑Mon Feb 05, 2018 6:39 pm Thanks - will give them a go this weekend and let you know how I get on.

On all occasions where I reflashed, I restarted with the default settings. The 2.32d.dh14 just refused point blank to connect to my ISP. Will grab more log files if the others fail.

It should work fine, as that was the stock firmware release, try and make sure the '802.1P Priority' is set to 0 and the '802.1Q VLAN ID' is set to 101 also

Thanks - I've reflashed back to the original as we were having stability problems anyway with the latest firmware.

All went well and worked first time. Now to wait for a while to see how stable it is.