I may only be at the Fedora Server WG meeting today for a short time,
because of a doctor's appointment, so I wanted to mention something that
came up when I was reviewing the documentation for Fedora Server
Installation and Post Install Tasks.
I tested the Fedora Server Standard ISO image install on the following
TOSHIBA product: Satellite C650 v: PSC2EU-001027
Mobo: TOSHIBA model: Portable PC serial: <filter> BIOS: INSYDE
CPU: Topology: Dual Core model: Intel Core i3-2310M bits: 64 type: MT
arch: Sandy Bridge
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated
vendor: Toshiba America Info Systems driver: i915
Network: Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet
vendor: Toshiba America Info Systems driver: atl1c
Device-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver:
Since, the laptop has a built in wifi adapter, I decided to set up
networking during the install using that device. Fedora Server installed
without issue, but when I tried to connect to it remotely I could not.
- The system had received an internal IP address from my DHCP server. My
DHCP server could see the system connected to the network at the address it
was assigned. The Fedora Server login prompt correctly displayed the
internal IP address that it had been given.
- Yet, I could not ssh to the system. Cockpit would not come up when I
tried to access Cockpit from my workstation on the same LAN. I was unable
to ping the system as well.
- However, when I logged into the system directly, I had the correct IP
address connected through the wireless adapter, and I could do a "sudo dnf
update" without any problems.
I tried plugging in an Ethernet cable, which still didn't allow me to
connect remotely to the system, until I rebooted. After a reboot, I was
able to ssh, connect to Cockpit, and ping the system. However, when I
closed the lid of the laptop (putting the system to sleep) and then opened
the lid again later, once again coming out of sleep I have all of the same
connection issues that I had before. I'm not sure what is happening during
sleep that causes the remote connections to be lost. When I run "ip
address" it looks the same when I reboot and have the ethernet cable
plugged in as when I wake the system from sleep and run the command again.
I realize that connecting Fedora Server with wifi is not the most common
way to network a server, but I didn't find anything in the documentation
that mentioned that wifi connections would not allow remote access. So, I
believe this is a bug in Fedora Server 37 Beta, and one that would be good
to address before release of Fedora 37.
Show replies by thread