I figure a courtesy restart wouldn't hurt then all things go south. The address showing on my external nic is 10.1.1.2 which is nothing like my isp's assigned static address and of course I have no internet. The only way I could fix this was to change the role of the adapter from PPPoE to unassigned then to save then revert back and save again. This took a few times before it worked.
I have re-installed and configured that file and all is ok besides the above problem still occurring. If I do ifconfig, it shows eth0 as 10.1.1.2, eth1 as 192.168.1.1 (correct) and ppp0 as a point to point connection with my correct isp's static ip address.
I cannot get any data I guess because this 10.1.1.2 is interfering for whatever reason. Is there any way to flush it out or is it another bug in 1.5 that I can fix by modifying a file to get rid of this random address?
I have gotten it to work once out of about 50 times by changing the role of the nic then back again. I shut it down to put another drive in and then same problem. When it did work it still showed the 10.1.1.2 address in the dashboard. Seems like a bug to me.
One other weird thing is a few times it would show an ip address in the gateway (network->gateways) that was not the static ip from the isp but it must have still been from their servers. The first two octets were the same and I could ping their server but no internet obviously.
Thanks again.
Edit: When I go back to modem->dhcp router->ebox server, it wipes out the 10.1.1.2 address and successfully gets an address from the router even though the nic is set to ppp0e.
I wonder if there is any train of thought as to whether the (($method eq 'dhcp') or ($method eq 'ppp')) is being a problem. Should 'ppp' go before 'dhcp' or simply exist by itself if you have a static isp address? I will have a play, but I thought that was for port forwarding, not necessarily isp connection. I'm out of my league, but hopefully someone can shed some light.
Thanks.