-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind- sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Monday, January 24, 2011 11:20 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Network troubleshooting
Hi,
If you are talking about buying a new router I have always had good luck with the Draytek products. They have enterprise features and although slightly more expensive than the home models are worth the money.
I had a Cisco wireless access point recently, and got double the range when I converted to a Draytek access point. I used their routers exclusively until a few years ago when I changed to Cisco for learning the Cisco command line, although Cisco are good they don't have nearly the bang for the buck that the Draytek stuff has imho.
Thanks. Andrew.
________________________________________ From: blind-sysadmins-bounces@lists.hodgsonfamily.org [blind-sysadmins- bounces@lists.hodgsonfamily.org] on behalf of Scott Granados [scott@granados-llc.net] Sent: 23 January 2011 22:48 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Network troubleshooting
I'm very certain your Netgear doesn't have anywhere near the forwarding rate you need to get 20+ megabits.
I had to go with a DLink extreme to get the most out of my 100 megabit cable here.
You also might think about buying some used enterprise gear on ebay both to learn and for better performance.
If you want to keep it inexpensive I'v ehad good luck with the DLink DIR-655.
On Jan 23, 2011, at 6:48 AM, Barry Toner wrote:
Hi,
I've ran the test directly connected to the cable modem Ping -n 1000 -1500 192.168.100.1 This is my modems Gateway address. Sent 1000, Recieved, 1000 Min, 2ms, max, 5ms, avg, 2ms.
I then pingged the router wired into it, Sent, 1000, Recieved,1000 Min, 0ms, max, 40ms, avg, 1ms
I thought I'd try some downloads where I know I get speeds in the 20MB range. Connected to modem wired, 2.3MB/s. WIFI To Router, 300K. Connected to Router Wired, 500K. I ran these download tests a few times. New router?
Cheers, Barry.
Cheers, Barry.
-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind- sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Sunday, January 23, 2011 11:05 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Network troubleshooting
Hi,
Something is definitely up there. Here is a ping session using
same command that I ran from a netbook on the other side of the house from the wireless point:
Ping statistics for 192.168.1.1: Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 0ms
If this was through wireless, is the AP provided on the router itself? Have you done a similar test connecting to the cable modem
Thanks. Andrew.
-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org
sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner Sent: 23 January 2011 00:17 To: 'Blind sysadmins list' Subject: Re: [Blind-sysadmins] Network troubleshooting
Hi Sean and all.
Firstly Sean thank you very much for your detailed steps and explainations. I will sit down and go through this over a morning or so to do it justice. In the mean time I've pingged my router using, Ping -n 1000 RouterIP The results were Sent 1000, Recieved 974. Min - 1ms, Max 3215ms, Avg - 92ms.
I then pingged within 30minutes after the first test using the full packet size -l 1500 Ping -n 1000 -l 1500 RouterAddress The results were Sent 1000, Recieved 1000 Min 2ms, max 2338ms, avg 11ms BTW. I tested this ping over WIFI in another part of the house from the AP. I will test it having my Laptop hardwired into the Router and report back.
Does this tell me without going any further that the Router might be the issue here? I've new cables in the post... Should I possibly be thinking about adding a new router to this? The strange thing is after calling my ISP last week the net was fine for about 4 days then fell off again. This is why I've been so feerce in my convictions it wasn't my hardware.
Regards, Barry.
-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind- sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Sean Murphy Sent: Saturday, January 22, 2011 1:37 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Network troubleshooting
Hi
You need to isolate where the packet loss is occurring. It appears you have done some work already. but I shall go over it again. Please read the hwhole mail before doing anything. I work in the networking industry, so I will go into some depth.
Caveats before we start.
some providers and network devices do not honour ICMP echo's and drop them to prevent DDOS attacks. therefore, you will sometimes not get the ICMP reply. The other thing is there is many different ways of configuring a PPP (Point to Point Protocol) connection by your ISP and the next hop that your router see's might go through other routers or networking devices before hand. But you cannot see this due to
[mailto:blind- the
protocols they are using. Such as LAC, DVPN, etc.
Lets discuss basic networking troubleshooting and this will assist.
the Ping command works at the layer 3 level. It does not test TcP level. This can be done easily enough but I will explain later.
firstly, you need to check your local network to varify it is all working with no packet loss. I shall not talk about Wireless, since there are to many factors that can cause packet loss. If the wired (Ehternet cat 5/6) is working fine. Then you can assume your local router/switch is fine.
1. Under windows. Use the ping command form the dos prompt.
ping -n 1000 -l 1500 <ip address>
The above is sending a full packet through your network. If you get no packet loss, then there are no MTU issues.Try different length sizes to see if you get any packet loss. This is important to test your router. the IP address should be your local IP addresses for the different machines. Make sure your local machines except ICMP echo and sends replies in
Firewall. You might want to keep it simple and shut down the firewall on
PC's until you are complete with the tests.
If this all works fine after testing different packet sizes. Then you can say your local network is fine.
2. Test your Next hop as have been suggested before.
A) If your setup is a dedicated cable modem and then the modem plugs into the router. The modem is in Bridge mode which means you will receive the IP address sent by your provider after the modem has performed the necessary training to learn the different frequencys to send/receive data. There is 2 areas where you could have
The
cable from your router to the Cable Modem. The connection from
cable modem to the ISP. Try the below suggestions.
A) Connect your PC directly to the Cable modem Ethernet port. B) Ping the provided IP address from your provider with the same command previously provided. If you get drops. Then it is either the ISP Cable plant or the modem. C) Remove the Coax cable from the cable modem. Make sure the modem is turned off first. D). turn the modem back on. You now should get a private IP address on your PC. Ping this address using the above example. If this all passes. Then you have narrowed down the issue. E). Before re-connecting the Coax. Earth it by gently touching
CoAx inner pin against something that is metal to ground it. Ensure the modem is turned off. Then Plug it back in. When screwing in
Hi Barry, I'll second what Andrew says about Draytek routers. Andrew advised me to use them yonks ago, and we've never looked back. Unfortunately, when we moved from a BT line to Virgin Cable at home, they supplied a Netgear, which has already been replaced once in the last year. One of these days I'll get down to finding out if it can be replaced with a Draytek, my concern being that the Netgear is a unit which appears to be specifically modified for Virgin customers. However the office Draytek just seems to keep going and going 24/365. George. -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner Sent: 24 January 2011 11:29 To: 'Blind sysadmins list' Subject: Re: [Blind-sysadmins] Network troubleshooting Hi, The thing I can't shake off is that this router served me well with 20MB for the past two years. So although it may be on it's way out it was certainly capable of the speeds delivered by my ISP. I cant' seem to find a Diogs page in the config.. and I must have hit every link at least 3 times. Draytek is a name I've heard over and over in the past year. I suppose if I'm going to spend £70 on a Netgear I might as well pay an extra £30 or so and get a Draytek. Finally, giving the information thus far does it look like the Routers needing replaced? Cheers all for your help. This has hopefully provided a useful thread for everyone. Regards, Barry. the directly? the the problems. the the the
CoAx cable, ensure you don't tighten it to much because you might damage the cable. It should be able to be unscrewed by your hand. F) Power up the modem again. Ensure you get the IP address that your provided provides, not the private address I mention before. Perform another ping to your providers gateway address.
I for got to mention how you find out the gateway address. When you are connected to the ISP. Drop to the DOS (command prompt). Enter in ipconfig. Look for your Ethernet port that your cable modem is connected too. You will see "gateway". this is the address you want to ping. If you don't get that, then you can try traceroute. But this will only give you the first router that replies. This doesn't mean it is the first hop.
B) If you have a combo Cable Modem/router. There might be a ping test within the router. Check this out. If it doesn't then you can only perform a ping to the Public IP address that is shown on the router.
If you have a specific site that you see more drops than others. Then perform a traceroute to that IP address. Take note of all IP addressses. Then ping each address that is shown as previously mention. this will isolate which IP address the packet drops start. But will not resolve the issue because now it is out of your hand. You can mention it to your ISP. But if it isn't in their network, they will more than likely not do anything.
Anything else beyond the above basic test require packet captures by using Tshark which is within Wireshark. This is not for the lite hearted.
Sean
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins