Quote from: NotFuzzyWarm on Today at 04:40:51 PM

PLEASE use the Code icon in the toolbar to post logs - looks like #. It makes things much easier to read...
As for the pools issue - if you are copy/pasting in the pool and user information make sure there are no spaces added. Quite often when doing c/p there is a space added to the end of the string and miners do not like that.

Quote

Where I have other trouble is if I try and use the FUNC button to get it into config mode, I can't access it at its default 168.168.168.168 because my router is at 168.168.1.1

Again - it is not a router address issue. You need to set the PC to use the same subnets the Avalon is on. In that situation most routers will act as a switch and just pass data from the PC & miner through it.

Ok. So when I press and hold the FUNC button, it should be defaulted to 168.168.168.168 on 255.255.255.0. If I go into windows and set a static IP of 192.168.168.100 at 255.255.255.0, I lose all connectivity and cannot connect to either the internet or the miner. The default gateway is 192.168.1.1, should that stay the same?

It did BRIEFLY work when I connected it directly to the router as opposed to through my network switch, but since then it won't connect, even when I connect directly again.

It just doesn't make any sense why DHCP won't work to connect to pools. I suppose it could be the controller or hashboards themselves, though they all worked when it did connect, but I have 2 PSU's and it doesn't make a difference which I connect, so at least I think I can rule that out. I suppose it could be some security setting with Verizon, but I did my best to limit that.