Isaac Schneider Posted June 8, 2009 Report Share Posted June 8, 2009 Hello, I have run across a bug when changing the network settings, system is not updating the OS config files. System is running v3.3.1.3177 with a single ethernet cable connected to lan port. Unit by default seems to be stuck with WAN port @ 192.168.1.99 and LAN DHCP. To bypass the gui I edited the following file. /etc/network/interfaces #This file was automatically generated by the IP PBX. auto lo iface lo inet loopback #eth0 is LAN Port auto eth0 iface eth0 inet static address 192.168.0.190 network 192.168.0.0 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.254 #eth1 is POTS-gateway Net auto eth1 iface eth1 inet static address 1.1.1.1 network 1.1.1.0 netmask 255.255.255.0 broadcast 1.1.1.255 #eth2 is WAN auto eth2 iface eth2 inet dhcp -Isaac Quote Link to comment Share on other sites More sharing options...
pbx support Posted June 8, 2009 Report Share Posted June 8, 2009 Sorry about that. This was an issue that was found sometime back and we have provided a fix for it. But the official release has not been out yet for this. You can download the latest on this here http://pbxnsip.com/cs410/update-3.4.0.3191.tgz Hello, I have run across a bug when changing the network settings, system is not updating the OS config files. System is running v3.3.1.3177 with a single ethernet cable connected to lan port. Unit by default seems to be stuck with WAN port @ 192.168.1.99 and LAN DHCP. To bypass the gui I edited the following file. /etc/network/interfaces #This file was automatically generated by the IP PBX. auto lo iface lo inet loopback #eth0 is LAN Port auto eth0 iface eth0 inet static address 192.168.0.190 network 192.168.0.0 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.254 #eth1 is POTS-gateway Net auto eth1 iface eth1 inet static address 1.1.1.1 network 1.1.1.0 netmask 255.255.255.0 broadcast 1.1.1.255 #eth2 is WAN auto eth2 iface eth2 inet dhcp -Isaac Quote Link to comment Share on other sites More sharing options...
edwardforgacs Posted June 9, 2009 Report Share Posted June 9, 2009 Yes, I can confirm this bug is happening on my system too with version 3.3.1.3177. At the moment it is preventing us from being able to use the device at all. Quote Link to comment Share on other sites More sharing options...
pbx support Posted June 9, 2009 Report Share Posted June 9, 2009 Yes, I can confirm this bug is happening on my system too with version 3.3.1.3177. At the moment it is preventing us from being able to use the device at all. So please download the version posted in the earlier response and update your system. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.