I can’t connect to any website besides the one running on my computer. No other computer can connect to my website.
Back Story: I was trying to get a new CA via Lets Encrypt. And it just couldn’t complete - I finally got it all to work - yeah! - But the problem started shortly there after. I had to open ports 80, and 443 via Yast to allow certbot to connect to my pc so it could generate the CA. Okay, did that, and certbot was able to connect and do it’s thing. And then I was able to connect to my pc from other devices on my local network. Everything was good.
A couple hours later I tried accessing Accuweather.com Nope. Then a News website. Nope. Then my own website on my own pc. Nope. I kept getting “This site can’t be reached - DNS address could not be found” error messages.
When I try to connect to my webserver from other devices on my network, I get: net::ERR_ADDRESS_UNREACHABLE errors.
And then I fired up Wireshark, only to see a very limited set of protocols. Specifically, STP, MDNS, and ICMP messages. So I can see packets from all hosts on my network using those protocols,
So I’m pretty sure the issue is with my fire wall. I didn’t use any tool other then Yast. I can’t see how I broke it with Yast, and I can’t figure out how to fix it with Yast.
The openSUSE firewall is an ingress firewall only, so that won’t be causing connectivity issues for you.
Getting an “address unreachable” error means that your routing table is likely not set up correctly.
Start by opening a terminal and running the route command, and look for a line that shows (under the ‘destination’ column) the word ‘default’. I’m going to guess that you’re missing that line.
What desktop are you using, and (more importantly) which network management tool is in use?
You can probably correct it by simply rebooting if nothing you changed was saved permanently - otherwise, using NetworkManager or YaST network management is probably how you will want to fix it. Specific steps depend on what you’ve got installed.
You need to establish a network connection with a router first. Are you using NetworkManager to do this? Are you connecting via Wi-Fi or Ethernet? More details please.
An “in between”.
Please always copy/paste computer output complete: the prompt-command line, all output up to and including the next prompt line. Then there is no need to explain what you did, because we see it. Also no need to say “return nothing”, because we see it.
Okay, this is where the rubber meets the road, so to say. I had NetworkManager installed, and after trying everything I could think of for around 3 hours, I switched to wicked. And after a couple of more hours of pounding on the keyboard, I switched back.
I’m using kde plasma desktop and wicked at this point. I’'m not married to wicked, I was just trying it because it seemed to allow me greater access…
Is it correct to assume that in both cases you use DHCP to get IP address (and also your default route, which you haven’t)?
Or do you use a fixed IP address (which is not too strange when you have a web server running). In which case you also should define at least the default route also manually.
I don’t know what a ‘sticky’ is. Anyway, I appreciate all the help I can get. Please forgive me if I ever seem rude, I’m probably just being blunt. And I’m also probably a jerk. No worries.
I’m less familiar with Wicked, but basically, in the network configuration there should be an option to do routing configuration, and you can just add 0.0.0.0 as a destination with a route that points at the internal address of your router, using the network interface on your system that connects to that network.
On my system, that means a default route looks like this (from ip route):
ip route | grep default
default via 172.16.42.1 dev enp2s0 proto dhcp src 172.16.42.42 metric 100
This is defined by DHCP in my setup, so if I lost it, I would either restart the system or just use dhcpcd to re-acquire the DHCP address and network info.
But if that’s not working, I’d use NetworkManager (which is what I have set up) and define it here (I’m using GNOME):
Because I’m using DHCP to provide that info, it’s set to “automatic”, but a manual setup would use values destination: 0.0.0.0 mask: 0.0.0.0, gateway: 172.16.42.1 (which is my router’s internal address), and probably leave the metric blank (my route output shows it set to 100, but I’m not sure that actually makes a difference since it’s a single connection - the metric is used to define a preferred route).
Don’t worry about getting the info copied/pasted from the system you’re having problems with. Those of us helping understand the situation well enough at this point to not need that.
On a semi-related note, something that I started doing years ago was using static assignments in my DHCP server, so the addresses are still ‘fixed’, but also are managed by the DHCP server. I used to do a range of dynamic addresses and a range of fixed addresses, but found it easier to just manage everything at the DHCP server - that helps ensure that DNS, default route, and any other network configuration parameters that can be served up via DHCP are consistent with all systems on my network.
