Posted by hans2 on Feb 26, 2016; 9:00pm
URL: https://itus.accessinnov.com/bridge-mode-not-working-tp178p181.html

Hi Breda

i've scanned your log files for words like: fail, failed, error, can't

this is what i've found:

----

Fri Feb 19 00:11:06 2016 kern.info kernel: [   48.226365] EXT3-fs (mmcblk0p4): mounted filesystem with writeback data mode 
Fri Feb 19 00:11:06 2016 user.err kernel: [   48.518963] init: failed to symlink /tmp -> /var 

unrelated, there is a redundant link option in the startup script.

----

 [   26.991163] octeon-pow-ethernet ERROR: You must specify a broadcast group mask. 

the lack of broadcasting should not cause your network failure. However this can be solved with adding the broadcast address:

in CLI run command:

uci set network.lan.broadcast=x.y.z.255

where x.y.z is your network IP range (example 192.168.0 or 10.10.10)

the other option is to edit the /etc/config/network file and add to the section config interface 'lan'
the line:
        option broadcast 'x.y.x.255'

----

 
Fri Feb 19 00:24:34 2016 daemon.err uhttpd[5285]: cut: standard output: Broken pipe 
Fri Feb 19 00:24:35 2016 daemon.err uhttpd[5285]: cat: can't open '/.do_date': No such file or directory 

unrelated. If you want to remove it, go to CLI and type in

touch /.do_date

however this date will be updated as soon as fwupgrade is run.

----

Fri Feb 19 00:20:00 2016 cron.info crond[3190]: USER root pid 6164 cmd /usr/sbin/ntpclient -s -p 123 -h 0.us.pool.ntp.org || /etc/init.d/ntpclient restart 
Fri Feb 19 00:20:00 2016 user.notice root: NTP 0.us.pool.ntp.org failed. 
Fri Feb 19 00:20:00 2016 user.notice root: NTP 0.us.pool.ntp.org failed. 
Fri Feb 19 00:20:00 2016 user.notice root: NTP 0.us.pool.ntp.org failed. 
Fri Feb 19 00:20:00 2016 user.notice root: NTP 0.us.pool.ntp.org failed. 
Fri Feb 19 00:20:00 2016 user.notice root: NTP 0.us.pool.ntp.org failed. 
Fri Feb 19 00:20:00 2016 user.notice root: NTP eager clock adjust failed. 

This is due to the lack of connection when the NTP client is started - you can ignore this as the default schedule will resolve it in 10 minutes.

----

Fri Feb 19 00:11:53 2016 daemon.crit dnsmasq[5365]: bad option at line 69 of /etc/ITUS_DNS.txt 
Fri Feb 19 00:11:53 2016 daemon.crit dnsmasq[5365]: FAILED to start up 
Fri Feb 19 00:11:53 2016 user.notice update_webfilter: updated dnsmasq blacklist 
Fri Feb 19 00:11:53 2016 user.notice update_webfilter: updated network.interface.blockdomain: 192.168.1.112 
Fri Feb 19 00:11:53 2016 user.notice update_webfilter: updated firewall.@redirect[0].Itusfilter: 192.168.1.112 
Fri Feb 19 00:11:53 2016 user.notice update_webfilter: updated firewall.@redirect[1]dns-traffic-to-shield: 192.168.1.112 
Fri Feb 19 00:11:53 2016 user.notice update_webfilter: updated uhttpd.Itusfilter 
Fri Feb 19 00:11:53 2016 daemon.crit dnsmasq[5380]: bad option at line 69 of /etc/ITUS_DNS.txt 
Fri Feb 19 00:11:53 2016 daemon.crit dnsmasq[5380]: FAILED to start up 

This could be the cause, DNSMASQ is not starting.

Try to make an update in the online blacklist (LUCI > Services > Web Filter > Black List). With "an update" I mean changing or add/remove a line and press Save&Apply
Once it is done, restart DNSMASQ in the Initscripts (LUCI > System > Startup) and RESTART dnsmasq (prio 60)


Have you installed any of the hotfixes, like Hotfix-160210?