This is not working.
I send ping 193.XX.34.31 response is from eth0 not eth1 or br0
deb64:~# ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP qlen 1000
link/ether 00:50:56:ba:00:01 brd ff:ff:ff:ff:ff:ff
inet 193.XX.215.4/22 brd 193.XX.215.255 scope global eth0
inet6 fe80::250:56ff:feba:1/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc pfifo_fast state
DOWN qlen 1000
link/ether 00:50:56:ba:00:11 brd ff:ff:ff:ff:ff:ff
inet 193.XX.213.32/22 brd 193.XX.215.255 scope global eth1
4: br0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UNKNOWN
link/ether 00:50:56:ba:00:11 brd ff:ff:ff:ff:ff:ff
inet 193.XX.213.30/22 brd 193.XX.215.255 scope global br0
inet6 fe80::250:56ff:feba:11/64 scope link
valid_lft forever preferred_lft forever
5: vif1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 00:23:20:c9:49:bc brd ff:ff:ff:ff:ff:ff
6: vif2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 00:23:20:aa:08:b7 brd ff:ff:ff:ff:ff:ff
7: vif3: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UNKNOWN
link/ether 00:23:20:e2:b7:ef brd ff:ff:ff:ff:ff:ff
inet 193.XX.213.31/22 brd 193.XX.215.255 scope global vif3
inet6 fe80::223:20ff:fee2:b7ef/64 scope link tentative flags 08
valid_lft forever preferred_lft forever
8: vi0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 00:23:20:b1:f6:57 brd ff:ff:ff:ff:ff:ff
Different host:
template:~# arp -a
? (193.XX.213.30) at 00:50:56:ba:00:01 [ether] on eth0
? (193.XX.213.31) at 00:50:56:ba:00:01 [ether] on eth0
Now we see packet is out from eth0 mac adress: 00:50:56:ba:00:01
but should go out from eth1 br0 on mac 00:50:56:ba:00:11 or from br0 or
vif3
My configuration:
Who tell me way this not working???
Ping should go out from eth1 or br0 thats right?
I have VMware virtualization for this ifrastructure.
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
193.34.212.0 * 255.255.252.0 U 0 0 0
eth0
193.34.212.0 * 255.255.252.0 U 0 0 0 br0
193.34.212.0 * 255.255.252.0 U 0 0 0
vif3
default 193.34.215.254 0.0.0.0 UG 0 0 0 br0
default 193.34.215.254 0.0.0.0 UG 0 0 0
eth0
deb64:~# ovs-vsctl list-ports br0
eth1
vi0
vif1
vif2
vif3
deb64:~# ovs-vsctl list Interface
_uuid : 455940d8-ba07-402b-9b1a-6522dd696b51
external_ids : {}
ingress_policing_burst: 0
ingress_policing_rate: 0
mac : []
name : "vif1"
ofport : 1
options : {}
type : internal
_uuid : b66015b4-63b2-4216-a57a-24ac8c1c52dd
external_ids : {}
ingress_policing_burst: 0
ingress_policing_rate: 0
mac : []
name : "vi0"
ofport : 5
options : {}
type : internal
_uuid : d102af51-45b8-4d8f-8184-60dd922533a6
external_ids : {}
ingress_policing_burst: 0
ingress_policing_rate: 0
mac : []
name : "vif3"
ofport : 4
options : {}
type : internal
_uuid : b242eadd-58ed-4975-870a-d06649e167d1
external_ids : {}
ingress_policing_burst: 0
ingress_policing_rate: 0
mac : []
name : "br0"
ofport : 65534
options : {}
type : ""
_uuid : 389ad6af-ec0a-4074-a4cc-60d81d603393
external_ids : {}
ingress_policing_burst: 0
ingress_policing_rate: 0
mac : []
name : "vif2"
ofport : 3
options : {}
type : internal
_uuid : 90e990e7-b4f2-4953-a2c6-2fd0b6973569
external_ids : {}
ingress_policing_burst: 0
ingress_policing_rate: 0
mac : []
name : "eth1"
ofport : 2
options : {}
type : ""
deb64:~# ovs-vsctl list Port
_uuid : 7644a7e1-df29-48e0-8d25-fd29eac9def1
bond_downdelay : 0
bond_fake_iface : false
bond_updelay : 0
external_ids : {}
fake_bridge : false
interfaces : [b66015b4-63b2-4216-a57a-24ac8c1c52dd]
mac : []
name : "vi0"
other_config : {}
tag : []
trunks : []
_uuid : 7e4a0626-dfd8-4bbc-9ad3-a21f3513cd84
bond_downdelay : 0
bond_fake_iface : false
bond_updelay : 0
external_ids : {}
fake_bridge : false
interfaces : [90e990e7-b4f2-4953-a2c6-2fd0b6973569]
mac : []
name : "eth1"
other_config : {}
tag : []
trunks : []
_uuid : bedca966-6e73-4e8b-b9b8-20f53f3e818d
bond_downdelay : 0
bond_fake_iface : false
bond_updelay : 0
external_ids : {}
fake_bridge : false
interfaces : [455940d8-ba07-402b-9b1a-6522dd696b51]
mac : []
name : "vif1"
other_config : {}
tag : []
trunks : []
_uuid : 5f8f44a7-67b2-49c8-b2f3-cdd933b0a685
bond_downdelay : 0
bond_fake_iface : false
bond_updelay : 0
external_ids : {}
fake_bridge : false
interfaces : [389ad6af-ec0a-4074-a4cc-60d81d603393]
mac : []
name : "vif2"
other_config : {}
tag : []
trunks : []
_uuid : 38d09317-5ee9-48d0-98b5-65d421ffc94b
bond_downdelay : 0
bond_fake_iface : false
bond_updelay : 0
external_ids : {}
fake_bridge : false
interfaces : [d102af51-45b8-4d8f-8184-60dd922533a6]
mac : []
name : "vif3"
other_config : {}
tag : []
trunks : []
_uuid : b78af88f-2cda-47d3-996e-513593ed4e47
bond_downdelay : 0
bond_fake_iface : false
bond_updelay : 0
external_ids : {}
fake_bridge : false
interfaces : [b242eadd-58ed-4975-870a-d06649e167d1]
mac : []
name : "br0"
other_config : {}
tag : []
trunks : []
deb64:~# ovs-vsctl list Bridge
_uuid : fcfcfd0b-d588-4878-b795-5fc3c6bcfb45
controller : []
datapath_id : "005056ba0011"
datapath_type : ""
external_ids : {}
flood_vlans : []
mirrors : []
name : "br0"
netflow : []
other_config : {}
ports : [38d09317-5ee9-48d0-98b5-65d421ffc94b,
5f8f44a7-67b2-49c8-b2f3-cdd933b0a685,
7644a7e1-df29-48e0-8d25-fd29eac9def1,
7e4a0626-dfd8-4bbc-9ad3-a21f3513cd84,
b78af88f-2cda-47d3-996e-513593ed4e47, bedca966-6e73-4e8b-b9b8-20f53f3e818d]
sflow : []
Dnia 20-08-2010 o 16:33:26 ahmed amamou <ahmed.ama...@hotmail.com>
napisał(a):
i think the solution is to do ans ifconfig down eth0 (eth0 not eth1)
route add default br0
then if you connect a cable to the br0 (eth1)
you will normalli be able to ping all vif
To: discuss@openvswitch.org
Date: Fri, 20 Aug 2010 13:14:28 +0200
From: ad...@hrd.pl
Subject: Re: [ovs-discuss] OpenvSwitch - create virtual port on switch
- virtual interface on Debian - help
You are think I should add route for eth1 or br0 ??
I don't know.
May I should delete eth1 from br0, and add eth1 as uplink for switch
br0.
But how do this?
Dnia 20-08-2010 o 13:05:11 ahmed amamou <ahmed.ama...@hotmail.com>
napisał(a):
>
>
>> deb64:~# route
>> Kernel IP routing table
>> Destination Gateway Genmask Flags Metric Ref
Use
>> Iface
>> 193.XX.212.0 * 255.255.252.0 U 0
0 0
>> eth0
>> 193.XX.212.0 * 255.255.252.0 U 0
0 0
>> vi0
>> 193.XX.212.0 * 255.255.252.0 U 0
0 0
>> vif1
>> 193.XX.212.0 * 255.255.252.0 U 0
0 0
>> vif2
>> 193.XX.212.0 * 255.255.252.0 U 0
0 0
>> vif3
>> default 193.XX.215.254 0.0.0.0 UG 0
0 0
>> eth0
>
>
> I think the problem come from the routes definition
>
> as eth0 is still up and it's the first entry to route to net
193.XX.212.0
>
> machine that contain this routing table will always send packet to
> 193.XX.212.0 from eth0
>
> and it's also the default route so all packet that aren't in
> 193.XX.212.0 network will be sent from eth0
> if you put eth0 down it will normally work because you will remove the
> first entry in routing table (that routing from eth0)
> but if you ping a host that isn't in the 193.XX.212.0 network you 'll
> have to add a default route
>
>
>
>
> hope that will help you
--
Tomasz Waśniewski
Admin HRD.pl
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
--
Tomasz Waśniewski
Admin HRD.pl
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
