Okay, will do, thanks.
On Sat, Jan 31, 2015 at 9:04 AM, Gurucharan Shetty
wrote:
> >
> > So "ovs-docker del-port..." bug? I can look at it and fix it... thought
> I'll
> > pass this by you...
> del-port has always worked for me. With the information that you have
> provided, it is not really pos
>
> So "ovs-docker del-port..." bug? I can look at it and fix it... thought I'll
> pass this by you...
del-port has always worked for me. With the information that you have
provided, it is not really possible for me to understand what is going
on. If you have a good reproduction case, I would appre
May be another issue with ovs-docker?:
Things work fine with --net=none. But I ran into this issue:
1. I create a container with --net=none.
2. I connect the vswitch to container: ovs-docker add-port
root@ashok-vb:~# ovs-docker add-port br-int eth0 25021347059d 2.2.2.2
root@25021347059d:/# ifco
Yes, I just read this issue with routing entry on google... :) for example
with dhcp lease renewal...
Thanks for your time... appreciate it.
On Fri, Jan 30, 2015 at 8:28 PM, Gurucharan Shetty
wrote:
> On Fri, Jan 30, 2015 at 8:26 PM, Ashok Chippa
> wrote:
> > Disclaimer: I am not a linux netw
Ah yes, thank you, I remember now. I had this working before (after of
course reading the relevant documentation) and now I remember starting the
container with --net=none. I am revisiting this after a few weeks and had
forgotten about this, and started the containers without --net=none.
Thanks a
On Fri, Jan 30, 2015 at 8:26 PM, Ashok Chippa wrote:
> Disclaimer: I am not a linux network expert... that's why I am struggling
> with this a bit...
>
> root@ashok-vb:/usr/local/bin# ovs-docker add-port br-int eth0 46524ba3123a
> 1.1.1.1
> RTNETLINK answers: File exists
> RTNETLINK answers: File
Disclaimer: I am not a linux network expert... that's why I am struggling
with this a bit...
root@ashok-vb:/usr/local/bin# ovs-docker add-port br-int eth0 46524ba3123a
1.1.1.1
RTNETLINK answers: File exists
RTNETLINK answers: File exists
I can just remove the file if I knew which file it is compl
On Fri, Jan 30, 2015 at 8:12 PM, Ashok Chippa wrote:
> Thanks, I figured the stray i/f issue. I looked at your script as well...
> quite straightforward...
>
> Any idea why this is happening:
>
> root@ashok-vb:/usr/local/bin# ovs-docker add-port br-int eth0 46524ba3123a
> 1.1.1.1
> RTNETLINK answe
Thanks, I figured the stray i/f issue. I looked at your script as well...
quite straightforward...
Any idea why this is happening:
root@ashok-vb:/usr/local/bin# ovs-docker add-port br-int eth0 46524ba3123a
1.1.1.1
RTNETLINK answers: File exists
RTNETLINK answers: File exists
I googled and tried
Hoping someone can answer this...
root@ashok-vb:~# ovs-docker add-port br-int eth0 051d80c13ef6 1.1.1.1
RTNETLINK answers: File exists
RTNETLINK answers: File exists
root@ashok-vb:~# ovs-docker del-port br-int eth0 051d80c13ef6
root@ashok-vb:~# ovs-docker add-port br-int eth0 051d80c13ef6 1.1.1.1
> On Jan 30, 2015, at 5:26 PM, Ashok Chippa wrote:
>
> ovs-docker seems to be a bit buggy... after creating/deleting/creating
> containers, I got into a situation where a stray port on the openvswitch
> remains...
Before you delete the containers, do you delete the ports using del-port
comma
I figured out the answer for my first question: ovs-docker del-port... The
second question is still pending...
On Fri, Jan 30, 2015 at 5:01 PM, Ashok Chippa wrote:
> Hi Gurucharan,
>
> Any idea how to work around this issue:
>
> root@ashok-vb:/usr/local/bin# ovs-docker add-port br-int eth0
> 465
ovs-docker seems to be a bit buggy... after creating/deleting/creating
containers, I got into a situation where a stray port on the openvswitch
remains...
root@ashok-vb:~# ifconfig
c7ef9934c0e44_l Link c7ef9934c0e44encap:Ethernet HWaddr ca:40:32:35:a6:8c
UP BROADCAST MULTICAST MTU:150
Hi Gurucharan,
Any idea how to work around this issue:
root@ashok-vb:/usr/local/bin# ovs-docker add-port br-int eth0 46524ba3123a
1.1.1.1
RTNETLINK answers: File exists
RTNETLINK answers: File exists
I reinstalled the openvswitch and recreated the containers and tried
ovs-docker again and ran in
14 matches
Mail list logo