[ovs-discuss] Physical Ip Address

[fantonio at student.dei.uc.pt]

Thank you for the reply.
I read the FAQ looking for a solution which solve my problem. I need  
the devices of LAN still see the physical NIC of my PC-Linux as a  
IP-MAC and not only MAC. It means when PC-LINUX recieve an ARP, it  
should reply with the information of IP-MAC.

Regards,
Filipe

Quoting Justin Pettit <jpettit at nicira.com>:

> On Feb 28, 2014, at 2:59 PM, filipe Antonio  
> <fantonio at student.dei.uc.pt> wrote:
>
>> I installed an OVS in a PC-Linux. When I add the WNIC to a bridge of
>> OVS, it loose IP connectivity with the gateway. I need the LAN devices
>> still recognize the IP address of the WNIC of PC-Linux. How can I do that?
>
> I think this FAQ entry will answer your question:
>
> Q: I created a bridge and added my Ethernet port to it, using commands
>    like these:
>
>        ovs-vsctl add-br br0
>        ovs-vsctl add-port br0 eth0
>
>    and as soon as I ran the "add-port" command I lost all connectivity
>    through eth0.  Help!
>
> A: A physical Ethernet device that is part of an Open vSwitch bridge
>    should not have an IP address.  If one does, then that IP address
>    will not be fully functional.
>
>    You can restore functionality by moving the IP address to an Open
>    vSwitch "internal" device, such as the network device named after
>    the bridge itself.  For example, assuming that eth0's IP address is
>    192.168.128.5, you could run the commands below to fix up the
>    situation:
>
>        ifconfig eth0 0.0.0.0
>        ifconfig br0 192.168.128.5
>
>    (If your only connection to the machine running OVS is through the
>    IP address in question, then you would want to run all of these
>    commands on a single command line, or put them into a script.)  If
>    there were any additional routes assigned to eth0, then you would
>    also want to use commands to adjust these routes to go through br0.
>
>    If you use DHCP to obtain an IP address, then you should kill the
>    DHCP client that was listening on the physical Ethernet interface
>    (e.g. eth0) and start one listening on the internal interface
>    (e.g. br0).  You might still need to manually clear the IP address
>    from the physical interface (e.g. with "ifconfig eth0 0.0.0.0").
>
>    There is no compelling reason why Open vSwitch must work this way.
>    However, this is the way that the Linux kernel bridge module has
>    always worked, so it's a model that those accustomed to Linux
>    bridging are already used to.  Also, the model that most people
>    expect is not implementable without kernel changes on all the
>    versions of Linux that Open vSwitch supports.
>
>    By the way, this issue is not specific to physical Ethernet
>    devices.  It applies to all network devices except Open vswitch
>    "internal" devices.
>
> Using a wireless NIC can also have some other issues, so if you run  
> into additional problems, I'd recommend looking at the FAQ.
>
> --Justin
>
>
>