this has been looked at before, and it seems the issue is most likely the version of FreePBX I have installed ( SNG7-PBX16-64bit-2302-1) doesn’t have the drivers for the Network adaptor for this unit. The website shows me this is SNG 7.8.
One solution on the forum for a guy having the same problem was to try SNG 7.4 vs 7.5 with different outcomes depending on the unit he was installing on.
But how do I know which SNG 7 version is used in the individual files in the archive, so I can try different ones?
Without knowing what the hardware is
You could install FreePBX 17, which liklely has the driver needed
You could plug in a $10:00 usb to ethernet adapter.
Both methods would likely expose the hardware , then search for a RH7 driver to suit and download it, then you can add that to SNG7 from a thumb drive.
edit:
Apparently you will need
But only these OS are supported
Linux*
-
Linux Real Time Kernel 5.x and 4.x (only on Intel Ethernet E810
Series) -
Linux, v2.4 kernel or higher
-
Red Hat* Enterprise Linux* (RHEL) 9.4
-
Red Hat Enterprise Linux 8.10
-
SUSE* Linux Enterprise Server (SLES) 15 SP5
-
SUSE Linux Enterprise Server 12 SP5
-
Canonical* Ubuntu* 22.04 LTS
-
Canonical Ubuntu 20.04 LTS
-
Debian* 11
So I’ve gone down this track, but with Debian 12. Should I start again with Debian 11?
Any chance you could step me through how to install that driver pack? Are you saying I could download that onto a flashdrive and load it onto the beelink machine with FreePBX 16 loaded on it (as standalone OS)? That would take some CLI commands?
thanks
No, I won’t, it’s all in the link i posted 
For the ‘CLI’ averse, starting over with FreePBX 17 is by far the easiest way to go, it is based on debian 12 thus with native support, SNG7 is on the other hand, is moribund.
OK…Thanks. The link has the driver .zip -not sure about a how to. Happy to mess with the CLI to some extent. If at all possible, I’m keen to stick with FreePBX16 for now. (having tried it out now, I’d say17 isn’t ready for the CLI averse just yet imho) 
Have you tried it though ? If you did, which bit of installing or running it needed a ‘CLI’ that was too much for you?
I will point out that the ‘CLI’ (most use and mean ‘bash’) are essentially the same for both SNG7 (RedHat) and bookworm (Debian)
OK.
as far as installing FreePBX 17. I followed the directions on the official site, using Debian12. Got the GUI up and restored from my FreePBX16 system. Unable to reload. At this point I was unable to ssh via putty as I usually do. Enter the address and putty just diappears. So unable to use fwconsole command. Messed around with that, but couldn’t fix. (tips on restoring ssh access??)
So re-installed FPBX16-to try to install the drivers.
used this link: https://www.intel.com/content/www/us/en/support/articles/000005480/ethernet-products.html
Got as far as copying the zip file with the intel drivers from the usb, but at the next step found I needed to install Kernel-Devel.
Downloaded this (kernel-devel-3.10.0-1160.119.1.el7.x86_64) but was unable to copy this across to the server. It (ls) can see the file on the usb, but won’t recognize the filename when I try to copy it across. also, I’m not sure I’d know how to install that if I did get it across. Now I’m out of my depth.
So quite a bit there.
So different problem.
I assume that is you got the GUI up you had a working network and ssh access because you said you did. FreePBX, ssh, networking, webserver mail and php mariadb (mysql) and PHP all working, correct?
So your ‘Network’ is no longer ‘unavailable’ is only appropriate for SNG7 and not bookworm with a beelink 2.5gb intel Ethernet adapter.
So close this thread as resolved and open another with your next ‘out of my depth’ problem 
True enough. Got FPBX17 up on the Debian12 with network access which was, as you point out, my OG problem. Figuring out how to SSH into it so I can make it work is a separate thing.
but configured exactly the same in any linux, To my knowledge, it ‘just works’ on 17 until the firewall kicks in and you try and access from an un-trusted host, what problems are you trying to resolve?
It was this problem. I switched off firewall and that didn’t fix it. And I had allowed my network as trusted host during the setup of firewall. (working from memory now, but perhaps I couldn’t switch off firewall because I couldn’t get it to ‘update config.’ And couldn’t SSH in, and at that point I returned to trying FreePBX16 and so on and so on. )
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.