USE AT YOUR OWN RISK
Revision 2bf3cf25 5 May 2012 12.04.7z
http://goo.gl/bJNNE
- add ddns provider joker.com, thanks to contribution from Rui Miguel Silva Seabra
- some work on web interface for openvpn
- add patch for major security issue recently identified in samba
- update tor to 2.3.13-alpha
etc
etc
Revision 2bf3cf25 5 May 2012 12.04.7z
Moderator: Moderators
Re: Revision 2bf3cf25 5 May 2012 12.04.7z
Just FYI, the new OpenVPN stuff is in a separate branch, so I doubt this build includes that. The OpenVPN code isn't at all useable yet... so you probably don't want what's there anyway.
Re: Revision 2bf3cf25 5 May 2012 12.04.7z
Thanks for the info
Re: Revision 2bf3cf25 5 May 2012 12.04.7z
If you guys are compiling custom images, or if Eric even wants to include this patch special in the next Gargoyle release (it might stay in trunk and not get backported for all I know), supposedly this fixes the failed to stop dma problem so many people have reported with Atheros routers on this forum:
https://dev.openwrt.org/changeset/31689/trunk
https://dev.openwrt.org/changeset/31689/trunk
WRT54GL v1.1
Gargoyle 1.4.7
Gargoyle 1.4.7
Re: Revision 2bf3cf25 5 May 2012 12.04.7z
The issue in doing that is that this patch is being applied to a different version of the mac80211 code. If you look at the Makefile in trunk vs backfire you'll see the version in trunk is from April, while the version in backfire is from last december.
So... even if the patch applied cleanly, I'm not sure if the reasoning behind the patch is still sound in the older version... it's possible that it could make things worse! If the patch can be backported I suspect the OpenWrt developers will do so, at which point it will be incorporated.
Of course if someone wants to try this experiment and report back... I'd be more than happy to include the patch right away if I have evidence that it is an improvement. Otherwise, I don't want to risk inadvertantly making things worse. I just don't know enough about the wireless kernel code to fully understand what the patch is doing, so I prefer to play it safe.
So... even if the patch applied cleanly, I'm not sure if the reasoning behind the patch is still sound in the older version... it's possible that it could make things worse! If the patch can be backported I suspect the OpenWrt developers will do so, at which point it will be incorporated.
Of course if someone wants to try this experiment and report back... I'd be more than happy to include the patch right away if I have evidence that it is an improvement. Otherwise, I don't want to risk inadvertantly making things worse. I just don't know enough about the wireless kernel code to fully understand what the patch is doing, so I prefer to play it safe.
Re: Revision 2bf3cf25 5 May 2012 12.04.7z
It's 5 lines of code it changes and has no bearing on anything else but the function order (ie., the tx function occuring before the rx function, thus the error stop rx before tx)... I guess Atheros users will hope for a backport.
WRT54GL v1.1
Gargoyle 1.4.7
Gargoyle 1.4.7
Re: Revision 2bf3cf25 5 May 2012 12.04.7z
I was using 1.5.X (Built 20120130-0339 git@6c084a4) until today. git@6c084a4 was working fine for me, and i didn't had any problems. The uptime was like 45 days, then router rebooted itself, but after reboot was still working fine.
The git@2bf3cf2 is working well for me too (for a few minutes:P), no errors after boot on logread, using N with 40Mhz on channel 10 (and 6). The first difference i see is memory usage (about 2MB more than previous, but not matter, still like 40% free). And well, we will see.
Thanks for sharing this update.
Update: Houston, we got problem. Inssider told me that my router use only channel 10 :S So no real 300Mb/s (i'll try to change channel to 11 and see if it will help). My current config is channel 10, 40Mhz, 2nd chan. below.
Update2: Change to channel 11 did help, but after a moment wifi signal disappeared. I turn off router from power, turn on again and it works now, but i'll try to move back to channel 10 or 9, because my laptop wifi card do not support frequency above channel 11.
Update3: Changed port to 9, click Save, routeer changed channels correctly (9+5) and after a second signal is gone (browser window with configuration stays at: please wait while settings are applied), wifi do not work at all. I checked with second computer and mobile phone - no wifi. I connected with cable - internet is working, no connection problem. Some info from logread:
Many many lines of very old bug: So i didn't find error log for the problem with wifi. The dmesg command add few lines at the end like that:
While web gui is working thru the cable i will try to make reboot now with cable connected, and change wifi channel looking on logread to see if i can catch the error moment.
Ok after reboot from GUI wifi works fine (chan 9+5), the logread do not show those errors and dmesg add only few line like this:
My next move is to change channel to 10(+6) and see what will happen with logread. Here is the result:
But - the router didn't lost the wifi signal, it uses channel 10 - but same time second channel do not work, so if channel 10 is selected, no second channel (even it's working with channel 9 or 11).
Now i will reboot router again, and the summary is: Channel 10+6 is working, and no errors in logread. So it looks like changing channel making problems, and only reboot helps. Now i will connect with wifi again, leave it work for some time and see how it's going on.
The git@2bf3cf2 is working well for me too (for a few minutes:P), no errors after boot on logread, using N with 40Mhz on channel 10 (and 6). The first difference i see is memory usage (about 2MB more than previous, but not matter, still like 40% free). And well, we will see.
Thanks for sharing this update.
Update: Houston, we got problem. Inssider told me that my router use only channel 10 :S So no real 300Mb/s (i'll try to change channel to 11 and see if it will help). My current config is channel 10, 40Mhz, 2nd chan. below.
Update2: Change to channel 11 did help, but after a moment wifi signal disappeared. I turn off router from power, turn on again and it works now, but i'll try to move back to channel 10 or 9, because my laptop wifi card do not support frequency above channel 11.
Update3: Changed port to 9, click Save, routeer changed channels correctly (9+5) and after a second signal is gone (browser window with configuration stays at: please wait while settings are applied), wifi do not work at all. I checked with second computer and mobile phone - no wifi. I connected with cable - internet is working, no connection problem. Some info from logread:
Many many lines of very old bug:
Code: Select all
May 15 11:12:09 berlin daemon.warn dnsmasq-dhcp[5634]: DHCP packet received on eth0.2 which has no addressCode: Select all
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
ar71xx-wdt: enabling watchdog timer
br-lan: port 2(wlan0) entering disabled state
br-lan: port 1(eth0.1) entering disabled state
device eth0 left promiscuous mode
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device eth0.1 left promiscuous mode
br-lan: port 1(eth0.1) entering disabled state
device eth0.1 entered promiscuous mode
device eth0 entered promiscuous mode
br-lan: port 1(eth0.1) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
Ok after reboot from GUI wifi works fine (chan 9+5), the logread do not show those errors and dmesg add only few line like this:
Code: Select all
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
ar71xx-wdt: enabling watchdog timer
Code: Select all
May 15 11:24:49 berlin daemon.notice miniupnpd[1862]: received signal 15, good-bye
May 15 11:24:50 berlin daemon.info dnsmasq[1742]: exiting on receipt of SIGTERM
May 15 11:24:52 berlin user.info kernel: br-lan: port 2(wlan0) entering disabled state
May 15 11:24:52 berlin user.info kernel: br-lan: port 1(eth0.1) entering disabled state
May 15 11:24:52 berlin user.info kernel: device eth0 left promiscuous mode
May 15 11:24:52 berlin user.info kernel: device wlan0 left promiscuous mode
May 15 11:24:52 berlin user.info kernel: br-lan: port 2(wlan0) entering disabled state
May 15 11:24:52 berlin user.info kernel: device eth0.1 left promiscuous mode
May 15 11:24:52 berlin user.info kernel: br-lan: port 1(eth0.1) entering disabled state
May 15 11:24:52 berlin daemon.info pppd[518]: Terminating on signal 15
May 15 11:24:52 berlin daemon.info pppd[518]: Connect time 3.3 minutes.
May 15 11:24:52 berlin daemon.info pppd[518]: Sent 29381 bytes, received 128398 bytes.
May 15 11:24:52 berlin daemon.notice pppd[518]: Connection terminated.
May 15 11:24:53 berlin daemon.info pppd[518]: Exit.
May 15 11:24:59 berlin user.notice ifup: Enabling Router Solicitations on loopback (lo)
May 15 11:25:00 berlin user.info kernel: device eth0.1 entered promiscuous mode
May 15 11:25:00 berlin user.info kernel: device eth0 entered promiscuous mode
May 15 11:25:00 berlin user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
May 15 11:25:01 berlin daemon.info pppd[3523]: Plugin rp-pppoe.so loaded.
May 15 11:25:01 berlin daemon.notice pppd[3523]: pppd 2.4.4 started by root, uid 0
May 15 11:25:01 berlin daemon.info pppd[3523]: PPP session is 21280
May 15 11:25:01 berlin daemon.info pppd[3523]: Using interface pppoe-wan
May 15 11:25:01 berlin daemon.notice pppd[3523]: Connect: pppoe-wan <--> eth0.2
May 15 11:25:01 berlin user.info kernel: device wlan0 entered promiscuous mode
May 15 11:25:01 berlin user.info kernel: br-lan: port 2(wlan0) entering forwarding state
May 15 11:25:01 berlin daemon.info pppd[3523]: CHAP authentication succeeded: CHAP authentication success, unit 5264
May 15 11:25:01 berlin daemon.notice pppd[3523]: CHAP authentication succeeded
May 15 11:25:01 berlin daemon.notice pppd[3523]: peer from calling number xx:xx:xx:xx:xx:xx authorized
May 15 11:25:02 berlin daemon.notice pppd[3523]: local IP address xxx
May 15 11:25:02 berlin daemon.notice pppd[3523]: remote IP address xxx
May 15 11:25:02 berlin daemon.notice pppd[3523]: primary DNS address xxx
May 15 11:25:02 berlin daemon.notice pppd[3523]: secondary DNS address xxx
May 15 11:25:02 berlin user.notice ifup: Enabling Router Solicitations on lan (br-lan)
May 15 11:25:02 berlin user.notice ifup: Enabling Router Solicitations on lan (br-lan)
May 15 11:25:03 berlin user.notice ifup: Enabling Router Solicitations on wan (pppoe-wan)
May 15 11:25:04 berlin user.notice root: starting ntpclient
May 15 11:25:55 berlin user.info kernel: device wlan0 left promiscuous mode
May 15 11:25:55 berlin user.info kernel: br-lan: port 2(wlan0) entering disabled state
May 15 11:25:56 berlin user.info kernel: device wlan0 entered promiscuous mode
May 15 11:25:56 berlin user.info kernel: br-lan: port 2(wlan0) entering forwarding state
May 15 11:25:58 berlin user.err firewall: DNAT redirect redirect_enabled_number_0: needs src and dest_ip or dest_port, skipping
May 15 11:25:58 berlin user.err firewall: DNAT redirect redirect_enabled_number_1: needs src and dest_ip or dest_port, skipping
May 15 11:25:58 berlin user.err firewall: DNAT redirect redirect_enabled_number_2: needs src and dest_ip or dest_port, skipping
May 15 11:25:58 berlin user.err firewall: DNAT redirect redirect_enabled_number_3: needs src and dest_ip or dest_port, skipping
May 15 11:25:58 berlin user.err firewall: DNAT redirect redirect_enabled_number_4: needs src and dest_ip or dest_port, skipping
May 15 11:25:58 berlin user.err firewall: DNAT redirect redirect_enabled_number_5: needs src and dest_ip or dest_port, skipping
May 15 11:25:58 berlin user.err firewall: DNAT redirect redirect_enabled_number_6: needs src and dest_ip or dest_port, skipping
May 15 11:25:58 berlin user.err firewall: DNAT redirect redirect_enabled_number_7: needs src and dest_ip or dest_port, skipping
May 15 11:26:08 berlin user.info firewall: adding lan (br-lan) to zone lan
May 15 11:26:09 berlin user.info firewall: adding wan (pppoe-wan) to zone wan
May 15 11:26:10 berlin user.notice miniupnpd: adding firewall rules for pppoe-wan to zone wan
May 15 11:26:10 berlin user.info syslog: SNet version started
May 15 11:26:10 berlin daemon.notice miniupnpd[4265]: HTTP listening on port 5000
May 15 11:26:10 berlin daemon.notice miniupnpd[4265]: Listening for NAT-PMP traffic on port 5351
May 15 11:26:10 berlin user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
May 15 11:26:10 berlin user.notice dnsmasq: Allowing 127.0.0.0/8 responses
May 15 11:26:11 berlin cron.err crond[4359]: crond (busybox 1.15.3) started, log level 9
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: started, version 2.55 cachesize 150
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
May 15 11:26:14 berlin daemon.info dnsmasq-dhcp[4502]: DHCP, IP range 192.168.1.100 -- 192.168.1.250, lease time 12h
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain micro
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain micro
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain micro
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain oss
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain oss
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain oss
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain null
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain null
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain null
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain ing
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain ing
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain ing
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain indy
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain indy
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain indy
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain gopher
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain gopher
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain gopher
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain geek
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain geek
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain geek
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain fur
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain fur
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain fur
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain free
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain free
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain free
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain bbs
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain bbs
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain bbs
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain dyn
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain dyn
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain dyn
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain parody
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain parody
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain parody
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain glue
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain glue
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain glue
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 78.47.86.43#53 for domain bit
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 178.32.31.41#53 for domain bit
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using local addresses only for domain lan
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: reading /tmp/resolv.conf.auto
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 217.30.137.200#53
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 217.30.129.149#53
May 15 11:26:14 berlin daemon.warn dnsmasq[4502]: ignoring nameserver 192.168.1.1 - local interface
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain micro
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain micro
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain micro
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain oss
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain oss
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain oss
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain null
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain null
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain null
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain ing
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain ing
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain ing
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain indy
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain indy
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain indy
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain gopher
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain gopher
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain gopher
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain geek
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain geek
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain geek
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain fur
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain fur
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain fur
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain free
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain free
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain free
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain bbs
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain bbs
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain bbs
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain dyn
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain dyn
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain dyn
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain parody
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain parody
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain parody
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.142.171.235#53 for domain glue
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 95.211.32.162#53 for domain glue
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 66.244.95.20#53 for domain glue
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 78.47.86.43#53 for domain bit
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using nameserver 178.32.31.41#53 for domain bit
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: using local addresses only for domain lan
May 15 11:26:14 berlin daemon.info dnsmasq[4502]: read /etc/hosts - 4 addresses
May 15 11:26:14 berlin daemon.info dnsmasq-dhcp[4502]: read /etc/ethers - 2 addresses
May 15 11:26:14 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:15 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:16 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:17 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:18 berlin daemon.info ddns_gargoyle[1792]: Checking whether update needed:
May 15 11:26:18 berlin daemon.info ddns_gargoyle[1792]: service provider=no-ip.com
May 15 11:26:18 berlin daemon.info ddns_gargoyle[1792]: domain=xxx
May 15 11:26:18 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:18 berlin daemon.info ddns_gargoyle[1792]: Successfully retrieved local ip from url: http://www.ipchicken.com
May 15 11:26:18 berlin daemon.info ddns_gargoyle[1792]: local IP = xxx
May 15 11:26:18 berlin daemon.info ddns_gargoyle[1792]: remote IP = xxx
May 15 11:26:18 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:19 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:19 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:19 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:20 berlin daemon.info ddns_gargoyle[1792]: Update successful
May 15 11:26:21 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:21 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:22 berlin daemon.notice miniupnpd[4265]: received signal 15, good-bye
[b]May 15 11:26:22 berlin daemon.err miniupnpd[4265]: Failed to remove pidfile /var/run/miniupnpd.pid: No such file or directory[/b]
May 15 11:26:22 berlin user.notice miniupnpd: removing firewall rules for pppoe-wan from zone wan
May 15 11:26:23 berlin user.notice miniupnpd: adding firewall rules for pppoe-wan to zone wan
May 15 11:26:23 berlin user.info syslog: SNet version started
May 15 11:26:23 berlin daemon.notice miniupnpd[4619]: HTTP listening on port 5000
May 15 11:26:23 berlin daemon.notice miniupnpd[4619]: Listening for NAT-PMP traffic on port 5351
May 15 11:26:23 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:23 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:25 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:25 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:25 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:31 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
May 15 11:26:31 berlin daemon.warn dnsmasq-dhcp[4502]: DHCP packet received on eth0.2 which has no address
and so on with same error...Now i will reboot router again, and the summary is: Channel 10+6 is working, and no errors in logread. So it looks like changing channel making problems, and only reboot helps. Now i will connect with wifi again, leave it work for some time and see how it's going on.
TL-WR1043ND HW v1.8 | FW Gargoyle 1.5.X (Built 20120504-1907 git@2bf3cf2) | 2 Mbit | PPPoE