| View previous topic :: View next topic |
| Author |
Message |
PrimeSuspect EVDO Newbie
Joined: 03 May 2006 Posts: 8
|
Posted: Wed May 03, 2006 9:59 am Post subject: KR1 DHCP status bug |
|
|
I suppose this isn't very major but definitely a bug. Even when you have the DHCP server disabled if you check device info status it shows it as enabled. I'm running firmware version RK1002.
Also, what does the DNS relay option actually do? I have a very large LAN so I would prefer not to use DHCP so I can keep track of each of the hosts easier. All of the hosts have their DNS set to the IP of the KR1. I would suspect that DNS stop working when I disable the DNS relay option but everything continues to work just fine.
I saw in another thread where Mackieman stated it should not matter that the device does not drop the connection when your link is idle because it goes into a dormant state instead. If Verizon really doesn't care that someone is connected 24/7 as long as they aren't transfering too much data that is fine but I assume they probably monitor your time spent online too. Just seems like a simple enough feature to drop idle connections and reconnect as needed. Would love to hear other people's thoughts and opinions. |
|
| Back to top |
|
 |
Scott EVDO Junkie
Joined: 18 Jul 2005 Posts: 530 Location: Central Coast of California
|
Posted: Wed May 03, 2006 10:07 am Post subject: |
|
|
I see what you mean. I have a couple of KR1's and other EVDO routers on a local subnet and DHCP is turned off on all of them. Yet the 'Status' page indicates: DHCP Server: Enabled.
When the KR1 is set to DNS relay, it is supposed to proxy DNS requests from LAN clients out to the primary and secondary DNS servers on your EVDO connection provider's network (noted on the 'Status' page under DNS).
There is a good possibility they are caching lookups (fairly normal on little Linux-based routers). So even when it is 'off' there still may be a cache of recently resolved addresses (not to mention any local cache on the machine your accessing the Interenet on).
With DNS Relay off, try looking up a website URL that you have not visited. Is the name still resolved?
You can configure all your hosts with static IPs and manually set your own local DNS servers or the EVDO providers DNS servers for each host as well.
Last edited by Scott on Wed May 03, 2006 10:22 am; edited 2 times in total |
|
| Back to top |
|
 |
PrimeSuspect EVDO Newbie
Joined: 03 May 2006 Posts: 8
|
Posted: Wed May 03, 2006 10:18 am Post subject: |
|
|
| Yeah, I assume it is doing caching when it is enabled. One would think that with it disabled it wouldn't even be listening on port 53 though. Even with it disabled I'm able to lookup domains that I have never visited or checked before. Just like the DHCP status bug (enabled vs disabled) this isn't a big deal as I'll be running my own server that will provide DNS services for my home LAN but I just found it odd that you don't seem to be able to control it on the KR1. |
|
| Back to top |
|
 |
Scott EVDO Junkie
Joined: 18 Jul 2005 Posts: 530 Location: Central Coast of California
|
Posted: Wed May 03, 2006 10:25 am Post subject: |
|
|
| After making the config changes, what happens if you reboot the KR1, still able to resolve addresses? I wouldn't be surprised if the KR1 still resolved addresses, since it still needs to do this for itself (time server, dyndns, etc.). Still, odd that DNS is still proxied for LAN hosts. |
|
| Back to top |
|
 |
PrimeSuspect EVDO Newbie
Joined: 03 May 2006 Posts: 8
|
Posted: Wed May 03, 2006 11:22 am Post subject: |
|
|
I am not positive whether the KR1 was rebooted between these changes or not. I think it is very likely because I was playing with lots of different settings. Of course the KR1 itself is going to be able to resolve addresses. It has the DNS servers from the PPP connection (ie it is the client). Maybe it runs a local DNS daemon (bind, djbdns, whatever) and uses that which would explain why you can't disable the setting (unless you added iptables rules to block this traffic from the LAN). I consider this fairly minor just like the DHCP status issue but something that should be easily fixed by DLink/Kyocera.
I am still curious about the idle/dormant situation and whether it matters at all or if this should be added to the KR1 list of features (disconnect pppd when idle and reconnect when network traffic is detected). |
|
| Back to top |
|
 |
Mackieman EVDO Junkie
Joined: 31 Oct 2005 Posts: 485
|
Posted: Wed May 03, 2006 12:21 pm Post subject: |
|
|
| PrimeSuspect wrote: | | I am still curious about the idle/dormant situation and whether it matters at all or if this should be added to the KR1 list of features (disconnect pppd when idle and reconnect when network traffic is detected). |
This is already handled by the PC card and is a function of CDMA. The state to which you refer is called dormancy and is a key feature of EVDO. Because EVDO uses a separate data channel from the air link, you can leave the data channel open and close the air link when no data is being passed. When you need to transfer data again, the air link is established and away you go. In so doing you maintain a data connection but do not utilize network resources when you don't need them. |
|
| Back to top |
|
 |
PrimeSuspect EVDO Newbie
Joined: 03 May 2006 Posts: 8
|
Posted: Wed May 03, 2006 12:33 pm Post subject: |
|
|
| Awesome, that is exactly what I wanted to hear! Thanks for clearing it up. :) |
|
| Back to top |
|
 |
|