Upgrade to 2.8.0 -- seemingly created many problems.

[Wylbur]

I have an older box (A) and a new box (B). And was trying to make B the primary with A being a backup.

So I swapped cables to make A the system running the LAN.

Then I started to update B and realized I had forgotten the first step -- uninstall all the applications. So I stopped this, and re-installed 2.7.2 on B. This is where things went sideways when I did the upgrade to 2.8.0.

Once the re-install (2.7.2) was completed and I had it all configured the same as box A (password, static IPs, and pools), I started the 2.8.0 upgrade, and then thought this was the time for going from ISC to KEA. Time for a reboot and that is when I started getting all kinds of error messages.

So I swapped back to A and could not get anything to work correctly. Laptops didn't connect to the LAN, could not ping anything. --- What I found out later was, this was a problem with the VPN software (Mulvad in this case). I had needed to turn that off on the laptops first -- OK, back to system B and now it can't be made to boot. I actually had to take another install DVD (different Linux O/S) and have it install to clear the disks.

I got the ISP involved and they wanted me to take their equipment and put that between my equipment and their ONT (fiber optic "modem"). So I did that. This added a new complication so I finally fixed it to be off on the side where it was not providing any service to box A or B.

This (wiring so that the EERO router did not provide service to Box A or B) is how I found that it was that 2.8.0 goes APE when it gets an IPV6 address when it has been configured to NOT use IPv6. So much so that I had to do another install of a Linux system to get the 272 DVD to actually install.

Meanwhile I read about others having a problem with KEA for DHCP so I decided to NOT use that once I got 2.7.2 to install correctly (again) -- I have not upgraded to 2.8.0. Not going down that road again for a while.

I'm finally operable using Box A.

One of the things that was happening was getting a large number of rule errors and various strings in messages during the boot processes after the install completed with 280. Since I don't understand that problem -- just not going to upgrade box B to 280 for now.