dnsmasq: recompile with HAVE_IPSET defined

GoogleCodeExporter commented 9 years ago

I want use dnsmasq with ipset, can you recompile dnsmasq with HAVE_IPSET 
defined?

Thanks!

Original issue reported on code.google.com by pun...@gmail.com on 10 Feb 2014 at 10:42

GoogleCodeExporter commented 9 years ago

https://code.google.com/p/rt-n56u/wiki/HowToMakeFirmware

Original comment by Dr.Sydorenko.O on 10 Feb 2014 at 10:39

GoogleCodeExporter commented 9 years ago

I rebuild firmware with HAVE_IPSET defined, now i get this error:

dnsmasq[515]:failed to create IPset control socket: Protocol not supported

BTW: I edit trunk/user/dnsmasq/src/config.h direct and uncommet the "defined 
HAVE_IPSET" line, is this a right way?

Original comment by pun...@gmail.com on 12 Feb 2014 at 1:32

GoogleCodeExporter commented 9 years ago

In .config you may see:

### Include IPSet utility, and kernel modules (~0.4MB)
CONFIG_FIRMWARE_INCLUDE_IPSET=y

Why do you not like it?

Original comment by Dr.Sydorenko.O on 13 Feb 2014 at 6:59

GoogleCodeExporter commented 9 years ago

Dr.Sydorenko.O,

At the first time before i wrote comment, in .config it have these line already:

### Include IPSet utility, and kernel modules (~0.4MB)
CONFIG_FIRMWARE_INCLUDE_IPSET=y

Yes, in this case, "ipset" command working, "iptables -set" working too, But 
when i wrote some ipset line in dnsmasq.conf, like:

ipset=/youtube.com/gfwlist

Then dnsmasq may start failed and log:

dnsmasq[545]: recompile with HAVE_IPSET defined to enable ipset directives.

So i edit the config.h file like the second comment i said, but got another 
failed start log:

dnsmasq[515]:failed to create IPset control socket: Protocol not supported.

Sorry my english, i wish you can get my point.

Original comment by pun...@gmail.com on 14 Feb 2014 at 2:13

GoogleCodeExporter commented 9 years ago

Jul  7 17:54:50 automount: Activate swap partition /dev/sda3 SUCCESS!
Jul  7 17:54:51 dnsmasq[431]: failed to create IPset control socket: Protocol 
not supported
Jul  7 17:54:51 dnsmasq[431]: FAILED to start up
Jul  7 17:54:51 kernel: Ralink HW NAT v2.50.7 Module Enabled, ASIC: RT3883, 
REV: 0105, FoE Size: 16384
Jul  7 17:54:51 kernel: EXT4-fs (sda2): warning: mounting unchecked fs, running 
e2fsck is recommended
Jul  7 17:54:51 kernel: EXT4-fs (sda2): mounted filesystem without journal. 
Opts: (null)
Jul  7 17:54:51 RT-N56U: Hardware NAT/Routing: Enabled, IPoE/PPPoE offload 
[WAN]<->[LAN/WLAN]
Jul  7 17:54:51 RT-N56U: Hardware NAT/Routing: IPv4 UDP flow offload - OFF
Jul  7 17:54:51 RT-N56U: Hardware NAT/Routing: IPv6 routes offload - OFF
Jul  7 17:54:51 kernel: EXT4-fs (sda1): mounted filesystem with ordered data 
mode. Opts: (null)
Jul  7 17:54:51 kernel: eth3: ===> VirtualIF_open
Jul  7 17:54:51 DHCP WAN Client: starting on eth3 ...
Jul  7 17:54:52 opt-mount.sh: started [/dev/sda1 /media/Main]
Jul  7 17:54:52 kernel: br0: port 1(eth2) entering forwarding state
Jul  7 17:54:52 httpd[535]: Server listening port 80 (HTTP).
Jul  7 17:54:52 dropbear[544]: Running in background
Jul  7 17:54:52 miniupnpd[552]: version 1.8 started
Jul  7 17:54:52 miniupnpd[552]: HTTP listening on port 14058
Jul  7 17:54:53 kernel: Netfilter messages via NETLINK v0.30.
Jul  7 17:54:53 kernel: ip_set: protocol 6
Jul  7 17:54:55 DHCP WAN Client: bound (eth3), IP: 192.168.8.30, GW: 
192.168.8.1, lease time: 86400
Jul  7 17:54:55 RT-N56U: WAN up (eth3)
Jul  7 17:54:59 IPT: firewall started
Jul  7 17:55:00 Samba Server: daemon is started
Jul  7 17:55:00 opt-start.sh: call /opt/etc/init.d
Jul  7 17:55:02 NTP Client: Synchronizing time to pool.ntp.org.
Jul  7 17:55:03 IPT: firewall already started
Jul  7 17:55:03 shadowsocks: Starting ss-local... 
Jul  7 17:55:03 shadowsocks: ss-local start success. 
Jul  7 17:55:03 shadowsocks: Starting ss-redir... 
Jul  7 17:55:03 shadowsocks: ss-redir start success. 
Jul  7 17:55:03 redsocks: Starting redsocks... 
Jul  7 17:55:03 redsocks: redsocks start success. 
Jul  7 17:55:03 pdnsd: Starting pdnsd... 
Jul  7 17:55:03 pdnsd[714]: pdnsd-1.2.9b-par starting.
Jul  7 17:55:03 pdnsd: pdnsd start success. 
Jul  7 17:55:12 watchdog: dnsmasq is missing, start again!
Jul  7 17:55:12 dnsmasq[725]: started, version 2.68 cachesize 1000
Jul  7 17:55:12 dnsmasq[725]: compile time options: IPv6 GNU-getopt no-RTC 
no-DBus no-i18n no-IDN DHCP DHCPv6 no-scripts TFTP no-conntrack ipset no-auth
Jul  7 17:55:12 dnsmasq[725]: warning: ignoring resolv-file flag because 
no-resolv is set
Jul  7 17:55:12 dnsmasq-dhcp[725]: DHCP, IP range 192.168.1.2 -- 192.168.1.244, 
lease time 1d
Jul  7 17:55:12 dnsmasq-dhcp[725]: DHCP, sockets bound exclusively to interface 
br0
............................................................................
Jul  7 17:55:12 dnsmasq[725]: read /etc/storage/dnsmasq/hosts - 0 addresses
Jul  7 17:55:32 NTP Client: Synchronizing time to time.nist.gov.
Jul  7 17:55:39 NTP Client: System time changed, offset: 3.486095s
Jul  7 18:01:03 dropbear[829]: Child connection from 192.168.1.134:53291
Jul  7 18:01:03 dropbear[829]: Password auth succeeded for 'admin' from 
192.168.1.134:53291

It seems like dnsmasq start too early? First the dnsmasq start failed, the 
watchdog reload dnsmasq succes later.

Original comment by pun...@gmail.com on 7 Jul 2014 at 1:55

callnothing commented 7 years ago

same problem, any body can explain this

padavanfirmware / rt-n56u

dnsmasq: recompile with HAVE_IPSET defined #1158