Thanks JimP for quick response.. I normally don't play with this stuff - but did recall a major change with the installer on 2.4..

Yes, both interfaces are on the same system. It's a Netgate SG-2440, so there are four identical Ethernet interfaces. I can use the wake command from the command-line on three out of the four interfaces. WOL from igb2 also seems to work from the web interface. Only wake from the command line with igb2 is giving the permission error.

@bumzag IP4 IP contain valid GATEWAY parameter? Go to a website and if... Comes back and says "site unknown/not found" = DNS broken. Comes back and says "unreachable" = no Gateway, IP4 missing/wrong param(s).

@ink You may find something here: link text

If you set the primary console to be the video/vga console then most of the bootup messages would only go there. The kernel startup messages always go to both, then the pfSense boot scripts output only to the primary console, and then all consoles get a menu.

Thx @jahonix I actually see it ob Chome and FF, very annoying

@jimp Thank you! It worked.

It was so simple I feel stupid. I knew it was something stupid simple but missed, I missed it because it shouldn't have been selected anyway. [image: 1529460872990-62e9c012-ecb1-4646-bb58-82ca00de6abe-image-resized.png]

At first his ISP thought he was going over his rated speed, but we traffic shaped and determined that was not the problem. His ISP now thinks it is the PPPoE Keep Alives not being recieved thus terminating his line. How would he got about mitigating this on the SG-1000? Here is what the ISP said, [image: 194610190618.png]

And here's what the routes look like after manually assiging the DNS servers in the GUI, assigning them the default gateway, and unchecking "Allow DNS server list to be overridden by DHCP/PPP on WAN" Internet: Destination Gateway Flags Netif Expire default 10.251.253.33 UGS xn0 10.251.251.67 10.251.253.33 UGHS xn0 10.251.251.252 10.251.253.33 UGHS xn0 10.251.253.32/27 link#5 U xn0 10.251.253.55 link#5 UHS lo0 10.252.252.245 10.251.253.33 UGHS xn0 104.43.216.101 10.251.253.33 UGHS xn0 localhost link#2 UH lo0 172.19.0.1 link#2 UH lo0 Now traffic from the other side of an IPSEC tunnel can reach the DNS server IP addresses.

Ok, well try setting 8.8.8.8 as the DNS in System > General setup and set Unbound to forwarding mode. Steve