Was dnsmasq updated or change from the last 2 months releases? apparently a flag which was working broke my configuration. _________________ Linksys WRT54GS v2.0 (corerev=7)
Asus WL-520GU (corerev=13)
Last edited by usera on Sun Jun 21, 2009 8:03; edited 1 time in total
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sun Jun 21, 2009 6:57 Post subject:
If what you have listed from your signature is correct, usera, then you really should be starting your own thread. This thread is about the newest firmware (pre-sp2) and possible issues with that firmware. What you have listed is not what this thread is about and there is a *good* chance it is also the cause of your problem.
Please check the Peacock thread (see my signature) about upgrading past the buggy firmware you have now. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Posted: Sun Jun 21, 2009 15:01 Post subject: uPnP looking good!
I upgraded to this new build, and Mac OS X 10.5's "Back To My Mac," which relies on a uPnP-compatible router, is no longer reporting errors 20 minutes after a router reboot! I'll have to get offsite some time soon and see if the feature actually works.
One small difference I had to work around... I have some wired computers that use fixed IP addresses, and they used to list the router (192.168.10.1) as both the router and the DNS field. The router has the OpenDNS IPs configured within, and the clients were getting copies of those DNS IPs with the older build. Before this build, using the "Manual" setting worked fine. After this build, the fixed-IP Macs didn't see a DNS server any more, so I had to change them to the "DHCP with a Manual Address" option, and they worked again. The TiVos had no such trouble, but they're on the other side of a bridge. We'll see what happens when I switch them to a wired connection next week.
Posted: Sun Jun 21, 2009 16:14 Post subject: Re: uPnP looking good!
stevem wrote:
One small difference I had to work around... I have some wired computers that use fixed IP addresses, and they used to list the router (192.168.10.1) as both the router and the DNS field. The router has the OpenDNS IPs configured within, and the clients were getting copies of those DNS IPs with the older build. Before this build, using the "Manual" setting worked fine. After this build, the fixed-IP Macs didn't see a DNS server any more, so I had to change them to the "DHCP with a Manual Address" option, and they worked again.
Steve[/img][/i]
That sounds a bit strange to me, manual is really manual and you have to setup all information manually in the client.
Clients getting their IP address via DHCP do also get the gateway address and the DNS server(s) in the DHCP response packet.
That is also why "DHCP with Manual Address" works for you. _________________ Kernel panic: Aiee, killing interrupt handler!
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sun Jun 21, 2009 22:36 Post subject:
Hmmm, I have noticed an issue with DDNS on this version. Two days after updating the firmware (current set time on DDNS updating) I have appearantly started getting errors updating the IP address.
Quote:
Thu Jun 18 06:08:17 2009: INADYN: Started 'INADYN Advanced version 1.96-ADV' - dynamic DNS updater.
Thu Jun 18 06:08:17 2009: INADYN: IP read from cache file is 'x.x.x.x'. No update required.
Fri Jun 19 00:31:44 2009: INADYN:IP: Error 0x83 in recv()
Fri Jun 19 00:31:44 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jun 19 00:31:44 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 182)
Fri Jun 19 08:54:59 2009: INADYN:IP: Error 0x83 in recv()
Fri Jun 19 08:54:59 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jun 19 08:54:59 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 265)
Fri Jun 19 20:50:34 2009: I:INADYN: IP address for alias 'xxxxxxxx.xxxxxx.net' needs update to 'x.x.x.x'
Fri Jun 19 20:50:34 2009: I:INADYN: Alias 'xxxxxxxx.xxxxxx.net' to IP 'x.x.x.x' updated successfully.
Fri Jun 19 23:28:13 2009: INADYN:IP: Error 0x83 in recv()
Fri Jun 19 23:28:13 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jun 19 23:28:13 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 409)
Sat Jun 20 00:29:20 2009: INADYN:IP: Error '0x16' resolving host name 'checkip.dyndns.org'
Sat Jun 20 00:29:20 2009: W: DYNDNS: Error 'RC_IP_INVALID_REMOTE_ADDR' (0x12) when talking to IP server
Sat Jun 20 00:29:20 2009: W:'RC_IP_INVALID_REMOTE_ADDR' (0x12) updating the IPs. (it 419)
Sat Jun 20 03:31:14 2009: INADYN:IP: Error 0x83 in recv()
Sat Jun 20 03:31:14 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sat Jun 20 03:31:14 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 449)
Sat Jun 20 04:48:12 2009: INADYN:IP: Error 0x83 in recv()
Sat Jun 20 04:48:12 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sat Jun 20 04:48:12 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 461)
Sat Jun 20 21:52:47 2009: INADYN:IP: Error 0x83 in recv()
Sat Jun 20 21:52:47 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sat Jun 20 21:52:47 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 630)
Sun Jun 21 10:24:33 2009: INADYN:IP: Error 0x83 in recv()
Sun Jun 21 10:24:33 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sun Jun 21 10:24:33 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 754)
Sun Jun 21 16:28:20 2009: INADYN:IP: Error 0x83 in recv()
Sun Jun 21 16:28:20 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sun Jun 21 16:28:20 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 814)
Sun Jun 21 18:11:43 2009: INADYN:IP: Error 0x83 in recv()
Sun Jun 21 18:11:43 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sun Jun 21 18:11:43 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 831)
Sun Jun 21 21:01:28 2009: INADYN:IP: Error 0x83 in recv()
Sun Jun 21 21:01:28 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sun Jun 21 21:01:28 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 859)
Sun Jun 21 22:08:10 2009: INADYN:IP: Error 0x83 in recv()
Sun Jun 21 22:08:10 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sun Jun 21 22:08:10 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 870)
Sun Jun 21 22:20:17 2009: INADYN:IP: Error 0x83 in recv()
Sun Jun 21 22:20:17 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sun Jun 21 22:20:17 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 872)
Sun Jun 21 22:38:28 2009: I:INADYN: IP address for alias 'xxxxxxxx.xxxxxx.net' needs update to 'x.x.x.x'
Sun Jun 21 22:38:28 2009: I:INADYN: Alias 'xxxxxxxx.xxxxxx.net' to IP 'x.x.x.x' updated successfully.
Mon Jun 22 00:45:48 2009: INADYN:IP: Error 0x83 in recv()
Mon Jun 22 00:45:48 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Jun 22 00:45:48 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 896)
Mon Jun 22 02:59:32 2009: INADYN:IP: Error 0x83 in recv()
Mon Jun 22 02:59:32 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Jun 22 02:59:32 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 918)
Anyone else noticing these errors using DynDNS.org? _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Posted: Mon Jun 22, 2009 4:13 Post subject: build 12188 and 12307 with no wireless internet connection
Hi,
I am new to this and have a question.
I have a wrt310n router with a build 12188 installed on the router.
Q)Will the new build 12307 work with the wrt310n and is there any issues, and if no issues what would I do on the installing of the firmware and which firmware to use.
Because my build 12188 works except the wireless,when I connect it says connected with limited access so i was wondering if the new build 12307 would fix this issue
Posted: Mon Jun 22, 2009 4:36 Post subject: Re: build 12188 and 12307 with no wireless internet connecti
wrt310n wrote:
Hi,
I am new to this and have a question. I have a wrt310n router with a build 12188 installed on the router.
Q)Will the new build 12307 work with the wrt310n and is there any issues, and if no issues what would I do on the installing of the firmware and which firmware to use.
Because my build 12188 works except the wireless,when I connect it says connected with limited access so i was wondering if the new build 12307 would fix this issue
Thank,
Chris
I’m certainly NO dd-wrt expert... that said I was seeing that also on my Vista system. To correct that (for me) I assigned a channel 6 on the router vs. leaving it set to Auto. YMMV
Posted: Mon Jun 22, 2009 4:59 Post subject: Re: build 12188 and 12307 with no wireless internet connecti
wrt310n wrote:
Because my build 12188 works except the wireless,when I connect it says connected with limited access so i was wondering if the new build 12307 would fix this issue
Thank,
Chris
This is a configuration issue; a build change won't fix it. For some reason your router is not assigning dhcp. Post a new separate thread and we will sort it out. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
I just installed build 12307 on my WHR-HP-G54, and when I try to configure it as a wireless bridge according to the tutorial I can't seem to get it to connect to my host router(access point) using site survey. I also did a hard reset after installing the build.
When I was using v24-sp1_standard everything worked fine, but with this build it fails when I set it up as a wireless bridge. Any ideas?
I just installed build 12307 on my WHR-HP-G54, and when I try to configure it as a wireless bridge according to the tutorial I can't seem to get it to connect to my host router(access point) using site survey. I also did a hard reset after installing the build.
When I was using v24-sp1_standard everything worked fine, but with this build it fails when I set it up as a wireless bridge. Any ideas?
WG
First off hello to you as well, but you actually need to post your configuration questions up one level in the main forum not here as this thread is to give feedback on actual firmware issues for this build.
Hmmm, I have noticed an issue with DDNS on this version. Two days after updating the firmware (current set time on DDNS updating) I have appearantly started getting errors updating the IP address.
Quote:
Thu Jun 18 06:08:17 2009: INADYN: Started 'INADYN Advanced version 1.96-ADV' - dynamic DNS updater.
Thu Jun 18 06:08:17 2009: INADYN: IP read from cache file is 'x.x.x.x'. No update required.
Fri Jun 19 00:31:44 2009: INADYN:IP: Error 0x83 in recv()
Fri Jun 19 00:31:44 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jun 19 00:31:44 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 182)
Fri Jun 19 08:54:59 2009: INADYN:IP: Error 0x83 in recv()
Fri Jun 19 08:54:59 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jun 19 08:54:59 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 265)
Fri Jun 19 20:50:34 2009: I:INADYN: IP address for alias 'xxxxxxxx.xxxxxx.net' needs update to 'x.x.x.x'
Fri Jun 19 20:50:34 2009: I:INADYN: Alias 'xxxxxxxx.xxxxxx.net' to IP 'x.x.x.x' updated successfully.
Fri Jun 19 23:28:13 2009: INADYN:IP: Error 0x83 in recv()
...snip...
Anyone else noticing these errors using DynDNS.org?
Yes, I also use DynDns and I'm seeing the same thing.
Posted: Mon Jun 22, 2009 15:42 Post subject: Re: build 12188 and 12307 with no wireless internet connecti
Murrkf wrote:
wrt310n wrote:
Because my build 12188 works except the wireless,when I connect it says connected with limited access so i was wondering if the new build 12307 would fix this issue
Thank,
Chris
This is a configuration issue; a build change won't fix it. For some reason your router is not assigning dhcp. Post a new separate thread and we will sort it out.
I'm not sure this is a configuration issue. I too have been experiencing this problem with my WRT310N. This issue has existed for me from 12188 to 12307. It seems the wireless signal on the clients will drop from 54 megs to 1 in 10 seconds with some settings and sometimes it will just be 1 and the limited connectivity error. It IS possible to get solid speeds with the N band enabled but nothing above 36 or 48 for me. And when the wireless is running poorly, the router runs bad (even the wired connections).
To get the router running really good for me, I used the following settings:
(some came from other posters)
Change the wireless mode to BG-Mixed
Manually set the channel (I had the best results with 7 in my setup)
ACK = 0
WPA2 Personal Mixed w/ AES
CTS Protection = Disabled
Frame Burst = Disabled
Beacon = 50
Preamble = Auto
TX Power = 40 (32 and above worked fine)
Afterburner = Disabled
WMM = Disabled
I have all wireless G clients ATM but I am wanting to mix N and G since I have a printer with a G card and my phone has a G card. Maybe it can still be a config issue but I have run out of configuration schemes. If anyone has insite, please share. Thank you.
Posted: Mon Jun 22, 2009 16:20 Post subject: Re: build 12188 and 12307 with no wireless internet connecti
fearreality wrote:
Murrkf wrote:
wrt310n wrote:
Because my build 12188 works except the wireless,when I connect it says connected with limited access so i was wondering if the new build 12307 would fix this issue
Thank,
Chris
This is a configuration issue; a build change won't fix it. For some reason your router is not assigning dhcp. Post a new separate thread and we will sort it out.
I'm not sure this is a configuration issue. I too have been experiencing this problem with my WRT310N. This issue has existed for me from 12188 to 12307. It seems the wireless signal on the clients will drop from 54 megs to 1 in 10 seconds with some settings and sometimes it will just be 1 and the limited connectivity error. It IS possible to get solid speeds with the N band enabled but nothing above 36 or 48 for me. And when the wireless is running poorly, the router runs bad (even the wired connections).
To get the router running really good for me, I used the following settings:
(some came from other posters)
Change the wireless mode to BG-Mixed
Manually set the channel (I had the best results with 7 in my setup)
ACK = 0
WPA2 Personal Mixed w/ AES
CTS Protection = Disabled
Frame Burst = Disabled
Beacon = 50
Preamble = Auto
TX Power = 40 (32 and above worked fine)
Afterburner = Disabled
WMM = Disabled
I have all wireless G clients ATM but I am wanting to mix N and G since I have a printer with a G card and my phone has a G card. Maybe it can still be a config issue but I have run out of configuration schemes. If anyone has insite, please share. Thank you.
Try enabling WMM Support and CTS Protection mode to Auto. _________________ R7000 Kong vpn 23550-R01 (Main Router)
WRT610Nv2 converted E3000 vpnKong 21661 (RB)
WRT600N v1.1 BS std-nokaid 13637(5Ghz CB)(2.4Ghz AP)
WRT54G v5 BS micro 14684(RB)
I did and that was when I was stable at about 48 megs on channel 9. After 2 days though it would only be stable at 36. I will try again just to confirm though, and I will also wait 5 to 10 minutes after making the setting changes to see if it helps (read in another post it "evens" out).
I did and that was when I was stable at about 48 megs on channel 9. After 2 days though it would only be stable at 36. I will try again just to confirm though, and I will also wait 5 to 10 minutes after making the setting changes to see if it helps (read in another post it "evens" out).
I personally don't always go by what the router status page says. You are probably fine in this particular case but I know I'm a perfectionist when it comes to things so it drives me crazy if I just don't sit back and stop worrying about it. Because it is not going to show 54Mbps all of the time especially when you are looking at it. _________________ R7000 Kong vpn 23550-R01 (Main Router)
WRT610Nv2 converted E3000 vpnKong 21661 (RB)
WRT600N v1.1 BS std-nokaid 13637(5Ghz CB)(2.4Ghz AP)
WRT54G v5 BS micro 14684(RB)
