root@FF-GE-HeiligerErnstKuzorra:~# logread
Sun Apr 26 17:10:09 2015 user.emerg syslog: setting up led USB1
Sun Apr 26 17:10:09 2015 user.emerg syslog: sh: write error: Invalid argument
Sun Apr 26 17:10:09 2015 user.emerg syslog: /etc/rc.common: eval: line 1: can't create /sys/class/leds/tp-link:green:usb1/device_name: nonexistent directory
Sun Apr 26 17:10:09 2015 user.emerg syslog: /etc/rc.common: eval: line 1: can't create /sys/class/leds/tp-link:green:usb1/activity_interval: nonexistent directory
Sun Apr 26 17:10:09 2015 user.emerg syslog: setting up led USB2
Sun Apr 26 17:10:09 2015 daemon.notice netifd: Network device 'bat0' link is up
Sun Apr 26 17:10:09 2015 daemon.notice netifd: Interface 'bat0' has link connectivity
Sun Apr 26 17:10:09 2015 daemon.notice netifd: Interface 'bat0' is setting up now
Sun Apr 26 17:10:09 2015 daemon.notice netifd: Interface 'bat0' is now up
Sun Apr 26 17:10:09 2015 user.emerg syslog: sh: write error: Invalid argument
Sun Apr 26 17:10:09 2015 user.emerg syslog: /etc/rc.common: eval: line 1: can't create /sys/class/leds/tp-link:green:usb2/device_name: nonexistent directory
Sun Apr 26 17:10:09 2015 user.emerg syslog: /etc/rc.common: eval: line 1: can't create /sys/class/leds/tp-link:green:usb2/activity_interval: nonexistent directory
Sun Apr 26 17:10:09 2015 user.emerg syslog: setting up led WLAN2G
Sun Apr 26 17:10:10 2015 daemon.notice netifd: Interface 'mesh_vpn' is now up
Sun Apr 26 17:10:10 2015 daemon.notice netifd: Interface 'wan' is now up
Sun Apr 26 17:10:10 2015 daemon.notice netifd: Interface 'client' is now up
Sun Apr 26 17:10:11 2015 user.emerg syslog: /etc/rc.d/S99alfred: starting alfred
Sun Apr 26 17:10:11 2015 user.emerg syslog: /etc/rc.d/S99alfred: starting batadv-vis
Sun Apr 26 17:10:11 2015 user.emerg syslog: - init complete -
Sun Apr 26 17:10:11 2015 kern.info kernel: [   27.970000] br-client: port 2(bat0) entered forwarding state
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.230000] batman_adv: bat0: Changing gw mode from: off to: client
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.230000] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.370000] IPv6: ADDRCONF(NETDEV_UP): wlan1-1: link is not ready
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.410000] device wlan1-1 entered promiscuous mode
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.440000] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.470000] device wlan0-1 entered promiscuous mode
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.470000] br-client: port 4(wlan0-1) entered forwarding state
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.480000] br-client: port 4(wlan0-1) entered forwarding state
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.640000] br-client: port 3(wlan1-1) entered forwarding state
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.640000] br-client: port 3(wlan1-1) entered forwarding state
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.650000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.750000] device wlan1-2 entered promiscuous mode
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.780000] br-wan: port 2(wlan1-2) entered forwarding state
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.780000] br-wan: port 2(wlan1-2) entered forwarding state
Sun Apr 26 17:10:12 2015 kern.info kernel: [   28.790000] IPv6: ADDRCONF(NETDEV_UP): wlan1-2: link is not ready
Sun Apr 26 17:10:13 2015 daemon.info dnsmasq[1692]: started, version 2.71 cachesize 150
Sun Apr 26 17:10:13 2015 daemon.info dnsmasq[1692]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC
Sun Apr 26 17:10:13 2015 daemon.info dnsmasq[1692]: using local addresses only for domain lan
Sun Apr 26 17:10:13 2015 daemon.warn dnsmasq[1692]: no servers found in /tmp/resolv.conf.auto, will retry
Sun Apr 26 17:10:13 2015 daemon.info dnsmasq[1692]: read /etc/hosts - 1 addresses
Sun Apr 26 17:10:13 2015 kern.info kernel: [   29.390000] br-client: port 4(wlan0-1) entered disabled state
Sun Apr 26 17:10:13 2015 kern.info kernel: [   29.700000] br-wan: port 2(wlan1-2) entered disabled state
Sun Apr 26 17:10:13 2015 kern.info kernel: [   29.730000] br-client: port 4(wlan0-1) entered forwarding state
Sun Apr 26 17:10:13 2015 kern.info kernel: [   29.740000] br-client: port 4(wlan0-1) entered forwarding state
Sun Apr 26 17:10:13 2015 kern.info kernel: [   29.750000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
Sun Apr 26 17:10:13 2015 kern.info kernel: [   29.760000] device wlan0-2 entered promiscuous mode
Sun Apr 26 17:10:13 2015 kern.info kernel: [   29.770000] br-wan: port 3(wlan0-2) entered forwarding state
Sun Apr 26 17:10:13 2015 kern.info kernel: [   29.770000] br-wan: port 3(wlan0-2) entered forwarding state
Sun Apr 26 17:10:13 2015 kern.info kernel: [   29.780000] IPv6: ADDRCONF(NETDEV_UP): wlan0-2: link is not ready
Sun Apr 26 17:10:14 2015 kern.info kernel: [   30.380000] br-wan: port 2(wlan1-2) entered forwarding state
Sun Apr 26 17:10:14 2015 kern.info kernel: [   30.390000] br-wan: port 2(wlan1-2) entered forwarding state
Sun Apr 26 17:10:14 2015 kern.info kernel: [   30.390000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-2: link becomes ready
Sun Apr 26 17:10:14 2015 kern.info kernel: [   30.430000] br-wan: port 3(wlan0-2) entered disabled state
Sun Apr 26 17:10:14 2015 kern.info kernel: [   30.640000] br-client: port 3(wlan1-1) entered forwarding state
Sun Apr 26 17:10:14 2015 kern.info kernel: [   30.800000] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Sun Apr 26 17:10:14 2015 kern.info kernel: [   30.860000] wlan1: Created IBSS using preconfigured BSSID 02:ff:13:37:ff:02
Sun Apr 26 17:10:14 2015 kern.info kernel: [   30.860000] wlan1: Creating new IBSS network, BSSID 02:ff:13:37:ff:02
Sun Apr 26 17:10:14 2015 kern.info kernel: [   30.870000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Sun Apr 26 17:10:14 2015 kern.info kernel: [   31.150000] br-wan: port 3(wlan0-2) entered forwarding state
Sun Apr 26 17:10:14 2015 kern.info kernel: [   31.160000] br-wan: port 3(wlan0-2) entered forwarding state
Sun Apr 26 17:10:14 2015 kern.info kernel: [   31.160000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-2: link becomes ready
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Network device 'wlan1-1' link is up
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Network device 'wlan1' link is up
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Interface 'mesh_radio1' is enabled
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Interface 'mesh_radio1' has link connectivity
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Interface 'mesh_radio1' is setting up now
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Network device 'wlan1-2' link is up
Sun Apr 26 17:10:15 2015 kern.info kernel: [   31.420000] batman_adv: bat0: Adding interface: wlan1
Sun Apr 26 17:10:15 2015 kern.info kernel: [   31.430000] batman_adv: bat0: Interface activated: wlan1
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Interface 'mesh_radio1' is now up
Sun Apr 26 17:10:15 2015 daemon.notice netifd: wan (1347): Performing a DHCP renew
Sun Apr 26 17:10:15 2015 daemon.notice netifd: wan (1347): Sending renew...
Sun Apr 26 17:10:15 2015 daemon.notice netifd: wan (1347): Lease of 192.168.0.21 obtained, lease time 864000
Sun Apr 26 17:10:15 2015 kern.info kernel: [   31.660000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sun Apr 26 17:10:15 2015 kern.info kernel: [   31.700000] wlan0: Created IBSS using preconfigured BSSID 02:ff:13:37:ff:01
Sun Apr 26 17:10:15 2015 kern.info kernel: [   31.710000] wlan0: Creating new IBSS network, BSSID 02:ff:13:37:ff:01
Sun Apr 26 17:10:15 2015 kern.info kernel: [   31.730000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sun Apr 26 17:10:15 2015 kern.info kernel: [   31.740000] br-client: port 4(wlan0-1) entered forwarding state
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Network device 'wlan0-1' link is up
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Network device 'wlan0' link is up
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Interface 'mesh_radio0' is enabled
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Interface 'mesh_radio0' is setting up now
Sun Apr 26 17:10:15 2015 daemon.notice netifd: Network device 'wlan0-2' link is up
Sun Apr 26 17:10:16 2015 kern.info kernel: [   32.220000] batman_adv: bat0: Adding interface: wlan0
Sun Apr 26 17:10:16 2015 kern.info kernel: [   32.220000] batman_adv: bat0: Interface activated: wlan0
Sun Apr 26 17:10:16 2015 daemon.notice netifd: Interface 'mesh_radio0' is now up
Sun Apr 26 17:10:16 2015 kern.info kernel: [   32.390000] br-wan: port 2(wlan1-2) entered forwarding state
Sun Apr 26 17:10:16 2015 daemon.notice netifd: wan (1347): Performing a DHCP renew
Sun Apr 26 17:10:16 2015 daemon.notice netifd: wan (1347): Sending renew...
Sun Apr 26 17:10:16 2015 daemon.notice netifd: wan (1347): Lease of 192.168.0.21 obtained, lease time 864000
Sun Apr 26 17:10:16 2015 user.notice firewall: Reloading firewall due to ifup of wan6 (br-wan)
Sun Apr 26 17:10:16 2015 authpriv.info dropbear[1926]: Child connection from 192.168.0.2:57703
Sun Apr 26 17:10:16 2015 kern.info kernel: [   33.160000] br-wan: port 3(wlan0-2) entered forwarding state
Sun Apr 26 17:10:20 2015 user.notice firewall: Reloading firewall due to ifup of wan (br-wan)
Sun Apr 26 17:10:22 2015 authpriv.info dropbear[1926]: Exit before auth: Exited normally
Sun Apr 26 17:10:22 2015 authpriv.info dropbear[2118]: Child connection from 192.168.0.2:57706
Sun Apr 26 17:10:22 2015 user.notice firewall: Reloading firewall due to ifup of client (br-client)
Sun Apr 26 17:10:29 2015 daemon.info fastd[1397]: resolving host `ffrg2.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet2>...
Sun Apr 26 17:10:29 2015 daemon.info dnsmasq[1088]: reading /var/gluon/wan-dnsmasq/resolv.conf
Sun Apr 26 17:10:29 2015 daemon.info dnsmasq[1088]: using nameserver 192.168.0.1#53
Sun Apr 26 17:10:29 2015 daemon.info fastd[1397]: resolved host `ffrg2.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolving host `ffrg5.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet5>...
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolved host `ffrg5.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolving host `ffrg11.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet11>...
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolved host `ffrg11.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolving host `ffrg7.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet7>...
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolved host `ffrg7.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolving host `ffrg4.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet4>...
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolved host `ffrg4.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolving host `ffrg8.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet8>...
Sun Apr 26 17:10:30 2015 daemon.info fastd[1397]: resolved host `ffrg8.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolving host `ffrg3.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet3>...
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolved host `ffrg3.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:32 2015 authpriv.notice dropbear[2118]: Password auth succeeded for 'root' from 192.168.0.2:57706
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolving host `ffrg6.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet6>...
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolved host `ffrg6.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolving host `ffrg9.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet9>...
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolved host `ffrg9.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolving host `ffrg1.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet1>...
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolved host `ffrg1.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolving host `ffrg10.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet10>...
Sun Apr 26 17:10:32 2015 daemon.info fastd[1397]: resolved host `ffrg10.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:34 2015 daemon.info fastd[1397]: resolving host `ffrg0.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet0>...
Sun Apr 26 17:10:34 2015 daemon.info fastd[1397]: resolved host `ffrg0.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:49 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet11>[85.14.244.128:10000]...
Sun Apr 26 17:10:49 2015 daemon.info fastd[1397]: resolving host `ffrg11.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet11>...
Sun Apr 26 17:10:49 2015 daemon.info fastd[1397]: resolved host `ffrg11.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:49 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet7>[37.120.172.71:10000]...
Sun Apr 26 17:10:49 2015 daemon.info fastd[1397]: resolving host `ffrg7.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet7>...
Sun Apr 26 17:10:49 2015 daemon.info fastd[1397]: resolved host `ffrg7.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:50 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet5>[37.120.172.62:10000]...
Sun Apr 26 17:10:50 2015 daemon.info fastd[1397]: resolving host `ffrg5.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet5>...
Sun Apr 26 17:10:50 2015 daemon.info fastd[1397]: resolved host `ffrg5.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:50 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet6>[37.120.172.60:10000]...
Sun Apr 26 17:10:50 2015 daemon.info fastd[1397]: resolving host `ffrg6.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet6>...
Sun Apr 26 17:10:50 2015 daemon.info fastd[1397]: resolved host `ffrg6.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:51 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet2>[5.39.121.115:10000]...
Sun Apr 26 17:10:51 2015 daemon.info fastd[1397]: received handshake response from <mesh_vpn_backbone_peer_ruhrgebiet2>[5.39.121.115:10000] using fastd v17
Sun Apr 26 17:10:51 2015 daemon.info fastd[1397]: 5.39.121.115:10000 authorized as <mesh_vpn_backbone_peer_ruhrgebiet2>
Sun Apr 26 17:10:52 2015 daemon.notice fastd[1397]: connection with <mesh_vpn_backbone_peer_ruhrgebiet2> established.
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: new session with <mesh_vpn_backbone_peer_ruhrgebiet2> established using method `salsa2012+umac'.
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet8>[37.120.172.76:10000]...
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: resolving host `ffrg8.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet8>...
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: resolved host `ffrg8.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet9>[37.120.161.36:10000]...
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: resolving host `ffrg9.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet9>...
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: resolved host `ffrg9.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet4>[85.14.244.127:10000]...
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: resolving host `ffrg4.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet4>...
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: resolved host `ffrg4.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet0>[5.39.121.113:10000]...
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: resolving host `ffrg0.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet0>...
Sun Apr 26 17:10:52 2015 daemon.info fastd[1397]: resolved host `ffrg0.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:53 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet3>[37.252.124.177:10000]...
Sun Apr 26 17:10:53 2015 daemon.info fastd[1397]: sending handshake to <mesh_vpn_backbone_peer_ruhrgebiet10>[37.120.173.105:10000]...
Sun Apr 26 17:10:53 2015 daemon.info fastd[1397]: resolving host `ffrg10.freifunk-ruhrgebiet.de' for peer <mesh_vpn_backbone_peer_ruhrgebiet10>...
Sun Apr 26 17:10:53 2015 daemon.info fastd[1397]: resolved host `ffrg10.freifunk-ruhrgebiet.de' successfully
Sun Apr 26 17:10:53 2015 daemon.info fastd[1397]: received handshake response from <mesh_vpn_backbone_peer_ruhrgebiet10>[37.120.173.105:10000] using fastd v16
Sun Apr 26 17:10:54 2015 daemon.info fastd[1397]: 37.120.173.105:10000 authorized as <mesh_vpn_backbone_peer_ruhrgebiet10>
Sun Apr 26 17:10:54 2015 daemon.notice fastd[1397]: connection with <mesh_vpn_backbone_peer_ruhrgebiet10> established.
Sun Apr 26 17:10:54 2015 daemon.info fastd[1397]: new session with <mesh_vpn_backbone_peer_ruhrgebiet10> established using method `salsa2012+umac'.
Sun Apr 26 17:15:18 2015 daemon.info dnsmasq[1692]: reading /tmp/resolv.conf.auto
Sun Apr 26 17:15:18 2015 daemon.info dnsmasq[1692]: using local addresses only for domain lan
Sun Apr 26 17:15:18 2015 daemon.info dnsmasq[1692]: using nameserver 2001:4ba0:ffff:1e9::33#53
Sun Apr 26 17:15:18 2015 daemon.info dnsmasq[1692]: using nameserver 2001:41d0:c:95c::190#53