[opensuse] Question about Ethernet setup
I have following setup: PC A: two network cards with a) mainboard network branched to a router - internet and set in opensuse as eth0 b) a bridge (created to when I run an instance of KVM to give it access c) an Ethernet card PCI-e Intel that has a static IP and should only listen on a specific private range. It is dedicated to the private internal network and is set as internal zone in the firewall. It should "talk" for learning purposes via ssh to a PC B on the home network. When I do set a) eth0 as DHCP IPv4, only no ip, automatic zone b) IPv4 DHCP dynamic IP linked to eth0 -automatic zone (or external zone). and c) eth1 ipv4 static IP, internal zone. I have no internet. I do not understand why. All this is in wicked. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
I have following setup:
PC A: two network cards with a) mainboard network branched to a router - internet and set in opensuse as eth0 b) a bridge (created to when I run an instance of KVM to give it access c) an Ethernet card PCI-e Intel that has a static IP and should only listen on a specific private range. It is dedicated to the private internal network and is set as internal zone in the firewall. It should "talk" for learning purposes via ssh to a PC B on the home network.
When I do set a) eth0 as DHCP IPv4, only no ip, automatic zone b) IPv4 DHCP dynamic IP linked to eth0 -automatic zone (or external zone). and c) eth1 ipv4 static IP, internal zone.
I have no internet. I do not understand why. All this is in wicked.
I assume you mean "no internet on PC A" - what is the routing on PC A at this point? You should have a default route that points to your internet router. -- Per Jessen, Zürich (27.3°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
I have following setup:
PC A: two network cards with a) mainboard network branched to a router - internet and set in opensuse as eth0 b) a bridge (created to when I run an instance of KVM to give it access c) an Ethernet card PCI-e Intel that has a static IP and should only listen on a specific private range. It is dedicated to the private internal network and is set as internal zone in the firewall. It should "talk" for learning purposes via ssh to a PC B on the home network.
When I do set a) eth0 as DHCP IPv4, only no ip, automatic zone b) IPv4 DHCP dynamic IP linked to eth0 -automatic zone (or external zone). and c) eth1 ipv4 static IP, internal zone.
I have no internet. I do not understand why. All this is in wicked.
Where don't you have internet? Have you FW_ROUTE="yes" FW_MASQUERADE="yes" in your firewall setup? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data giovedì 24 agosto 2017 16:39:50 CEST, Peter Suetterlin ha scritto:
stakanov wrote:
I have following setup:
PC A: two network cards with a) mainboard network branched to a router - internet and set in opensuse as eth0 b) a bridge (created to when I run an instance of KVM to give it access c) an Ethernet card PCI-e Intel that has a static IP and should only listen on a specific private range. It is dedicated to the private internal network and is set as internal zone in the firewall. It should "talk" for learning purposes via ssh to a PC B on the home network.
When I do set a) eth0 as DHCP IPv4, only no ip, automatic zone b) IPv4 DHCP dynamic IP linked to eth0 -automatic zone (or external zone). and c) eth1 ipv4 static IP, internal zone.
I have no internet. I do not understand why. All this is in wicked.
Where don't you have internet? Have you FW_ROUTE="yes" FW_MASQUERADE="yes" in your firewall setup?
Thanks to both for answering. I was trying to answer when I got another blackscreen here (a new 42.3 feature on ironlake based notebooks). So in the meanwhile: I should have internet only on eth0 (which was wrongly renamed eth1 for reasons that I do not understand. It is the eth of the mainboard. I then have a eth1 pci-e card that handles only internal traffic and should be set to inner zone (no restrictions). Traffic on that card should have no possibility to access the internet. It will be handled by a little dedicated router. The bridge is there for kvm and should allow the virtualized systems to access the internet via eth0. So, first I looked for sudo route and got that I had the default route that was on the network not branched to the router. So I found out about the naming and renamed the whole thing. Then I tried to set up the bridge for KVM and linked it to eth0. However then, when I do this I have no default route any more. If I just have the two cards it seems that for reasons I do not understand, eth1 is preferred over eth0. So far so good, i did eliminate the eth1 (unconfigured and did eliminate the bridge and i have now at least internet. Now I will have to find out why I cannot link the eth0 to the bridge for kvm and have the eth1 separately. eth1 has static IP, eth0 is dhcp btw. When I set up the bridge it gets: eth0 non, bridge via dhcp (ipv4 only in my case), and eth1 static on another private address range. I will check for the firewall settings now. masquerade I recall having it set. FW route yes I did not check. For which should it be set when I have eth0 and br0? For br0? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
I should have internet only on eth0 (which was wrongly renamed eth1 for reasons that I do not understand. It is the eth of the mainboard.
Enumeration of network interfaces follows the sequence in which their drivers are loaded. You can change it with YaST or by directly editing /etc/udev/rules.d/70-persistent-net.rules
I then have a eth1 pci-e card that handles only internal traffic and should be set to inner zone (no restrictions). Traffic on that card should have no possibility to access the internet. It will be handled by a little dedicated router. The bridge is there for kvm and should allow the virtualized systems to access the internet via eth0.
Okay.
So, first I looked for sudo route and got that I had the default route that was on the network not branched to the router. So I found out about the naming and renamed the whole thing. Then I tried to set up the bridge for KVM and linked it to eth0. However then, when I do this I have no default route any more.
In that setup, eth0 does not have the address, br0 will - but you'll have to enable dhcp for br0.
If I just have the two cards it seems that for reasons I do not understand, eth1 is preferred over eth0.
What do you mean by "preferred" ?
Now I will have to find out why I cannot link the eth0 to the bridge for kvm and have the eth1 separately. eth1 has static IP, eth0 is dhcp btw. When I set up the bridge it gets: eth0 non, bridge via dhcp (ipv4 only in my case), and eth1 static on another private address range.
That sounds good. What are you missing here? -- Per Jessen, Zürich (25.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
I should have internet only on eth0 (which was wrongly renamed eth1 for reasons that I do not understand. It is the eth of the mainboard.
Enumeration of network interfaces follows the sequence in which their drivers are loaded. You can change it with YaST or by directly editing /etc/udev/rules.d/70-persistent-net.rules
I then have a eth1 pci-e card that handles only internal traffic and should be set to inner zone (no restrictions). Traffic on that card should have no possibility to access the internet. It will be handled by a little dedicated router. The bridge is there for kvm and should allow the virtualized systems to access the internet via eth0.
Okay.
So, first I looked for sudo route and got that I had the default route that was on the network not branched to the router. So I found out about the naming and renamed the whole thing. Then I tried to set up the bridge for KVM and linked it to eth0. However then, when I do this I have no default route any more.
In that setup, eth0 does not have the address, br0 will - but you'll have to enable dhcp for br0.
If I just have the two cards it seems that for reasons I do not understand, eth1 is preferred over eth0.
What do you mean by "preferred" ? Actually you answered that above. As the driver for the pci-e was loaded before, the eth0 was attributed from mainboard to pci-e and the default route
In data venerdì 25 agosto 2017 15:20:29 CEST, Per Jessen ha scritto: pointed to ... the internal network without internet.
Now I will have to find out why I cannot link the eth0 to the bridge for kvm and have the eth1 separately. eth1 has static IP, eth0 is dhcp btw. When I set up the bridge it gets: eth0 non, bridge via dhcp (ipv4 only in my case), and eth1 static on another private address range.
That sounds good. What are you missing here? You gave me quite some info I was missing. Will try to set it up to see if (toghether with the firewall settings) the thing will work. Will report back here.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data venerdì 25 agosto 2017 15:20:29 CEST, Per Jessen ha scritto:
stakanov wrote:
I should have internet only on eth0 (which was wrongly renamed eth1 for reasons that I do not understand. It is the eth of the mainboard.
Enumeration of network interfaces follows the sequence in which their drivers are loaded. You can change it with YaST or by directly editing /etc/udev/rules.d/70-persistent-net.rules
I then have a eth1 pci-e card that handles only internal traffic and should be set to inner zone (no restrictions). Traffic on that card should have no possibility to access the internet. It will be handled by a little dedicated router. The bridge is there for kvm and should allow the virtualized systems to access the internet via eth0.
Okay.
So, first I looked for sudo route and got that I had the default route that was on the network not branched to the router. So I found out about the naming and renamed the whole thing. Then I tried to set up the bridge for KVM and linked it to eth0. However then, when I do this I have no default route any more.
In that setup, eth0 does not have the address, br0 will - but you'll have to enable dhcp for br0.
If I just have the two cards it seems that for reasons I do not understand, eth1 is preferred over eth0.
What do you mean by "preferred" ? Actually you answered that above. As the driver for the pci-e was loaded before, the eth0 was attributed from mainboard to pci-e and the default route pointed to ... the internal network without internet.
Yes, when you have two interfaces that both use DHCP, you need to specify which one gets to set the default route. See DHCLIENT_SET_DEFAULT_ROUTE in the network config. -- Per Jessen, Zürich (26.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/25/2017 08:12 AM, stakanov wrote:
If I just have the two cards it seems that for reasons I do not understand, eth1 is preferred over eth0.
Always worth a trip by: https://wiki.archlinux.org/index.php/Network_bridge after reading: https://wiki.archlinux.org/index.php/Network_configuration#Device_names -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data sabato 26 agosto 2017 07:26:00 CEST, David C. Rankin ha scritto:
On 08/25/2017 08:12 AM, stakanov wrote:
If I just have the two cards it seems that for reasons I do not understand, eth1 is preferred over eth0.
Always worth a trip by:
https://wiki.archlinux.org/index.php/Network_bridge
after reading:
https://wiki.archlinux.org/index.php/Network_configuration#Device_names
Thank you very much! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
David C. Rankin
-
Per Jessen
-
Peter Suetterlin
-
stakanov