I just installed from SNG7-FPBX-64bit-1703-1.iso (downloaded from the Asia server which didn’t have the 1706 file) using the Recommended option. The install completed successfully and after the reboot and logging in to the console as root the welcome message showed the eth0 interface with no ip address. Trying ifconfig eth0 up created an ipv6 address but ipv4.
Looking at the ifcfg-eth0 file showed onboot=no which I changed to “yes” and following a reboot the ipv4 address was displayed OK. The interface was set to use DHCP.
I’ve not found a reference to this elsewhere on the forum, so I’m putting it here fwiw in case anyone else runs into it.
Generally a VOIP server SHOULD have a static IP that you can rely on, otherwise you will have ongoing problems as the various endpoints can’t find it if your dhcp server decides to reassign it. That’s just a basic netowrking concept, but easy to implement. So what kind of guy is your DHCP server? you can probably “PEG” it there, if not look at the GUI to “PEG” the IP appropriately
If your router cant do IPV4 then you have a bigger problem.
Yes, I agree re the static ip, but that wasn’t the problem. Normally, after a new installation, I’d expect to login to the root account, see what the ip address is and then go to the admin gui (using the assigned dhcp address) to set the static address. In my case, the eth0 interface wasn’t enabled (onboot=no) so there was no assigned ip address to use.
It just seemed unusual that the ethernet interface would be disabled by default at the end of a normal installation.
Again, I wouldn’t rely on FreePBX to properly handle your network “edge case” , how would it know what you want it to do? How would it provide routing ? etc, etc, etc
Linux is way better set to provide that function, you just need to RTFM
I’m not an edge case, I fully intend applying a static ip address to the server, but if the server had no dhcp address assigned to begin with then I can’t access the admin gui to apply the static ip.
All I’m saying is that I installed Freepbx and the Ethernet interface was disabled and that I think that is unusual.
Again, there is nothing wrong with my network, after I set the ethernet interface to be enabled on boot and rebooted the Freepbx server, there was a dhcp address assigned, I logged into the admin gui and assigned a static ip, job done.
But I should not have had to edit the ifcfg-eth0 file in order to get the initial ip address.
I don’t believe anyone else has that problem, maybe don’t use the “I just installed from SNG7-FPBX-64bit-1703-1.iso (downloaded from the Asia server which didn’t have the 1706 file”
Dave, thanks for this. I also had a similar problem. Installed a fresh VM using SNG7-FPBX-64bit-1707.iso. VM had 2 NICs, but only eth0 would show. Eth1 was listed with no ipv4 address from the console and would not appear in the drop-down under Admin/System Admin/Network Settings/Network Interface.
For those who are new at this, I’ll share what I did in case it also helps you:
(My interface was eth1, but substitute your one as appropriate)
ifconfig
to check your interfaces. If you have an interface that is present, but not connected, you’ll probably see it has no ip4 address. cat /etc/sysconfig/network-scripts/ifcfg-eth1
You will see that ONBOOT=no
Change it to yes nano /etc/sysconfig/network-scripts/ifcfg-eth1
Edit, then CtrlO to save and CTRLX to exit. Restart the network interfaces /etc/init.d/network restart
Now you will see the interface is available to configure via the GUI and will show in the drop-down.
My problem is if i set a static IP for eth0 the nic will not start on boot.
it is set to.
if i go back to DHCP it works fine.
i am only having this issue with 1707-1 distro on sangoman 60 servers.
if i reload it with 10.13.66-64bit i do not have this issue.
also if i do a fwconsole restart the nic will come up.
any ideas
Thanks man, this just solved my issue!
I downloaded the latest v14 FreePBX issue from the official freepbx website, transferred it to a USB, installed on a micro server and it just wouldn’t get the IP address automatically! When I checked, true enough, ONBOOT was set to no! Why do they ship them like this?? Like the original poster, I would usually install freepbx with a automatic IP address assigned by DHCP, then navigate to it from GUI and set the static there after configuring the system.
Don’t quite understand why they changed it to be like this on a fresh install…
GOLD. 5/4/2018 I downloaded the freepbx distro from the website. I guess its still has an issue. But I notice that It randomly does it. because I put together another system with the same Iso and it worked fine. go figure.
r5eR FAug '17
Dave, thanks for this. I also had a similar problem. Installed a fresh VM using SNG7-FPBX-64bit-1707.iso. VM had 2 NICs, but only eth0 would show. Eth1 was listed with no ipv4 address from the console and would not appear in the drop-down under Admin/System Admin/Network Settings/Network Interface.
For those who are new at this, I’ll share what I did in case it also helps you:
(My interface was eth1, but substitute your one as appropriate)
ifconfig
to check your interfaces. If you have an interface that is present, but not connected, you’ll probably see it has no ip4 address.
cat /etc/sysconfig/network-scripts/ifcfg-eth1
You will see that ONBOOT=no
Change it to yes
nano /etc/sysconfig/network-scripts/ifcfg-eth1
Edit, then CtrlO to save and CTRLX to exit. Restart the network interfaces
/etc/init.d/network restart
Now you will see the interface is available to configure via the GUI and will show in the drop-down.
Why not just assign the static IP during the install? I’ve never had this issue but I always set a static during an install, and I typically do a couple of installs a week at the least.