Skip to content
Snippets Groups Projects
  1. Jan 13, 2017
  2. Jan 12, 2017
    • Hans Dedecker's avatar
      map: take over maintainership · d1daf3f3
      Hans Dedecker authored
      
      Signed-off-by: default avatarHans Dedecker <dedeckeh@gmail.com>
      Acked-by: default avatarJo-Philipp Wich <jo@mein.io>
      d1daf3f3
    • Hans Dedecker's avatar
      odhcp6c: take over maintainership · 0d49f9f4
      Hans Dedecker authored
      
      Signed-off-by: default avatarHans Dedecker <dedeckeh@gmail.com>
      Acked-by: default avatarJo-Philipp Wich <jo@mein.io>
      0d49f9f4
    • Hans Dedecker's avatar
      odhcpd: take over maintainership · 5303d4be
      Hans Dedecker authored
      
      Signed-off-by: default avatarHans Dedecker <dedeckeh@gmail.com>
      Acked-by: default avatarJo-Philipp Wich <jo@mein.io>
      5303d4be
    • Hans Dedecker's avatar
      Revert "dnsmasq: change 'add_local_hostname' to use dnsmasq '--interface-name'" · ec63e3bf
      Hans Dedecker authored
      
      This causes problem when a FQDN is configured in /etc/config/system. The
      domain name will appear twice in reverse DNS.
      
      Next to that, there seems to be a bug in dnsmasq. From the manual page:
      
      --interface-name=<name>,<interface>[/4|/6]
      Return  a  DNS  record  associating  the  name  with  the primary address
      on the given interface. This flag specifies an A or AAAA record for the
      given name in the same way as an /etc/hosts line, except that the address
      is not constant, but taken from the given interface. The interface may be
      followed by "/4" or "/6" to specify  that  only  IPv4  or  IPv6 addresses
      of the interface should be used. If the interface is down, not configured
      or non-existent, an empty record is returned. The matching PTR record is
      also created, mapping the interface address to the name. More than one name
      may be associated with an interface address by repeating the flag; in that
      case the first instance is used for  the  reverse address-to-name mapping.
      
      It does not just create an A/AAAA record for the primary address, it creates
      one for all addresses. And what is worse, it seems to actually resolve to the
      non-primary address first. This is quite annoying when you use floating IP
      addresses (e.g. VRRP), because when the floating IP is on the other device,
      SSH failes due to incorrect entry in the known hosts file.
      
      I know that this is not a common setup, but it would be nice if there was an
      option to restore the previous behaviour, rather than just forcing this new
      feature on everybody.
      
      Reported-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
      Signed-off-by: default avatarHans Dedecker <dedeckeh@gmail.com>
      ec63e3bf
    • Hans Dedecker's avatar
      map: delete map-t device when tearing down map interface · bb8e9c51
      Hans Dedecker authored
      
      Delete the map-t device when tearing down the map-t interface; as such
      there's no conflict when the map-t interface comes up again when trying
      to add the map-t device as the map-t device was still present
      (Can not add: device 'map-wan6_4' already exists!).
      
      Only call ifdown in teardown for map-e and lw6o4 map interfaces types
      in order to suppress the trace "wan6_4 (6652): Interface wan6_4_ not found"
      
      Signed-off-by: default avatarHans Dedecker <dedeckeh@gmail.com>
      bb8e9c51
  3. Jan 11, 2017
Loading