Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Choose different subnet for configuration mode IP #56

Closed
mountaindude opened this issue Apr 6, 2016 · 7 comments
Closed

Choose different subnet for configuration mode IP #56

mountaindude opened this issue Apr 6, 2016 · 7 comments
Milestone

Comments

@mountaindude
Copy link

The 192.168.1.1 net is quite often used by SOHO routers.
Placing a homie device in config mode on that same IP might easily cause conflicts with the user's cable modem/router/Internet gateway.

Maybe something like 192.168.50.1 (or something similarly infrequently used subnet)?

Or provide a way for the developer to define the desired subnet themselves?

@mountaindude
Copy link
Author

I guess one could also change the Homie source.. Looks like the 192.168.1.1 is defined in the src/Homie/Boot/BootConfig.cpp file (I am using Homie together with PlatformIO, btw)

@mountaindude
Copy link
Author

...then again, changing the access point's IP address to 192.168.50.1 breaks the config tool at http://marvinroger.github.io/homie-esp8266, it seems...

@marvinroger
Copy link
Member

The problem is changing the default 192.168.1.1 would be a breaking change. And 192.168.50.1 might also be used by someone else! So yes, maybe we should move the apIp variable to the Constants.hpp, so that it is easily customizable.

It should not break the config tool, it tries to reach http://homie.config, and as you can see, the DNS server is tied to the apIp.

@marvinroger
Copy link
Member

Is it enough for you?

@mountaindude
Copy link
Author

Yeah it sounds like a good plan.

On 15 April 2016 at 09:29, Marvin Roger notifications@github.com wrote:

Is it enough for you?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#56 (comment)

@marvinroger
Copy link
Member

It will land in v1.4.0. :)

@marvinroger marvinroger added this to the v1.4.0 milestone Apr 17, 2016
@marvinroger
Copy link
Member

Released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants