[ovs-discuss] Issue with Basic OVS + VXLAN + OF Configuration

2016-01-28 Thread Nick Couchman
to try to figure it out? I've tried dumping the flows on the switches, but because they are fairly dynamic and controlled by the Floodlight controller, it's hard to pin them down during the actual problem. I'm seeing some dropped packets on the OVS switch in Linux via the ip com

[ovs-discuss] Vswitch

2014-08-25 Thread nick miller
I have a Nokia Lumia 521 with windows 8 and solavei as my service provider. I just did a reset because things weren't working properly. Now the only thing that doesn't work is my internet sharing option. Says it currently unavailable. I'm guessing its the vswitch. If it is I need help with that

[ovs-discuss] Vswitch

2014-08-25 Thread nick miller
Oops forgot email add. nikenickna...@gmail.com Sent from my Windows Phone___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss

[ovs-discuss] OVS kernel module in vanilla kernel vs kernel module from OVS source tarball

2013-07-05 Thread Nick
I apologize if this documented somewhere since it seems like it should be a FAQ, but for the life of me I can't seem to find the answer searching. What exactly is the difference between using the openvswitch kernel module from a recent vanilla kernel.org kernel, and using the kernel module that co

Re: [ovs-discuss] Bootstrapping OVS (network config before openvswitch db is up)

2013-05-15 Thread Nick
Thanks so much! It looks like this is going to be easier than I at first suspected. On Tue, May 14, 2013 at 2:08 PM, Ben Pfaff wrote: > On Tue, May 14, 2013 at 12:07:46PM -0700, Nick wrote: > > Ok that sounds better. So would it be best to use the same eth0 (or > > whatev

Re: [ovs-discuss] Bootstrapping OVS (network config before openvswitch db is up)

2013-05-14 Thread Nick
PM, Nick wrote: > > 5. Start ovsdb-server on one node (on a floating IP which would be an > alias > > on eth0.mgmt), with a persistent storage data directory. If this server > > dies it will be automatically master elected (using our internal > automation > > framework)

[ovs-discuss] Bootstrapping OVS (network config before openvswitch db is up)

2013-05-13 Thread Nick
I'm working on a large-scale netbooted cluster configuration, which has it's persistent data stored on a clustering filesystem for redundancy. There is only one physical network link, where the untagged vlan is used for management/filesystem replication, and tagged vlans are used for other things.

[ovs-discuss] Another ovs-vsctl Question

2010-09-13 Thread Nick Couchman
ow/NetFlow configuration, Virtual/Internal ports, and port mirroring. Apparently those examples have not yet been ported over to OVSDB commands. I'm happy to help by adding these things to man pages, I just need to figure out how to do them, myself. Thanks! -Nick This e-m

Re: [ovs-discuss] Permanent MAC on Internal Interfaces

2010-09-09 Thread Nick Couchman
>>> On 2010/09/09 at 15:07, Jesse Gross wrote: > On Thu, Sep 9, 2010 at 10:22 AM, Nick Couchman > wrote: >> Another question to throw out there...per my previous post, I have an > internal interface (vi0) for my Linux system that actually picks up the IP > addre

[ovs-discuss] Permanent MAC on Internal Interfaces

2010-09-09 Thread Nick Couchman
knew how to do it in the pre-ovsdb days, but not sure what the command is for ovs-vsctl using ovsdb. Thanks, Nick This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not

Re: [ovs-discuss] OVS Ports not Available at Boot Time

2010-09-09 Thread Nick Couchman
correctly, was related to the modules not loading - everything is working fine, now. Thanks, and sorry for clutter the list with silly questions like this! :-) -Nick >>> On 2010/09/08 at 18:03, Jesse Gross wrote: > On Wed, Sep 8, 2010 at 1:29 PM, Nick Couchman wrote: >>

[ovs-discuss] OVS Ports not Available at Boot Time

2010-09-08 Thread Nick Couchman
pen vSwitch) it does not seem to operate in promiscuous mode. This is problematic for internal interface that I've created, as packets going back to that interface (right now, DHCP responses) don't get put through. Any hints on how to solve this one? Thanks, Nick ---