nlf / dhyve

docker meets xhyve

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

`dhyve up` breaks my network config

durin42 opened this issue · comments

dhyve up seems to change my default route to go over the bridge interface instead of en(0|1), and then I have to manually restore the default route in order to do anything over the network again. I'd be delighted to offer extra debug information, but I'm not sure what to collect or how.

commented

wow, that's a pretty big bug. you might open an issue on xhyve for this one, since it'll be a problem there. i'll keep this open for tracking though.

Filed as machyve/xhyve#50

On Aug 29, 2015, at 11:39 AM, Nathan LaFreniere notifications@github.com wrote:

wow, that's a pretty big bug. you might open an issue on xhyve for this one, since it'll be a problem there. i'll keep this open for tracking though.


Reply to this email directly or view it on GitHub.

commented

Although I don't have any issue with two default gateways as below, I guess it is not related to xhyve but vmnet.framework which xhyve uses in Yosemite.

$ netstat -r -n
Routing tables

Internet:
Destination        Gateway            Flags        Refs      Use   Netif Expire
default            192.168.1.1        UGSc           90        3     en0
default            link#11            UCSI            0        0 bridge1
127                127.0.0.1          UCS             0        0     lo0
127.0.0.1          127.0.0.1          UH              4     1015     lo0
169.254            link#5             UCS             0        0     en0
192.168.1          link#5             UCS             0        0     en0
192.168.1.1/32     link#5             UCS             1        0     en0
192.168.1.1        c0:3f:e:8b:14:41   UHLWIir        92       24     en0   1158
192.168.1.10/32    link#5             UCS             0        0     en0
192.168.64         link#11            UC              2        0 bridge1
192.168.64.3       16.c1.b5.29.cf.32  UHLWI           0       28 bridge1   1198

Is this a work around for it?

$ sudo route delete default -ifscope bridge100
commented

I've heard that there is something wrong with Pow and xhyve networking.

I don't have multiple defaults left after a 'dhyve up', just the one broken one:

$ netstat -r -n | grep default
default            link#12            UCS            30        0 bridge1

the only fix for me is to

$ sudo route delete default
$ sudo route add default $OLD_DEFAULT_GATEWAY

by hand after every dhyve up.

What's Pow?

commented

Oh, you have just one default after dhyve up. That's different from mine.

What's Pow?

I'm not familiar with Rails, but it seems http://pow.cx/ .

Yes, I have one default and I can't add another until I delete the bogus one on bridge0.

I don't use Pow, but you probably guessed that.