Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
First my network wouldnt work and after a long time of trying I seem to have it fixed (I used the libvirtd networking guide to fix this)
Now, a few months later, I reboot my server and networking is again not working anymore.
The setup is as follows:
The goal is to have all these accessible from/to any of these devices
I need a bridge for this so I configured it.
The Dom0 I want to be accessible trough 192.168.1.11 and the DomU through 192.168.1.10
There is no dhcp needed.
I added a ifcfg-br0 config (with "Bridge" and not "bridge"/"BRIDGE" in it)
ifcfg-eth0 I configured to use br0.
In example configs I have seen that the bridge IP was assigned through dhcp. But I dont want to assign it through dhcp. So I configured the 192.168.1.11 address for it.
When I restart the networking service the Dom0 is accessible through 192.168.1.11 and can ping any other except the DomU.
If I do arp -n then I see that the HWaddress for the DomU is incomplete (aka no answer?).
If I do the same on the DomU (through the console) I see a HWaddress for the Dom0 (192.168.1.11), however this is the address of the br0 interface.
Now I wonder if eth0 is the physical interface, or br0.
I would think some interface in ifconfig should have an HWaddress that accepts all traffic.
The interface of the DomU (vifx.0 or something) and eth0 is added to the br0.
Does anyone knows what I do/understand wrong and explain to me?
Maybe I do not understand the bridge workings correctly.
THanks alot in advance!
EDIT: in the output of arp -n on the DomU I meant that the mac was shown of a tap interface instead of the br0 interface
I couldn't seem to find what was causing the problem but I fixed it as explained below.
The only thing weird for me was that I couldn't see a "Source Device" in virtmanager. And there is no way to select anything.
So I added a new NIC and had the possibilty to select a bridge, br0. I selected this one and created it.
After rebooting the DomU and configuring an IP on that interface, I was able to connect it.
So deleting the old one and adding a new one on the bridge interface should solve this.
I think this might be a bug as no Source Device was selected.
for anyone trying to solve this instead of using the previous workaround, you can try to edit the config file in: /usr/lib/xend/domains/