[ovs-discuss] can't add peth0 to bridge eth0: Invalid argument

pspreadborough at comcast.net pspreadborough at comcast.net
Thu Dec 10 15:35:17 UTC 2009


Yes thank you Jeongkeun that worked well. I also moved to CentOS5 
where openvswitch built without problems and I now have packets 
flowing. 

Regards, 

Pete 

----- Original Message ----- 
From: "Jesse Gross" <jesse at nicira.com> 
To: "Jeongkeun Lee" <jklee at hp.com> 
Cc: pspreadborough at comcast.net, discuss at openvswitch.org 
Sent: Wednesday, December 9, 2009 11:16:31 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [ovs-discuss] can't add peth0 to bridge eth0: Invalid argument 

That should fix the problem. Thanks for passing this on, JK. 

On Dec 9, 2009, at 1:43 PM, "Lee, Jeongkeun" <jklee at hp.com> wrote: 

> In my case, I modified Xen scripts to work around the re-naming issue. 
> 
> In /etc/xen/scripts/network-bridge 
> 
> op_start () { 
> ... 
> ip link set ${tdev} name ${bridge} 
> # ovs-brcompatd does not proxy 'ip link set name' command 
> # need to manually change the bridge name in the ovs config file 
> # should do it better instead of just replacing all the instances 
> of ${tdev} 
> sed -i "s/${tdev}/${bridge}/g" /etc/ovs-vswitchd-xen.conf 
> ... 
> 
> In /etc/xen/scripts/vif-common.sh 
> 
> do_or_die ip link set "$vif" name "$vifname" 
> # needed for OVS 
> sed -i "s/$vif/$vifname/g" /etc/ovs-vswitchd-xen.conf 
> 
> Hope this helps. 
> 
> -- JK 
> 
>> -----Original Message----- 
>> From: discuss-bounces at openvswitch.org [mailto:discuss- 
>> bounces at openvswitch.org] 
>> On Behalf Of pspreadborough at comcast.net 
>> Sent: Tuesday, December 08, 2009 6:55 AM 
>> To: Jesse Gross 
>> Cc: discuss at openvswitch.org 
>> Subject: Re: [ovs-discuss] can't add peth0 to bridge eth0: Invalid 
>> argument 
>> 
>> 
>> 
>> That certainly helped, using the following config enables 
>> me to boot but not pass traffic: 
>> 
>> bridge.eth0.port=eth0 
>> bridge.eth0.port=peth0 
>> bridge.eth0.port=vif1.0 
>> 
>> 
>> xen at xenhost:~$ ifconfig 
>> eth0 Link encap:Ethernet HWaddr 00:15:17:1d:6d:fc 
>> inet6 addr: fe80::215:17ff:fe1d:6dfc/64 Scope:Link 
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 
>> RX packets:4 errors:0 dropped:0 overruns:0 frame:0 
>> TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 
>> collisions:0 txqueuelen:0 
>> RX bytes:3219 (3.1 KiB) TX bytes:9179 (8.9 KiB) 
>> 
>> eth1 Link encap:Ethernet HWaddr 00:15:17:1d:6d:fd 
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 
>> RX packets:107 errors:0 dropped:0 overruns:0 frame:0 
>> TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 
>> collisions:0 txqueuelen:100 
>> RX bytes:20399 (19.9 KiB) TX bytes:90 (90.0 B) 
>> 
>> lo Link encap:Local Loopback 
>> inet addr:127.0.0.1 Mask:255.0.0.0 
>> inet6 addr: ::1/128 Scope:Host 
>> UP LOOPBACK RUNNING MTU:16436 Metric:1 
>> RX packets:12 errors:0 dropped:0 overruns:0 frame:0 
>> TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 
>> collisions:0 txqueuelen:0 
>> RX bytes:876 (876.0 B) TX bytes:876 (876.0 B) 
>> 
>> peth0 Link encap:Ethernet HWaddr 00:15:17:1d:6d:fc 
>> inet addr:192.168.3.110 Bcast:192.168.3.255 Mask: 
>> 255.255.255.0 
>> inet6 addr: fe80::215:17ff:fe1d:6dfc/64 Scope:Link 
>> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 
>> RX packets:266 errors:0 dropped:0 overruns:0 frame:0 
>> TX packets:118 errors:0 dropped:0 overruns:0 carrier:0 
>> collisions:0 txqueuelen:100 
>> RX bytes:83545 (81.5 KiB) TX bytes:21698 (21.1 KiB) 
>> Memory:88180000-881a0000 
>> 
>> vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff 
>> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link 
>> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
>> TX packets:14 errors:0 dropped:15 overruns:0 carrier:0 
>> collisions:0 txqueuelen:32 
>> RX bytes:0 (0.0 B) TX bytes:1864 (1.8 KiB) 
>> 
>> 
>> A tail of the syslog file shows: 
>> 
>> xen at xenhost:~$ tail -f /var/log/syslog 
>> Dec 8 09:45:52 xenhost ovs-vswitchd: 00360|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:1c:c0:1e:44:ea- 
>>> 00:12:17:ab:b4:02 type0800 proto6 ip192.168.3.103->76.96.58.220 
>>> port52290->80 
>> Dec 8 09:45:55 xenhost ovs-vswitchd: 00361|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0000:vlan65535 
>> mac00:15:17:1d:6d:fc- 
>>> ff:ff:ff:ff:ff:ff type0800 proto17 ip0.0.0.0->255.255.255.255 
>>> port68->67 
>> Dec 8 09:46:04 xenhost ovs-vswitchd: 00362|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:1c:c0:02:f2:ec- 
>>> ff:ff:ff:ff:ff:ff type0800 proto17 ip192.168.3.107->192.168.3.255 
>>> port631- 
>>> 631 
>> Dec 8 09:46:05 xenhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 
>> port 
>> 67 interval 10 
>> Dec 8 09:46:07 xenhost ovs-vswitchd: 00363|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:1c:c0:1e:44:ea- 
>>> 00:12:17:ab:b4:02 type0800 proto6 ip192.168.3.103->207.138.82.31 
>>> port48506- 
>>> 80 
>> Dec 8 09:46:07 xenhost ovs-vswitchd: 00364|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:1c:c0:1e:44:ea- 
>>> 00:12:17:ab:b4:02 type0800 proto6 ip192.168.3.103->207.138.82.31 
>>> port48504- 
>>> 80 
>> Dec 8 09:46:07 xenhost ovs-vswitchd: 00365|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:1c:c0:1e:44:ea- 
>>> 00:12:17:ab:b4:02 type0800 proto6 ip192.168.3.103->207.138.82.31 
>>> port48505- 
>>> 80 
>> Dec 8 09:46:07 xenhost ovs-vswitchd: 00366|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:1c:c0:1e:44:ea- 
>>> 00:12:17:ab:b4:02 type0800 proto6 ip192.168.3.103->207.138.82.31 
>>> port48507- 
>>> 80 
>> Dec 8 09:46:07 xenhost ovs-vswitchd: 00367|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:1c:c0:1e:44:ea- 
>>> 00:12:17:ab:b4:02 type0800 proto6 ip192.168.3.103->207.138.82.31 
>>> port48509- 
>>> 80 
>> Dec 8 09:46:10 xenhost ovs-vswitchd: 00368|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0000:vlan65535 
>> mac00:15:17:1d:6d:fc- 
>>> ff:ff:ff:ff:ff:ff type0800 proto17 ip0.0.0.0->255.255.255.255 
>>> port68->67 
>> Dec 8 09:46:15 xenhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 
>> port 
>> 67 interval 5 
>> Dec 8 09:46:15 xenhost ovs-vswitchd: 00369|bridge|WARN|Dropped 27 
>> log 
>> messages in last 60 seconds due to excessive rate 
>> Dec 8 09:46:15 xenhost ovs-vswitchd: 00370|bridge|WARN|bridge 
>> tmpbridge: 
>> received packet on unknown interface 0 
>> Dec 8 09:46:19 xenhost ovs-vswitchd: 00371|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:12:17:ab:b4:02- 
>>> ff:ff:ff:ff:ff:ff type0800 proto17 ip192.168.3.1->255.255.255.255 
>>> port520- 
>>> 520 
>> Dec 8 09:46:20 xenhost dhclient: No DHCPOFFERS received. 
>> Dec 8 09:46:20 xenhost dhclient: No working leases in persistent 
>> database - 
>> sleeping. 
>> Dec 8 09:46:20 xenhost ovs-vswitchd: 00372|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0000:vlan65535 
>> mac00:15:17:1d:6d:fc- 
>>> ff:ff:ff:ff:ff:ff type0800 proto17 ip0.0.0.0->255.255.255.255 
>>> port68->67 
>> Dec 8 09:46:26 xenhost ovs-vswitchd: 00373|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:1c:c0:1e:44:ea- 
>>> 00:12:17:ab:b4:02 type0800 proto6 ip192.168.3.103->96.17.149.10 
>>> port59850->80 
>> Dec 8 09:46:26 xenhost ovs-vswitchd: 00374|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:1c:c0:02:f2:ec- 
>>> 00:12:17:ab:b4:02 type0800 proto17 ip192.168.3.107->17.151.16.21 
>>> port123->123 
>> Dec 8 09:46:30 xenhost ovs-vswitchd: 00375|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:12:17:ab:b4:02- 
>>> ff:ff:ff:ff:ff:ff type0800 proto17 ip192.168.3.1->192.168.3.255 
>>> port41729- 
>>> 162 
>> Dec 8 09:46:30 xenhost ovs-vswitchd: 00376|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:12:17:ab:b4:02- 
>>> ff:ff:ff:ff:ff:ff type0800 proto17 ip192.168.3.1->192.168.3.255 
>>> port41730- 
>>> 162 
>> Dec 8 09:46:31 xenhost ovs-vswitchd: 00377|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:12:17:ab:b4:02- 
>>> ff:ff:ff:ff:ff:ff type0800 proto17 ip192.168.3.1->192.168.3.255 
>>> port41731- 
>>> 162 
>> Dec 8 09:46:32 xenhost ovs-vswitchd: 00378|dpif|WARN|dp0: failed 
>> to delete 
>> flow (No such file or directory) in_port0002:vlan65535 
>> mac00:12:17:ab:b4:02- 
>>> ff:ff:ff:ff:ff:ff type0800 proto17 ip192.168.3.1->192.168.3.255 
>>> port41732- 
>>> 162 
>> 
>> 
>> 
>> ----- Original Message ----- 
>> From: "Jesse Gross" <jesse at nicira.com> 
>> To: pspreadborough at comcast.net, discuss at openvswitch.org 
>> Sent: Monday, December 7, 2009 10:10:13 PM GMT -05:00 US/Canada 
>> Eastern 
>> Subject: Re: [ovs-discuss] can't add peth0 to bridge eth0: Invalid 
>> argument 
>> 
>> Earlier versions of Xen networking (which apparently the Lenny port 
>> is based 
>> on) used some "interesting" tricks with renaming. In this case eth0 
>> is 
>> renamed to peth0 and a bridge named tmpbridge is created then 
>> renamed to 
>> eth0. 
>> 
>> I'm fairly certain that our bridge compatibility layer does not 
>> deal well 
>> with all of this renaming. However, you should be able to configure 
>> this 
>> manually after the machine has booted. For example add the 
>> following to 
>> your /etc/ovs-vswitchd.conf file and reload vswitchd: 
>> 
>> bridge.eth1.port=eth1 
>> bridge.eth1.port=peth1 
>> 
>> You should then be able to assign an IP to eth1. 
>> 
>> Jesse 
>> 
>> On 12/7/09 6:13 PM, "pspreadborough at comcast.net" 
>> <pspreadborough at comcast.net> wrote: 
>> 
>>> 
>>> I'm getting the error "can't add peth0 to bridge eth0: Invalid 
>>> argument" 
>>> during boot. 
>>> 
>>> Any help would be appreciated. 
>>> 
>>> Regards, 
>>> 
>>> Pete 
>>> 
>>> /usr/local/sbin/ovs-vswitchd --version 
>>> ovs-vswitchd (Open vSwitch) 0.90.6 
>>> Compiled Dec 3 2009 14:24:51 
>>> OpenFlow versions 0x97:0x97 
>>> 
>>> I applied the datapath.c patch to work around Debian Lenny 
>>> module compile errors. 
>>> 
>>> Linux xenhost 2.6.26-2-xen-686 #1 SMP Wed Nov 4 23:23:33 UTC 2009 
>>> i686 
>>> GNU/Linux 
>>> 
>>> xenhost:~# cat /etc/ovs-vswitchd.conf 
>>> bridge.tmpbridge.port=tmpbridge 
>>> 
>>> xenhost:~# ovs-dpctl show 
>>> dp0: 
>>> flows: cur:0, soft-max:1024, hard-max:1048576 
>>> ports: cur:1, max:1024 
>>> groups: max:16 
>>> lookups: frags:0, hit:0, missed:0, lost:0 
>>> queues: max-miss:100, max-action:100 
>>> port 0: eth0 (internal) 
>>> 
>>> 
>>> 
>>> _______________________________________________ 
>>> discuss mailing list 
>>> discuss at openvswitch.org 
>>> http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org 
>> 
>> 
>> 
>> _______________________________________________ 
>> discuss mailing list 
>> discuss at openvswitch.org 
>> http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org 




More information about the discuss mailing list