Ticket #759 (new)

Opened 8 years ago

Last modified 3 years ago

Setup node DHCP to advertise .wlan search domain

Reported by: mitar Owned by: kostko
Priority: major Milestone: Next milestone
Component: nodewatcher/modules Version:
Keywords: Cc:
Related nodes: Realization state:
Blocking: Effort: normal
Blocked by: Security sensitive: no

Description (last modified by kostko) (diff)

Setup node DHCP to advertise wlan search domain.

(Also see #455.)

Change History

comment:1 Changed 5 years ago by kostko

  • Component changed from firmware to nodewatcher/modules

Should this be defaulted to wlan by OpenWrt platform module (can then be simply overriden by other nodewatcher modules), configured by some other module (under administration?) and left unconfigured by default, configured per-node via the configuration schema or something else?

comment:2 Changed 5 years ago by kostko

  • Description modified (diff)
  • Summary changed from Nastaviti DHCP na točkah, da pošilje wlan domeno to Setup node DHCP to advertise .wlan search domain

comment:3 follow-up: ↓ 4 Changed 5 years ago by mitar

Interesting, in fact we do not have DHCP configuration at all in our configuration registry schema. But I think this is network wide setting, the same as which DNS servers are pushed to the client. So where we configure which DNS servers are pushed to the client or which are in the network?

In general we will probably have a module which will connect nodewatcher with DNS server, no? So this should probably be part of that. If you push nodewatcher node names into DNS server, part of configuration is also what is top-level domain used and then this is used by nodes.

comment:4 in reply to: ↑ 3 Changed 5 years ago by kostko

Replying to mitar:

Interesting, in fact we do not have DHCP configuration at all in our configuration registry schema.

Not yet. We will have to add at least marking what networks to advertise on specific interfaces.

But I think this is network wide setting, the same as which DNS servers are pushed to the client. So where we configure which DNS servers are pushed to the client or which are in the network?

DNS server configuration is currently per-node, as well as for example VPN servers. The idea is that we will configure defaults via rules and when we need to update the values, there should be an option in the admin to modify node configuration in batch.

I am not sure if this is the best way, but it offers the most flexibility as you can have nodes that test specific DNS/VPN servers without messing up others' configuration.

In general we will probably have a module which will connect nodewatcher with DNS server, no? So this should probably be part of that. If you push nodewatcher node names into DNS server, part of configuration is also what is top-level domain used and then this is used by nodes.

I agree, this should be handled by that module and by default we advertise no search domains via DHCP.

comment:5 Changed 5 years ago by mitar

What about the situation with centralized DHCP? For example once we migrate to Batman? Then this would become configuration only on gateway server and nodes would not have DHCP servers at all.

comment:6 Changed 5 years ago by kostko

Why exactly would this be a problem? The module that implements the "DNS server connection" can simply check that if the DHCP server is not configured on nodes it doesn't configure the DHCP search domain.

comment:7 Changed 3 years ago by mitar

  • Milestone changed from 3.0b to Next milestone
Note: See TracTickets for help on using tickets.