![]() |
Re: ping and tracert networking question
Your router has a DHCP server -- it acts as a DHCP client wrt the network and as a DHCP server to hand out local addresses. When you remove the router, your computer has a different DHCP server (the one on the network, not the one on the router). Welcome to the convoluted ways of networking, tip of the iceberg thing again!
I'd like to see the packet statistics from a pathping run, or at least know that you've looked at these and not seen anything amiss. Again, you want to pick an endpoint for this testing that is very far away (like chiefdelphi.com / google.com / etc.). Do you remember what DNS servers you were using before the trouble? You might want to try tracert and/or pingpath to these IP addresses... Very glad to hear that things have improved for you!!! |
Re: ping and tracert networking question
Quote:
|
Re: ping and tracert networking question
Ether,
It looks like your router is doing NAT. Here are two suggestions: 1 - Turn off NAT in the router and let your radio assign the IPs to local machines, or replace the router with a switch. 2 - Update the software in the router. -Hugh |
Re: ping and tracert networking question
Quote:
When the computer is connected the lease does expire. It could be they assigned an IP to his router's MAC but that seems unlikely. Even if they did that it should renew as usual to the same IP. Ether's information on page 3 shows that the ISP renews the DHCP every hour. Ether's router is providing NAT and DHCP and is renewing his internal DHCP every day. When his router times out it should renew every hour on the public interface. When his computer times out it should renew every day on the router's private interface. The question is: why does his router indicate that this obtained and renew timestamp are the same? His computer when connected in place of the router does not agree with that and shows 1 hour intervals. Updating the router firmware might correct any bugs the manufacturer found including those impacting DHCP. |
Re: ping and tracert networking question
Your router is almost certainly doing NAT. This makes multiple computers on your local LAN look like a single computer from the perspective of the network. You probably do not want to turn this off -- but when you directly connect the PC to the radio, you effectively do this. What is happening with DHCP is somewhat related. You need a single IP address on the network side, and your router gets this by having an internal DHCP client. The DHCP server on the network hands out the lease there, and whatever value the server choses is what the router gets. It automatically renews the lease, often at the halfway point in its lifetime. The router is getting the same sort of leases when it is connected as when you directly connect the PC to the network, but the displayed info may be rounded or some similar issue. It doesn't seem that you are seeing DHCP lease issues of any sort, although this is an interesting theory it doesn't fit the facts, particularly that things got better when you changed your DNS server config info. BTW, did you do this at the router?
Each computer on your LAN (including wireless) needs an IP address, and each has a built-in DHCP client. The router has a DHCP server, and you can tweak the configuration to hand out addresses in a different range, or to limit the number of addresses it will hand out. The router controls the DHCP lease lifetime for these leases. |
Re: ping and tracert networking question
1 Attachment(s)
Quote:
Quote:
Quote:
Quote:
2) I just now checked it again. I apparently have the latest version. Quote:
|
Re: ping and tracert networking question
I assume this <http://wiki.ubnt.com/AirOS_3.4> manual applies to your device?
Since you can't log in, I'm not sure how you can tell for sure. Your ISP may have updated the firmware to something newer, if this device supports it. However, the answer most likely does not change -- yes, this device can act as a layer 2 bridge. For reference, here is the info for your router: <http://documentation.netgear.com/wpn...FullManual.pdf>. Quote:
The data from pingpath should make it possible to work out where along the way the over-the-air hops are happening. I'm hoping to find some hops where there are some drops as one clue. Another clue is just the IP address info and where in the list of hops each address appears. At any rate, this is some hard data that would be very helpful to have. |
Re: ping and tracert networking question
Using SNMP to get some info from your radio isn't a bad idea, but it depends on this being enabled at the radio and having a default (or known) security setup. One tool for looking at SNMP info is here: <http://en.wikipedia.org/wiki/Net-SNMP>. Basically, not having info from the radio opens a major gap in what we can observe. FWIW, it is pretty common to have read-only SNMP access on by default, for purposes of network management. You would use the IP address where you saw the AirOS splash screen with the SNMP tool to obtain some useful info, hopefully.
|
Re: ping and tracert networking question
Quote:
|
| All times are GMT -5. The time now is 23:29. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi