It seems that the firewall protecting our management portal was responsible for the issue we were having.
As noted in another thread we were experiencing timeout issues pulling the PF images during the installation process; We were able to resolve this issue with our firewall. What is not absolutely clear to us is if the problems with the Configurator, which used the same firewall, were caused by possible session issues on the firewall, or corruption in the images possibly created during the restarted installation image pulling process. During our various attempts at v11.2, 12.0 and 12.1, we saw some strange GUI artifacts, for example the Pulldowns that allows selection of 'ssl' for SMTP or 'timezone' for system clock were showing empty lists, but appeared populated after some GUI Previous/Next operations, which suggests to us the firewall and not image corruption was the root cause of our issues. A freshly deployed 12.1, without any timeouts during image pull, is now launching the Configurator with interface detection as we expect. This issue is resolved from our perspective, and seemed to be squarely in our court from the start. cheers, Ian On Mon, Jan 16, 2023 at 4:40 PM Ian MacDonald <i...@netstatz.com> wrote: > Hello Packetfence Users, > > We tested a fresh install of v12.1 on a freshly spun up Debian 11.6 > today. > > > packetfence_12.1.0+20230116163629+748667390+0011+maintenance~12~1+bullseye1_all.deb > > Prior to installing packetfence, we deployed some basic packages, listed > here as part of our default staging script. I do not see any reason any of > these would cause detection scripts for the interfaces to fail, and both > ifconfig and ip are providing valid output on the CLI. > > apt install gnupg arptables dnsutils unzip pigz mtr-tiny less vim screen > curl iperf3 wget tcpdump dialog subnetcalc vlan bridge-utils ethtool iftop > iotop deborphan apt-show-versions ethtool pv systemd-timesyncd > > The configurator however did not detect any interfaces. The simple > interface configuration is shown below, for the Management, Registration > and Isolation (eth0, eth1, eth2 respectively). > > ip addr output is below. The configurator web page is stuck at step 1, > with no interfaces shown to select for the Management network. Our next > step will be to add our interfaces into the configuration manually via CLI > and see if the configurator picks them up, or possibly revert to v11.1 and > see if it happens there too. > > Any insights here on why this might be happening appreciated. > > pf5:~# ip addr > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether 00:16:3e:dc:7d:fd brd ff:ff:ff:ff:ff:ff > inet 10.2.1.2/24 brd 10.2.1.255 scope global eth0 > valid_lft forever preferred_lft forever > inet6 fe80::216:3eff:fedc:7dfd/64 scope link > valid_lft forever preferred_lft forever > 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether 00:16:3e:dc:7d:fe brd ff:ff:ff:ff:ff:ff > inet 10.2.2.2/24 brd 10.2.2.255 scope global eth1 > valid_lft forever preferred_lft forever > inet6 fe80::216:3eff:fedc:7dfe/64 scope link > valid_lft forever preferred_lft forever > 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether 00:16:3e:dc:7d:ff brd ff:ff:ff:ff:ff:ff > inet 10.2.3.2/24 brd 10.2.3.255 scope global eth2 > valid_lft forever preferred_lft forever > inet6 fe80::216:3eff:fedc:7dff/64 scope link > valid_lft forever preferred_lft forever > 153: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue > state DOWN group default > link/ether 02:42:e7:4c:45:ca brd ff:ff:ff:ff:ff:ff > inet 100.64.0.1/24 brd 100.64.0.255 scope global docker0 > valid_lft forever preferred_lft forever >
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
