Oh,thanks to talk me about this, I just think they are in the same page.
> Subject: Re: [ovs-discuss] new nox and discovery
> From: jpet...@nicira.com
> Date: Tue, 8 Jan 2013 10:27:57 -0800
> CC: discuss@openvswitch.org
> To: aaron11...@hotmail.com
>
> Have you looked at the nox-dev mailing
Open vSwitch just configures existing kernel QoS features. If OVS
isn't doing a good job of it, then we should fix that. But short of
that, you need to figure out what the kernel HTB implementation is
actually doing. We're not experts on that here. I suggest asking
about HTB behavior on a maili
On Tue, Jan 8, 2013 at 11:24 AM, Qin, Xiaohong wrote:
> Hi Jesse,
>
> Thanks for the tip. I have loaded it into the kernel by running the insmod
> CLI and now I can launch the "ovs-vswitchd" CLI successfully. Then I did this,
>
> ovs-vsctl show
> 6a792107-75e2-44fb-a3f0-019c29042283
>
> It didn't
On Tue, Jan 8, 2013 at 10:19 AM, Jeff Welsch wrote:
> Sorry, what happens is the source address of the GRE tunnel is set to the IP
> of the 10.0.1.0/24 interface, resulting in the packets being seen on that
> interface using tcpdump. eth0 is configured as 10.0.1.27 and eth1 is
> 192.168.1.2 (d
Hi Jesse,
Thanks for the tip. I have loaded it into the kernel by running the insmod CLI
and now I can launch the "ovs-vswitchd" CLI successfully. Then I did this,
ovs-vsctl show
6a792107-75e2-44fb-a3f0-019c29042283
It didn't print out the version number as previous release,
ovs-vsctl show
a55
On Tue, Jan 8, 2013 at 10:49 AM, Qin, Xiaohong wrote:
> Hi Ben,
>
> I was able to get rid of that schema problem but still I'm running into the
> kernel module issue; here is the error message,
>
> ovs-vswitchd --pidfile --detach
> 2013-01-08T11:27:40Z|1|reconnect|INFO|unix:/usr/local/var/run
Hi Ben,
I was able to get rid of that schema problem but still I'm running into the
kernel module issue; here is the error message,
ovs-vswitchd --pidfile --detach
2013-01-08T11:27:40Z|1|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
connecting...
2013-01-08T11:27:40Z|2|rec
Have you looked at the nox-dev mailing list at noxrepo.org? That's probably a
better forum for questions about NOX.
--Justin
On Jan 8, 2013, at 8:36 AM, 鍾 燿全 wrote:
> Hi,everyone:
>
> I'm a new about NOX.
>
> Now I'm trying to use new NOX to find the LLDP information.
>
> But I have a pro
Jesse, thanks so much. Things are routing, OSPF seems happy and I'm
pushing iperf tests now.
The MTU of 1396 yields a functional size of around 1496 with the odd
fragmented packet here and there. Anyone have thoughts to a more optimal
MTU size?
I had some issues getting the syntax for the op
Sorry, what happens is the source address of the GRE tunnel is set to the IP of
the 10.0.1.0/24 interface, resulting in the packets being seen on that
interface using tcpdump. eth0 is configured as 10.0.1.27 and eth1 is
192.168.1.2 (desired egress interface).
09:48:00.315878 IP 10.0.1.27 > 1
On Tue, Jan 8, 2013 at 9:39 AM, m...@privateit.net wrote:
> gretap fixed my GRE tunneling issue, thank you...
>
> However, ipsec between the two systems is now “broken”. If the ipsec
> tunnel is shutdown and the GRE tunnels are up, we can route without
> problem. If the ipsec tunnel is up, GRE
gretap fixed my GRE tunneling issue, thank you...
However, ipsec between the two systems is now “broken”. If the ipsec
tunnel is shutdown and the GRE tunnels are up, we can route without
problem. If the ipsec tunnel is up, GRE packets from the iproute2 box
(cash) appear to be ipsec encapsulated
On Mon, Jan 7, 2013 at 7:38 PM, Jeff Welsch wrote:
> Hello,
>
> Is there a way to specify the egress interface for a GRE tunnel? I am
> matching flows and sending them to a tunnel using an output action. This
> works fine when my remote IP is on eth0, but I would like to send some
> tunnels o
Hi,everyone:
I'm a new about NOX.
Now I'm trying to use new NOX to find the LLDP information.
But I have a problem to find the code about that, and the code on the Internet
almost from the NOX-classic
Can someone can help me to find the code like discovery.py and link-event.cc in
the NOX-cla
This will show you the patches that went into 1.4:
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=log;h=refs/heads/branch-1.4
You can see the release number in the little yellow tags.
--Justin
On Jan 8, 2013, at 8:05 AM, selen jia wrote:
> Hi ,
>
> i am working on openvswitc
Hi ,
i am working on openvswitch 1.4 and i wanted to know what bugs are fixed on
openvswitch 1.4 version, I can get the patch logs on 1.4 version from
openvswitch github in* tags* section..
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=summary
But when i see 1.4 code i can not find
16 matches
Mail list logo
