[SOLVED] SuSE LEAP 15 firewalld

scasey · 08-19-2018, 07:00 PM

Quote:

Originally Posted by LawsonRL

I am using the network bridge configuration because I planned to use name based virtual apache2 webservers. It has been a while since I installed this distribution (it has not worked since I installed it, but I do not give up easily) and I forget whether the system defaulted to the bridges, or if the system set up the network that way when I set up the virtual configuration. I will try NetworkManager to see what happens but I did download Centos 7 this afternoon. This has been way too much time to try to figure out what happened. I think I have landed on the "bleeding edge" rather than the "leading edge."

Thanks to all of you who have assisted me with this problem. I will answer any replies and close this thread out if and when I change to another distribution.

Virtual webservers shouldn't need a network bridge. I have around 70 domains on a single IP. The virtualization is managed in the webserver configuration, not in the networking.

You opened the thread with questions about firewalld because you thought that was the cause of the problem. It wasn't. You need to configure your networking. Follow ferrari's suggestion about how to do that.

LawsonRL · 08-19-2018, 07:44 PM

Quote:

Originally Posted by ferrari

I still don't understand why you created network bridges in the first place. Remove them and start over with IP addresses assigned to the ethernet network interfaces. For internet connectivity (as Sean already pointed out), you'll want a default route for the NIC connected to the internet-facing router.

The openSUSE Leap guide for configuring network connections via YaST (when using wicked) can be found here...
https://doc.opensuse.org/documentati...c.network.yast

I didn't create the network bridges, something I did to create virtual environment triggered their creation. I had never used them before nor could I see a need for them, although the documentation said they were wonderful.

I did not see this reply earlier, but I recently saw an email on my smartphone telling me that it was here. I read it and deleted the network bridges using Yast2 Network Settings. After deleting the network bridges, I verified that I could ping the DNS server, go to SuSe website, and connected to the system using PUTTY from my Windows desktop.

Thanks to everyone who took the time and brain power to help me get this figured out. Now, if someone could just tell me why the system configured itself with the network bridges and why they killed everything, including self updates.

LawsonRL · 08-19-2018, 08:01 PM

Quote:

Originally Posted by scasey

Virtual webservers shouldn't need a network bridge. I have around 70 domains on a single IP. The virtualization is managed in the webserver configuration, not in the networking.

You opened the thread with questions about firewalld because you thought that was the cause of the problem. It wasn't. You need to configure your networking. Follow ferrari's suggestion about how to do that.

******************

I didn't see the need for network bridges either, but they were there and I did not create them and I still don't see the need for them. I do recall reading something that said that they made virtual webservers easier. You are absolutely correct, I was asking about firewalld because I could not get connectivity and the firewalld version was less than 1 so I thought it had some kind of bug.

I saw ferrari's note later, did what it said, and now I am on the road. If you have some configuration files for apache and virtualization, etc. for 5 or 10 domains on a single IP that would be a fabulous assist for me to regain lost time getting this thing up. I think you can email whatever you can share with me here.

Again, thanks to you and everyone who took the time to help me.

ferrari · 08-19-2018, 09:03 PM

There are good guides showing how to get name-based virtual hosting running. For example...

https://httpd.apache.org/docs/2.4/vh...ame-based.html
https://www.maketecheasier.com/name-...alhost-apache/

Edit: When you're ready to tackle the apache configuration, my advice is to start a new thread with a descriptive title to attract the attention of those that can help. This thread is no longer about firewalld.

scasey · 08-20-2018, 02:53 AM

+1 to ferrari's advice.
Glad you got the server working.