Hi all, I had a good server but I wanted to make WebVirtmgr working and made an extra NIC.
Connection lost!
Now I plugged in a monitor and removed all the NIC’s and started all over again (network).
I still can’t connect, not even ping to the server. I did even stopt shorewall service. (If that’s the only thing to stop to stop firewall).
First output of db networks show
br0=bridge
gateway=192.168.0.1
ipaddr=192.168.0.134
netmask=255.255.255.0
role=green
br1=bridge
bootproto=none
gateway=192.168.0.1
ipaddr=192.168.0.136
netmask=255.255.255.0
role=green
enp0s31f6=ethernet
FwInBandwidth=
FwOutBandwidth=
bootproto=none
bridge=br1
role=bridged
ppp0=xdsl-disabled
AuthType=auto
FwInBandwidth=
FwOutBandwidth=
Password=
name=PPPoE
provider=xDSL provider
role=red
user=
virsh net-list gave me default and eth0
It was the first time I see my old eth0 back, I am used to see that name on ubuntu.
The description of my network?
Easy, I have a fyber connection 512 mbit, to a router, the router give dhcp.
And thats it. All the system get there ip address from that router or I give them a static.
Both br0 and br1 have static ip.
The server has an AD DS and WebVirtMgr running. Also httpd etc…
In Red Hat Enterprise Linux 7 [thus same in CentOS 7 and NethServer 7], udev supports a number of different naming schemes. The default is to assign fixed names based on firmware, topology, and location information. This has the advantage that the names are fully automatic, fully predictable, that they stay fixed even if hardware is added or removed (no re-enumeration takes place), and that broken hardware can be replaced seamlessly. The disadvantage is that they are sometimes harder to read than the eth0 or wlan0 names traditionally used. For example: enp5s0.
Can you ping any of the two IP addresses or, if httpd-admin service is running, access the server-manager using any of them? (If I recall correctly you use a custom port number for the server-manager, verify it didn’t change).
If not working, you could try to remove one of the bridges:
Identify the bridge used by AD (example: br0):
config show nsdc
Delete the other bridge (example uses br1):
db networks delete br1
ifconfig br1 down
brctl delbr br1
rm -f /etc/sysconfig/network-scripts/ifcfg-br1
service network restart
signal-event system-init
/var/log/messages might give some clues on the problem.
A problem is, the machine is here at home, after full configuration i have to take it to my classroom where i teach. The network sistuation there is totally different so i maybe have the same problems all over again.
You may just setup the Nethserver at home. Then configure a network client (laptop, school pc) to be in your home network by giving it an IP like 192.168.0.222 so you may reach the web UI of Nethserver with that client at school and then being able to configure your Nethserver to work in the school network.
Maybe you could try to configure your interface manually:
db networks set br0 bridge
db networks setprop br0 ipaddr 192.168.0.134
db networks setprop br0 netmask 255.255.255.0
db networks setprop br0 gateway 192.168.0.1
db networks setprop br0 role green
db networks delete enps31f6
db networks set eth0 ethernet
db networks setprop eth0 bridge br0
db networks setprop eth0 role bridged
db networks show => output should look similar to @mrmarkuz post
signal-event interface-update
Maybe you have to reboot. Important is “role=green” to be reachable.
I have allready reinstalled the system. Started all over again.
Everything is working fine now.
I want to thank Markus for his great post, I think I will use a lot from that page. Thanks!