OUR NETWORK:TiVo Community TechLore Sling Community My DigitalEntertainer MotoDash See all... About UsAdvertiseContact Us

 
Learn about scoring Forum's Raw Score: 117606.0
January 3, 2008 01:35 AM

Categories: Troubleshooting

Rating (0 votes)
  • 1
  • 2
  • 3
  • 4
  • 5
Rate This!

Member Avatar

ewhac

Member
Joined: 12/27/2007

So the whole point of me digging into this is to find out why the KWGR614 is dropping DNS requests when configured as a WAP. After some poking around, I have made the following observations.

The facility responsible for mucking with DNS requests appears to be 'dnrd', which is a DNS proxy server. It's been configured to trap 'routerlogin.net' and handle it locally. Okay, seems easy enough, just chop 'dnrd' out of the startup scripts and recompile, except...

I can't really find any startup scripts. In fact, the only mention of 'dnrd' I can find is buried in a link library called 'libhttp_dni.a', which is linked in to 'boa', the internal Web server which serves the Web-based router configuration pages. The source code for this library is not in evidence.

Add to that the fact that the source code for the WiFi network interface (RTL8185) is supplied only as a binary blob, which might be fine if you want to stick with ucLinux. However, the RTL8651B SoC is reputed to have an MMU, meaning it can handle "real" Linux. But with a binary blob for the WiFi, compiling against a generic 2.6.x or even a 2.4.x kernel is impossible.

So. I can't compile a garden variety Linux for the platform (which means I can't construct my own idea of a build tree), and I haven't (yet) worked out how to snip 'dnrd' out of the router startup.

*sigh*

Schwab

Discussion:    Add a Comment | Comments 1-5 of 5 | Latest Comment

January 3, 2008 9:56 PM

Hmm. Nachikita's blog entry was quite informative. But if the RTL8651B has an MMU, with bother with uCLinux when a generic tarball from kernel.org should work just fine?

I'll have a look at the alleged source code at RealTek's site.  Not that I'm likely to make much sense of it...

Schwab

January 4, 2008 1:35 AM

Snarfed the driver sources for the RTL8185 at RealTek's site, and they appear complete. Moreover, it appears to work with fairly recent kernels (at least up through 2.6.22). Impressive. There may be hope for this thing yet...

Now to find out what this ROME thing is that replaces ipfilter...

Schwab

January 5, 2008 1:09 PM

Well not sure why realtek chose to use uclinux distribution - the code you see comes from the Realtek SDK with netgear specific additions - one of them is the "dns annoyances" of routerlogin.net.

I can only guess about why uCLinux distribution is used - possibly realtek wanted to use the same code base from their earlier generation 8650A/B codebase which doesn't have an MMU.

You can edit the user/Makefile to exclude dnrd just comment out the line 411

dir_y += dnrd-dnshijack

or you can even edit the dnrd-dnshijack to use the proxy but not with routerlogin.net. You can do many of the customization in the user/Makefile.

Nachi

January 5, 2008 1:43 PM

ewhac said: Snarfed the driver sources for the RTL8185 at RealTek's site, and they appear complete. Moreover, it appears to work with fairly recent kernels (at least up through 2.6.22). Impressive. There may be hope for this thing yet...  Now to find out what this ROME thing is that replaces ipfilter... Schwab

great.. - can you also check if the RTL8185 driver supports the Access Point mode (or the managed mode) along with the Station modes?

January 5, 2008 7:06 PM

Nachi said: You can edit the user/Makefile to exclude dnrd just comment out the line 411

dir_y += dnrd-dnshijack

or you can even edit the dnrd-dnshijack to use the proxy but not with routerlogin.net. You can do many of the customization in the user/Makefile.

I'm trying to eliminate 'dnrd' as the source of trouble. Right now, it's accused by inference -- I've successfully sent pings through the router to the DNS server, but DNS requests get blocked. I've verified this by running 'trafshow' on the gateway, and no DNS requests are being passed on. 'dnrd' appears to be the most obvious culprit, since it's purpose in life is to mess with DNS requests.

I know I can chop 'dnrd' out of the build, but something tries to launch it during boot. That something appears to be 'boa'. It's not clear what 'boa' will do if 'dnrd' isn't present or fails to launch, and how that will affect the rest of the boot process.

In case it helps at all, my LAN topology looks something like this.

     DSL bridge
|
FreeBSD gateway
(firewall/NAT/DHCP)
|
Ethernet switch
| | | |
| PCs
|
WAP
|
+ Laptops
+ TiVo
\ Wii

By having a WAP there, I don't have the complication of managing sub-nets or having to propogate routes.  Call me lazy...

Schwab

Discussion:    Add a Comment | Back to Top | Comments 1-5 of 5 | Latest Comment

Add Your Reply

(will not be displayed)

Email me when comments are added to this thread

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

You can also log in using OpenID.

close this window
close this window