Thanks for the answer I think I know where me problem is 'cause I use a real
Ethernet switch to connect the controller and ovs in the same LAN and two hubs
to connect the hosts to the switch.
192.168.0.0/24 -------------
_______________ --------------- ____________ --------------
| POX | | Eth Sw
| | OVS |
------------- ----------------
--------------
/ \
/ \
_________/
\___________
|
|
-------------
---------------
| Hub |
| Hub |
------------- --------------
|
|
10.0.0.0/24
10.0.1.0/24
|
|
-------------
---------------
| Host 1 | | Host 2 |
------------
---------------
So if I get it right I have to remove the hubs and the ethernet siwtch so I
dont have that message?
Thanks so much!Subject: Re: [pox-dev] Problems with the connection with ovs
From: [email protected]
Date: Wed, 17 Apr 2013 23:01:27 -0700
CC: [email protected]
To: [email protected]
On Apr 17, 2013, at 3:50 PM, Mayumi Park Campos wrote:I have a problem with the
conection between the pox controller and openvswitch.
Are you sure you have a problem?
And on the controller this is what I see: WARNING:forwarding.l2_learning:Same
port for packet from 00:0c:ce:1f:10:1d -> 00:0c:ce:1f:10:1d on
00-14-22-4b-5e-60.2. Drop.DEBUG:forwarding.l2_learning:86474710624: flood
00:0c:ce:1f:10:1d -> 01:00:0c:cc:cc:ccDEBUG:forwarding.l2_learning:86474710624:
flood 00:0c:ce:1f:10:1d -> 01:00:0c:00:00:00WARNING:forwarding.l2_learning:Same
port for packet from 00:0c:ce:1f:10:1d -> 00:0c:ce:1f:10:1d on
00-14-22-4b-5e-60.2. Drop.
But I don´t understand why I get that message.
Could anyone help me to understad
l2_learning will not try to forward packets out of the same port that they
arrived from. This is because if the packet was received from that segment,
then if the recipient was also on that segment, it will have also received it
-- there's no point sending it back out. That's the case that this WARNING
message refers to. Usually it's caused by being plugged into a hub or a real
Ethernet switch which hasn't learned a destination yet.
This case is a bit weird, though. It looks like you have some strange packets
where the destination address is the same as the sending address. It looks
like they're coming from the br0 interface; you might try looking for them with
Wireshark. In this case, of course it looks like the recipient is out the same
port it was received on -- the recipient seems to have been the sender!
Dropping these packets is the right thing to do despite the warning in the log.
-- Murphy
