Re: [OpenWrt-Devel] Use DHCP by default on single port devices
Hi, W dniu 2018-08-28 o 22:29, Michael Heimpold pisze: Hi, "DHCP Client", even with an alternative static IP address, might not work for some home users. to make this work better, some companies are choosing the static fallback IP address in the AutoIP range 169.254.x.x/16. At least Windows will fallback to this range if it does not find a DHCP server on this link; so it should at least possible to browse to the web gui and/or open a SSH connection... without reconfiguring your Windows system. I don't know whether this works out-of-the-box on Mac or usual Linux distros, too. At least on my Debian boxen, using NetworkManager, it does not. I have to select this type of autoconfiguration manually first. Regards, Michael ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel To me, adding of 2 separate mechanisms (mDNS, UPnP) on top of fixed IP address or APIPA sounds like a horrendous feature creep, just to replace one mechanism that works (DHCP). On my machines, I use none of the mechanisms. I don't like the idea of installing Avahi on Linux boxen, or enabling UPnP on Windows ones, just to get to my router/bridge/AP/whatever-runs-OpenWrt for initial configuration. When configuring the Ubiquiti bridges (for example Nanobridge M5) for the first time, while sitting on rooftop with my laptop only, DHCP works quite well - it is not a big effort to just disable it at the end of configuration. When doing testing on the ground, I usually have a router with DHCP server already available, so using it to assign IP to newly configured device might be useful, but it usually is not a big problem to temporarily connect Ethernet to the newly configured device, still having Wi-Fi connectivity. Also, there is another class of devices, beside "bridges". Travel routers, such as TP-Link WR703N. Having only one USB port it is clearly a router, having USB port dedicated for mobile broadband modem. Yet this is the most typical scenario. One might use it as an access point, or as weather station as well. Those configurations suit different types of address assignment method. Do we really need to make the distinction between them? Actually, when writing the above, one idea struck me. When starting, dnsmasq checks if there are no other DHCP servers present on the network, and if they are, it bails out. Maybe it would be possible to use IP assigned by authoritative DHCP server, if one is already present, otherwise startup DHCP as before. Still, this would be quite unusual behaviour, and this might have flaws I have yet to think of -- With kind regards, Lech ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Use DHCP by default on single port devices
Hi, I've added a PR for a small mDNS daemon https://github.com/openwrt/openwrt/pull/1339 The init.d script is hackish and has race condition issues, suggestions to improve it would be highly appreciated. For some reason it doesn't seem to work during boot up :/ Best regards, Daniel On 2018-08-27 16:00, Alberto Bursi wrote: On 8/27/2018 12:37 PM, Daniel Engberg wrote: As per request, Fine as long as we fix mdns in some way? https://github.com/openwrt/openwrt/pull/1062 Not subscribed, so CC Best regards, Daniel Engberg ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel I agree with the proposal as phrased in the mailing list. it's either mdns installed by default + dhcp so people can reach the device by writing "OpenWrt.local" or something in the browser or it has to stay static IP. Just going to DHCP without any other easy mean to reach the device will only be annoying. Devices with a single port and low flash can stay with static IP to save space imho. -Alberto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Use DHCP by default on single port devices
Hi, > "DHCP Client", even with an alternative static IP address, might not > work for some home users. to make this work better, some companies are choosing the static fallback IP address in the AutoIP range 169.254.x.x/16. At least Windows will fallback to this range if it does not find a DHCP server on this link; so it should at least possible to browse to the web gui and/or open a SSH connection... without reconfiguring your Windows system. I don't know whether this works out-of-the-box on Mac or usual Linux distros, too. Regards, Michael ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Use DHCP by default on single port devices
What if I use a router that has a single port, and on the USB, there is a 4G modem? This is still a router, and DHCP makes no sense. I don't think it is a good idea to require a user to have a DHCP server. Regards, Levente On Tue, Aug 28, 2018 at 6:11 AM Luiz Angelo Daros de Luca wrote: > > Hi Daniel, > > I do often that kind of switch: dhcpd off, static -> dhcpc. Even > though I'm not sure about this change. > > I read superficially the PR. I looks like a simple change from static > to dhcp on some devices. Correct me if I'm wrong. > > I guess it will break some use cases. Imagine that this change is > applied to an AP device (one ethernet, one wireless). > wireless is disable by default, ethernet now requires a DHCP server. > The user will connect that AP to a single port router (that has DHCP). > How could the use configure it? If the user plugs into the router, it > gets an IP address but wireless is still off. If the user plugs into a > computer > ethernet port, it expects a DHCP server. The user will need to install > a DHCP server on the PC. We are coming from "plug the device into > a computer port, get an IP address from device DHCP, configure the > device" to "configure PC to use static address, configure a DHCP > server, plug > the device and configure it". Remember that some home users have > limited network knowledge and no CLI experience. > > Will it affect failsafe too? > > Most enterprise devices do use DHCP client as default. However, they > still have a static IP address as a fallback. > If that alternative is not available, I'm fully against this change. > Static IP address might give some extra job but it is always there. > Even with a fallback IP address mechanism, DHCP server does help > configure the device the first time without touching PC settings. > > "DHCP server + static IP address" still works with enterprise but > "DHCP Client", even with an alternative static IP address, might not > work for some home users. > > For enterprise users, maybe it's time to customize their own firmware. > Some simple uci-defaults script can do that job nicely. > > Regards, > > --- > Luiz Angelo Daros de Luca > luizl...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Use DHCP by default on single port devices
Hi Daniel, I do often that kind of switch: dhcpd off, static -> dhcpc. Even though I'm not sure about this change. I read superficially the PR. I looks like a simple change from static to dhcp on some devices. Correct me if I'm wrong. I guess it will break some use cases. Imagine that this change is applied to an AP device (one ethernet, one wireless). wireless is disable by default, ethernet now requires a DHCP server. The user will connect that AP to a single port router (that has DHCP). How could the use configure it? If the user plugs into the router, it gets an IP address but wireless is still off. If the user plugs into a computer ethernet port, it expects a DHCP server. The user will need to install a DHCP server on the PC. We are coming from "plug the device into a computer port, get an IP address from device DHCP, configure the device" to "configure PC to use static address, configure a DHCP server, plug the device and configure it". Remember that some home users have limited network knowledge and no CLI experience. Will it affect failsafe too? Most enterprise devices do use DHCP client as default. However, they still have a static IP address as a fallback. If that alternative is not available, I'm fully against this change. Static IP address might give some extra job but it is always there. Even with a fallback IP address mechanism, DHCP server does help configure the device the first time without touching PC settings. "DHCP server + static IP address" still works with enterprise but "DHCP Client", even with an alternative static IP address, might not work for some home users. For enterprise users, maybe it's time to customize their own firmware. Some simple uci-defaults script can do that job nicely. Regards, --- Luiz Angelo Daros de Luca luizl...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Use DHCP by default on single port devices
Hi Levente Please have a look at the Github pull request. It doesn't affect "routers" (depending how you have want to look at it I guess) just devices with a single ethernet port and tries to make all consistent and convenient. Best regards, Daniel On 2018-08-27 16:54, Levente wrote: Can someone explain what is this all about? Why the default IP address is a problem? As far as I understand the router would use DHCP to get an IP address. Then a DHCP server is mandatory on the network? Thanks, Levente On Mon, Aug 27, 2018 at 4:01 PM Alberto Bursi wrote: On 8/27/2018 12:37 PM, Daniel Engberg wrote: > As per request, > > Fine as long as we fix mdns in some way? > > https://github.com/openwrt/openwrt/pull/1062 > > Not subscribed, so CC > > Best regards, > Daniel Engberg > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel I agree with the proposal as phrased in the mailing list. it's either mdns installed by default + dhcp so people can reach the device by writing "OpenWrt.local" or something in the browser or it has to stay static IP. Just going to DHCP without any other easy mean to reach the device will only be annoying. Devices with a single port and low flash can stay with static IP to save space imho. -Alberto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Use DHCP by default on single port devices
Can someone explain what is this all about? Why the default IP address is a problem? As far as I understand the router would use DHCP to get an IP address. Then a DHCP server is mandatory on the network? Thanks, Levente On Mon, Aug 27, 2018 at 4:01 PM Alberto Bursi wrote: > > > On 8/27/2018 12:37 PM, Daniel Engberg wrote: > > As per request, > > > > Fine as long as we fix mdns in some way? > > > > https://github.com/openwrt/openwrt/pull/1062 > > > > Not subscribed, so CC > > > > Best regards, > > Daniel Engberg > > > > ___ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > I agree with the proposal as phrased in the mailing list. > > it's either mdns installed by default + dhcp so people can reach the > device by > > writing "OpenWrt.local" or something in the browser or it has to stay > static IP. > > Just going to DHCP without any other easy mean to reach the device will > only be annoying. > > Devices with a single port and low flash can stay with static IP to save > space imho. > > -Alberto > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Use DHCP by default on single port devices
On 8/27/2018 12:37 PM, Daniel Engberg wrote: As per request, Fine as long as we fix mdns in some way? https://github.com/openwrt/openwrt/pull/1062 Not subscribed, so CC Best regards, Daniel Engberg ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel I agree with the proposal as phrased in the mailing list. it's either mdns installed by default + dhcp so people can reach the device by writing "OpenWrt.local" or something in the browser or it has to stay static IP. Just going to DHCP without any other easy mean to reach the device will only be annoying. Devices with a single port and low flash can stay with static IP to save space imho. -Alberto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Use DHCP by default on single port devices
As per request, Fine as long as we fix mdns in some way? https://github.com/openwrt/openwrt/pull/1062 Not subscribed, so CC Best regards, Daniel Engberg ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
