EDIT: I have removed all references to 32bit and 64bit in this post - I made as assumption regarding the new Entware repo and my router model. Everything is 32bit - old repo, new repo, all binaries. The problem reported below still exists.
Over the last two days I completely rebuilt my RT-AC88U on 384.10_2. I did a factory reset and reformatted both JFFS and USB before reinstalling Entware.
Upon starting BIND 9.12.3-P4 I saw the following error in my logs.
The BIND server process (named) was running, but the output of netstat -anp showed it was not listening on any interface. DNS resolution was not working at all.
To get around this problem, I ended up staying on 384.10_2 and created a modified entware-setup.sh which used the old repository (http://pkg.entware.net/binaries/armv7). I then re-installed Entware from scratch, including BIND 9.11.2-3. This version of BIND started without error and is running perfectly.
This result is confusing because BIND has used TCP_FASTOPEN since version 9.11.0 - so why does 9.11.2-3 work but 9.12.3-P4 fail?
From my research, it appears that for TCP_FASTOPEN to work it requires kernel support. I'm unclear whether this means there is a problem with how kernel 384.10_2 has been compiled, or there's a problem with how BIND 9.12.3-P4 has been compiled.
Can anyone shed any light on this?
Over the last two days I completely rebuilt my RT-AC88U on 384.10_2. I did a factory reset and reformatted both JFFS and USB before reinstalling Entware.
Upon starting BIND 9.12.3-P4 I saw the following error in my logs.
Code:
named[2126]: [daemon.info] listening on IPv6 interfaces, port 53
named[2126]: [daemon.err] socket.c:5683: unexpected error:
named[2126]: [daemon.err] setsockopt(21, TCP_FASTOPEN) failed with Protocol not available
named[2126]: [daemon.info] listening on IPv4 interface lo, 127.0.0.1#53
named[2126]: [daemon.err] socket.c:5683: unexpected error:
named[2126]: [daemon.err] setsockopt(22, TCP_FASTOPEN) failed with Protocol not available
named[2126]: [daemon.info] listening on IPv4 interface eth0, <my external IP>#53
named[2126]: [daemon.err] socket.c:5683: unexpected error:
named[2126]: [daemon.err] setsockopt(23, TCP_FASTOPEN) failed with Protocol not available
named[2126]: [daemon.info] listening on IPv4 interface br0, 192.168.9.1#53
named[2126]: [daemon.err] socket.c:5683: unexpected error:
named[2126]: [daemon.err] setsockopt(24, TCP_FASTOPEN) failed with Protocol not available
...
named[2126]: [daemon.err] socket.c:5683: unexpected error:
named[2126]: [daemon.err] setsockopt(25, TCP_FASTOPEN) failed with Protocol not available
named[2126]: [daemon.notice] command channel listening on 127.0.0.1#953
The BIND server process (named) was running, but the output of netstat -anp showed it was not listening on any interface. DNS resolution was not working at all.
To get around this problem, I ended up staying on 384.10_2 and created a modified entware-setup.sh which used the old repository (http://pkg.entware.net/binaries/armv7). I then re-installed Entware from scratch, including BIND 9.11.2-3. This version of BIND started without error and is running perfectly.
This result is confusing because BIND has used TCP_FASTOPEN since version 9.11.0 - so why does 9.11.2-3 work but 9.12.3-P4 fail?
From my research, it appears that for TCP_FASTOPEN to work it requires kernel support. I'm unclear whether this means there is a problem with how kernel 384.10_2 has been compiled, or there's a problem with how BIND 9.12.3-P4 has been compiled.
Can anyone shed any light on this?
Last edited: