I had to set up the server using Ethernet cable because I needed the Broadcom firmware to access via wifi.
I have added the firmware and created a wifi connection, but I cannot connect to the server through the assigned IP on the wifi interface.
You need to provide more information.
On the server check that you are connected to your network.
ip addr
How are you connecting to the server? What error do you see?
What is the network info for your client machine?
ip addr
This has self-resolved itself. I have no idea how or why it decided to start working.
This morning, I tried to connect again. I toggled the active state of the WiFi interface off and on, and I am now able to connect using WiFi. I have disconnected Ethernet and can still access the server via WiFi
Background info requested below.
I am connected to the network via Ethernet. I can access the server on that IP address.
I am also connected to a different WiFi access point and it shows up in Network Manager and in my router app with an IP address reserved for the server. I cannot connect to the Cockpit interface nor a web app based service hosted on the server through that WiFi IP address. I can connect to both using the Ethernet IP address.
I need to disconnect the hard wire connection a use the server on WiFi.
This may be an issue of having both ethernet and wifi connected at the same time and both being in the same ip subnet on the LAN. What is shown with ip r when only the wifi is connected, as compared to when both wifi & ethernet are both connected.?
To get a clean comparison first boot with both connected and run that command.
Then disconnect the ethernet and reboot before repeating that command.
What I am suspecting is that this may be an issue caused by the timing for the order in which those interfaces are configured so the routing may not use the wifi as the default interface. The first interface configured usually becomes the default for routing.
They were on different subnets and different routers. The Ethernet was directly connected to the modem/router. The WiFi access point is connected to the modem/router. The modem just provides the internet connection to the WiFi router. All routing is done by the WiFi. Usually, I have nothing else connected to the modem.
I can see where it might have been confused by the setup, but since they were on different subnets and showing up in the WIFI router app as having an IP address, I didn’t consider that. Also, at one point, when I thought I had created the WiFi interface (I hadn’t) I disconnected Ethernet and lost access to the server. Now, with a working WiFi interface, I think it may have been a routing problem.
All good, now, I think. Thanks for jumping in.
Hi James,
Welcome to Fedora!
Yeah, from your stated scenario, I’ll bet you had a routing issue. Particularly if the machine that was trying to access the server via WiFi was not on the same subnet as the WiFi.