Hi!
An easy way to see if it makes a difference might be to remove the card temporarily…
The script you ran has quite a few problems that were present when I ran it over a month ago fixed, Back when I run it looks like something I did at one point somehow got me out of the no network connectivity problem.
Somehow, while trying to fix some of those problems, network connectivity got restored…
The A200 I have (and other DAHDI hardware (including another A200) another early tester had) seemed to play a part in our loss of network connectivity.
Mind you, there were other DAHDI and Wanpipe problems present that you should no longer have but I had to get unstuck from that loss of network connectivity to have them…
After that problem got apparently resolved I could not access the FreePBX GUI and I had to disable both the iptables and firewalld service if I recall correctly.
I do not recall anybody else mentioning this problem and I am not sure why this was needed. Not everyone has telephony hardware (like the A200) and not everyone’s setup essentially put the PBX in a DMZ of sorts…
(A real DMZ, a different subnet with it’s own firewall rules, usually more server than the main LAN…)
The other person who had network connectivity problem and telephony hardware had to restore from a backup so i do not know if he would have had the same problem or not…
To this day I still have one problem related to the Wanpipe drivers… About 4 of the about 5 minutes of the boot time of my system are taken by them:
re:
Sep 9 09:18:17 jester wanrouter: Configuring interfaces: w1g1
Sep 9 09:18:17 jester wanrouter: done.
Sep 9 09:18:17 jester wanrouter: Waiting for Dahdi /dev/dahdi …
Sep 9 09:22:42 jester systemd: wanrouter.service start operation timed out. Terminating.
Sep 9 09:22:42 jester systemd: Failed to start SYSV: WANPIPE WAN Router Initialization Script…
Sep 9 09:22:42 jester systemd: Unit wanrouter.service entered failed state.
Sep 9 09:22:42 jester systemd: wanrouter.service failed.
Sep 9 09:22:42 jester systemd: Starting LSB: Bring up/down networking…
Sep 9 09:22:43 jester network: Bringing up loopback interface: [ OK ]
Sep 9 09:22:43 jester kernel: sky2 0000:04:00.0 eth0: enabling interface
Looks like something times out at 09:22:42 after running since 09:18:17…
Interesting tidbit, can you see what gets initialized after the wanrouter?
Things works after that and if I stop and then start them once the system is up they take nowhere that time… They perform flawlessly as far as I can see, it’s only that initial initialization that fails in this way…
Keep us posted and good luck and have a nice day!
Nick