Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

expose causes network overlap complaint on restart #1076

Closed
rade opened this issue Jul 5, 2015 · 0 comments
Closed

expose causes network overlap complaint on restart #1076

rade opened this issue Jul 5, 2015 · 0 comments
Assignees
Milestone

Comments

@rade
Copy link
Member

rade commented Jul 5, 2015

$ weave launch
$ weave expose
10.128.0.2
$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.254   0.0.0.0         UG    0      0        0 wlan0
10.128.0.0      0.0.0.0         255.192.0.0     U     0      0        0 weave
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.1.0     0.0.0.0         255.255.255.0   U     9      0        0 wlan0
192.168.48.0    0.0.0.0         255.255.255.0   U     0      0        0 vboxnet0
$ weave stop
$ weave launch
Network 10.128.0.0/10 overlaps with existing route 10.128.0.0/10 on host.
Default -iprange 10.128.0.0/10 overlaps with existing route on host.
Please pick another range and set it on all hosts.

Perhaps we should ignore the weave bridge in our overlap calculations.

@rade rade added this to the 1.0.2 milestone Jul 5, 2015
@bboreham bboreham self-assigned this Jul 6, 2015
@rade rade modified the milestones: current, 1.0.2 Jul 7, 2015
@rade rade closed this as completed in #1090 Jul 7, 2015
rade added a commit that referenced this issue Jul 7, 2015
Don't complain about weave bridge routes clashing

Fixes #1076.
@rade rade modified the milestones: current, 1.1.0 Jul 13, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants