SUCCESS !!! BLUE WiFi clients now get IP addr and can connect. The backup restore not yet been done, but the BLUE DHCP has been enabled via the gui. K) Again, another full install of 163 from CD, but this time replaced the ‘USB to Ethernet’ adapter for BLUE with a newly purchased unit (like I did for GREEN earlier on to get it going). Still no DHCP response on BLUE, and the stream of ‘MAC CTRL’ packets continue. DHCP on BLUE has been disabled and re-enabled via gui. BLUE iface still with same USB to Ethernet. J) another full reinstalled of 163 from CD. Hoped here that after the reboot, and setting back to NATIVE, that this would reinitialize the port and/or adapter. The USB to Ethernet (DLink) iface no longer showed active LED. I) from ipFire’s gui ‘Zone Configuration’ i disabled BLUE (was set to NATIVE), and rebooted ipfire. Turns out the BLUE iface, was constantly sending (per WireShark descript) PROTOCOL=‘MAC CTRL’, DEST=‘Spanning-tree-(for-bridges)_01’, INFO=‘Pause: pause_time: 0 quanta’, and INFO=‘Pause: pause_time: 65535 quanta’ H) this time decided to wireShark capture what all the blinking was about, so I connected directly to the BLUE’s USB to Ethernet adapter iface (Manufact DLink). WiFi clients were not getting DHCP ip addressess, and the other unmanaged switch (DLink) was also showing the same rapid led blinking like I previously had on GREEN. G) discovered that BLUE was acting same as GREEN previously. Likely the latter, as you will see below the same thing was happening to the BLUE interface.
So either wiping the SD card, or a new USB to Ethernet device did the trick. (no IP address given to client via DHCP)į) I zero’s out the SD card i use for the ipFire (dd if=/dev/zero of=/dev/sdb), replaced the ‘USB to Ethernet’ adapter i use for the GREEN iface with a new adapter, and re-installed 163 from CD. The led indicator on the unmanaged switch connected to GREEN iface was blinking constantly about 3 times per sec.Ĭ) I cold restarted my 2 unmanaged switches one for GREEN (Cisco SHO) and one for BLUE (DLink)ĭ) i reinstalled 163 from CD. The cmd interface also appeared frozen, so after apout 10 minutes I powered off and did a restart.ī) after restart, I could not get a gui session. Pakfire kept giving an error saying there was already a pakfire session running. (where gui is mentioned, it means the ipFire web admin configure screen)Ī) home page indicated a upgrade from 161 to 163 was available. Not looking for a solution here, but rather providing my notes here mainly as help if someone else comes across the same scenario. I ran into similar issues when upgrading from 161 to 163.
0 kommentar(er)
