Also, just make sure you did not terminate ovs by 'kill' it, since that way, the opened tap interfaces are not removed and could cause errors when you restart ovs.
Thanks, Alex Wang, On Tue, Feb 24, 2015 at 3:35 PM, Atanu Ghosh <at...@acm.org> wrote: > Hi, > > If SIOCSIFNAME is used to change the name of the tap interface it seems to > work on FreeBSD 10.1: > ovs-netdev: flags=ffdc8802<BROADCAST,SIMPLEX,MULTICAST,MONITOR,STATICARP> > metric 0 mtu 1500 > options=80000<LINKSTATE> > ether 00:bd:43:48:02:00 > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > media: Ethernet autoselect > status: no carrier > br0: flags=ffdc8802<BROADCAST,SIMPLEX,MULTICAST,MONITOR,STATICARP> metric > 0 mtu 1500 > options=80000<LINKSTATE> > ether 00:30:18:c0:44:c4 > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > media: Ethernet autoselect > status: no carrier > > After you mentioned that the problem may be with the tap interface I > remembered that at some point I had created a tap0, in am attempt to get > OVS working. I think the existence of this tap interface may have been > causing the problems that I have been seeing. I still see some warnings and > errors but it looks like the bridge may be working. > > Atanu. > > On Tue, Feb 24, 2015 at 11:49 AM, Alex Wang <al...@nicira.com> wrote: > >> According to >> https://www.freebsd.org/cgi/man.cgi?query=tap&apropos=0&sektion=4&manpath=FreeBSD+9.3-RELEASE&arch=default&format=html >> >> it seems that freebsd does not support setting SIOCSIFNAME for tap >> interfaces. >> >> I think I'll just remove the code in ovs. >> >> Thanks, >> Alex Wang, >> >> On Tue, Feb 24, 2015 at 9:34 AM, Alex Wang <al...@nicira.com> wrote: >> >>> Okay, could you show me the ovs-vswitchd.log? >>> >>> Usually, there should be some messages explaining the error. >>> >>> Thanks, >>> Alex Wang, >>> >>> On Tue, Feb 24, 2015 at 9:33 AM, Atanu Ghosh <at...@acm.org> wrote: >>> >>>> Hi, >>>> >>>> It seems to be loaded: >>>> >>>> k3$ kldstat | grep if_tap >>>> 13 1 0xffffffff81b93000 5584 if_tap.ko >>>> >>>> Atanu. >>>> >>>> On Tue, Feb 24, 2015 at 9:29 AM, Alex Wang <al...@nicira.com> wrote: >>>> >>>>> Hey, >>>>> >>>>> I think you need to load the 'if_tap.ko'~ >>>>> >>>>> Thanks, >>>>> Alex Wang, >>>>> >>>>> On Mon, Feb 23, 2015 at 3:29 PM, Atanu Ghosh <at...@acm.org> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> The code in the master branch now passes all the tests on FreeBSD >>>>>> 10.1. >>>>>> However, I still see the same errors when trying to create a bridge. >>>>>> Setting the datapath type to netdev doesn't seem to help the situation. >>>>>> >>>>>> Atanu. >>>>>> >>>>>> On Fri, Feb 20, 2015 at 2:32 PM, Alex Wang <al...@nicira.com> wrote: >>>>>> >>>>>>> Hey Atanu, >>>>>>> >>>>>>> We pushed the fixes to master and branch-2.3. I tested on my >>>>>>> FreeBSD-9.3 >>>>>>> VM. Everything should work fine now, >>>>>>> >>>>>>> Thanks, >>>>>>> Alex Wang, >>>>>>> >>>>>>> On Fri, Feb 20, 2015 at 9:54 AM, Alex Wang <al...@nicira.com> wrote: >>>>>>> >>>>>>>> Sorry for this delayed reply, >>>>>>>> >>>>>>>> We found the issue, and working on a fix. Will send more updates >>>>>>>> soon, >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Alex Wang, >>>>>>>> >>>>>>>> On Tue, Feb 17, 2015 at 4:59 PM, Atanu Ghosh <at...@acm.org> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I have been trying to use OVS on FreeBSD 10.1. I have hit a number >>>>>>>>> of issues. >>>>>>>>> >>>>>>>>> 1) This simple command fails: >>>>>>>>> k3$ sudo ovs-vsctl add-br br0 >>>>>>>>> ovs-vsctl: Error detected while setting up 'br0'. See >>>>>>>>> ovs-vswitchd log for details. >>>>>>>>> k3$ sudo ovs-vswitchd >>>>>>>>> 2015-02-18T00:29:29Z|00001|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock: >>>>>>>>> connecting... >>>>>>>>> 2015-02-18T00:29:29Z|00002|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock: >>>>>>>>> connected >>>>>>>>> 2015-02-18T00:29:29Z|00003|bridge|INFO|ovs-vswitchd (Open vSwitch) >>>>>>>>> 2.3.1 >>>>>>>>> 2015-02-18T00:29:34Z|00004|ofproto|WARN|unknown datapath type >>>>>>>>> system >>>>>>>>> 2015-02-18T00:29:34Z|00005|ofproto|WARN|unknown datapath type >>>>>>>>> system >>>>>>>>> 2015-02-18T00:29:34Z|00006|ofproto|WARN|could not create datapath >>>>>>>>> br0 of unknown type system >>>>>>>>> 2015-02-18T00:29:34Z|00007|bridge|ERR|failed to create bridge br0: >>>>>>>>> Address family not supported by protocol family >>>>>>>>> >>>>>>>>> 2) I ran "make check" and hit a number of problems with >>>>>>>>> ovsdb-server interactions, which were due to set_dscp failing on >>>>>>>>> FreeBSD. I >>>>>>>>> have not looked into how to make it work. >>>>>>>>> >>>>>>>>> diff --git a/socket-util.c b/socket-util.c >>>>>>>>> index aa0c719..c17f0d9 100644 >>>>>>>>> --- a/socket-util.c >>>>>>>>> +++ b/socket-util.c >>>>>>>>> @@ -112,6 +112,8 @@ set_dscp(int fd, uint8_t dscp) >>>>>>>>> int val; >>>>>>>>> bool success; >>>>>>>>> >>>>>>>>> + return 0; >>>>>>>>> + >>>>>>>>> if (dscp > 63) { >>>>>>>>> return EINVAL; >>>>>>>>> } >>>>>>>>> >>>>>>>>> 3) I ran "make check" again and hit the problems on the subject >>>>>>>>> line. I looked at 1381 a little and it doesn't look like it even >>>>>>>>> manages to >>>>>>>>> contact the server. I have attached the log file. >>>>>>>>> >>>>>>>>> My python version: >>>>>>>>> k3$ python -V >>>>>>>>> Python 2.7.9 >>>>>>>>> >>>>>>>>> Atanu. >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> discuss mailing list >>>>>>>>> discuss@openvswitch.org >>>>>>>>> http://openvswitch.org/mailman/listinfo/discuss >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
