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

iprange overlap error message could be clearer #1034

Closed
rade opened this issue Jun 28, 2015 · 2 comments
Closed

iprange overlap error message could be clearer #1034

rade opened this issue Jun 28, 2015 · 2 comments
Assignees
Milestone

Comments

@rade
Copy link
Member

rade commented Jun 28, 2015

network 10.128.0.0/10 would overlap with route 10.128.0.0/16
Default -iprange 10.128.0.0/10 overlaps with existing route.
Please pick another range and set it on all hosts.

A user reports...

Specifying -iprange and the dynamic aspects of weave was something I'd never touched yet. Based on the error message, I had no idea where the 10.128.x route came from - so it seemed like this was some internal weave thing. As my boxes are all set up by ansible scripts I had no reason to believe this box had anything special on it. Perhaps this error message could suggest to check out existing routes on the system, or link to a URL that could offer more advice.

@bboreham
Copy link
Contributor

Recommending somewhere to look for more advice seems like a good idea. However, embedding specific URLs inside executables is likely to rot over time.

Maybe something along the lines of "look in the docs, in section [iprange]" ?

@rade
Copy link
Member Author

rade commented Jun 29, 2015

The only change I would make is "existing route" -> "existing route on the host".

One would hope that googling for weave iprange would produce some useful links. Though it looks like the docs link is only third.

@rade rade self-assigned this Jul 2, 2015
@rade rade closed this as completed in 18a4c14 Jul 2, 2015
@rade rade modified the milestone: 1.1.0 Jul 2, 2015
rade added a commit that referenced this issue Jul 7, 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