Debian Configuration :: Squeeze Installed - Slow Responses To Ping
Feb 15, 2011
Just installed squeeze and noticing slow responses to ping. Ping with -n is fine, and as expected. Ping without -n is very slow to appear on the screen.
ben@WOPR:~$ ping google.com
PING google.com (74.125.230.114) 56(84) bytes of data.
64 bytes from 74.125.230.114: icmp_req=1 ttl=54 time=26.2 ms
64 bytes from 74.125.230.114: icmp_req=2 ttl=54 time=25.9 ms
64 bytes from 74.125.230.114: icmp_req=3 ttl=54 time=29.3 ms
64 bytes from 74.125.230.114: icmp_req=4 ttl=54 time=25.5 ms
^C64 bytes from 74.125.230.114: icmp_req=5 ttl=54 time=25.8 ms
--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 20199ms
rtt min/avg/max/mdev = 25.514/26.569/29.308/1.399 ms
ben@WOPR:~$ ping -n google.com
PING google.com (74.125.230.115) 56(84) bytes of data.
64 bytes from 74.125.230.115: icmp_req=1 ttl=54 time=25.6 ms
64 bytes from 74.125.230.115: icmp_req=2 ttl=54 time=26.0 ms
64 bytes from 74.125.230.115: icmp_req=3 ttl=54 time=26.8 ms
64 bytes from 74.125.230.115: icmp_req=4 ttl=53 time=21.5 ms
^C
--- google.com ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4006ms
rtt min/avg/max/mdev = 21.540/25.042/26.859/2.064 ms
I've tried disabling ip6, disabling avahi and adding options single-request to my /etc/resolv.conf - problem remains. If it helps when installing Squeeze was prompted to install firmware-realtek, which I didn't have. So downloaded onto usb from another machine installed once setup was complete.
I have a mysql server in guest domU on debian squeeze. when i create test table and do INSERT INTO test (name, value) VALUES(RAND(), RAND()); Query OK, 1 row affected (0.28 sec)
At other physical server with same configuration Query OK, 1 row affected (0.00 sec)
I try this several time but on physical server max value never get over 0.05sec and on VM lowest value was 0.13sec.
Another tests:
On physical server:
OLTP test statistics:
Threads fairness:
on VM:
OLTP test statistics:
Threads fairness:
performance of disk write speed on VM is much better then on physical server .
I have Acer Aspire 4740 laptop with Atheros ar928x wireless. My wireless is very slow, unstable. Wireless card still works well and fast in Windows (dual booting). After searching I see that there are many Ubuntu users have the same problem in Ubuntu 11.04 with this card.
I installed Firestarter firewall on debian Squeeze.Now i note there is a gui available in System->Administration which apparently does not need to be running all the time - its not set up to start on boot.When I boot I notice the boot message has a line saying "Starting Firestarter firewall .... failed"When I am logged in and type "/etc/init.d/firestarter status" as the Firestarter FAQs say, I get"Firestarter is running... ... (warning)"I can run the gui manually and still same message.
Hi,I'm using a Dell Lattitude D620 laptop. I just installed the latest kernel 2.6.38 in my Squeeze amd64 :
Output of uname -r 2.6.38-bpo.2-amd64
Now I'm running on new kernel,everything seems fine except my wifi ( now I'm connected through ethernet ). Before I do the process with the guide in http://wiki.debian.org/wl to activate my wifi,I'd like to ask for some advice here,is this latest kernel support my wifi card? If yes,how to activate it?
Host machine is a "2.6.32-24-generic-pae #38-Ubuntu" and VMware Workstation version is 7.1.2 build-301548.In addition to those three IP addresses(192.168.1.254/24, 192.168.1.68/24 and 192.168.1.221/24) seen on a drawing, there are four identical virtual machines inside the 192.168.1.68/24 machine. Virtual machines are named Olive0-3. Olive0 has IP address 192.168.1.100, Olive1 has 192.168.1.101, Olive2 has 192.168.1.102 and Olive3 has 192.168.1.103.
I have a debian server installed with a static ip. Now i am able to ping my ip, but when i try to configure a domain name with the nameserver as my ip, i am not able to ping the domain name
I have a pretty quick machine, quad core 2.66GHz duo processor, nice ASUS motherboard, high speed memory bus and so on. Basically, this is not a machine that's getting "maxed out" by playing some music.Load averages for the 4 processors according to htop are 1.48, 1.25, 0.85. Looking at the System Monitor CPU history I am seeing an average of perhaps 25% load.
However, when I am in a shell, I am getting a second or longer waits between key presses at times.My only guess as to why is that may be is that the streaming audio is on some very high priority so everything else gets put on the back burner. In any case, does anyone have any experience with this and a possible tweak that would give everything else a "fair go" so things didn't seem so unresponsive?
Several days ago responses to many, but not all, of my internet requests slowed from long to never.I'm on Verizon FIOS; running Firefox on a Debian Lenny system with 6GB or RAM and 500GB HD with 32GB cache.
internettrafficreport.com shows index of 84 for North America. I've pinged a few sites -- see returns from 16ms to 91ms.I've also rebooted my Verizon DSL router.
I have a home network consisting of 1 Linux box running Fedora 13, a laptop running Windows XP, and an HP Officejet Pro L7780. With the Fedora 13 box I have Firefox 3.6.4. I have noticed in the last couple of days a very sluggish response seemingly one site, amazon.com. I'll connect to the site but Firefox remains loading the page and parts of it will be missing. If I search for a particular item it takes forever to display parts of the newly requested page. I have hit stop and then refresh and sometimes the page will then come up although it's never 100%. Eventually I'll loose my router (which by the way is a Linksys BEFSR8.1 v3.01), in that if I ping it I'll get the error that it is unreachable. The laptop also looses access to the router. I'll then reset it (unplug/plug) and it'll come back up ok until I go back to Amazon and start searching again.
My question(s) are: Can a router go bad and just show up bad with one site initially? In other words is the router slowly dying?Can a problem with a site affect the router this way?I have also changed my namserver settings in /etc/resolv.config and on the router with no real change in symptoms. It's always Amazon and I don't seem to have issues with any other sites that I visit. Any clues?
We have an environment where couple of webservers are being active behind the loadbalancer, the webpage is getting loaded extremely slow if we restart the apache on those boxes its responding very fine. So currently we are restarting the apache service daily basis, i have attached the config with this thread could anyone suggest how to fine tune apache so it works fine without restarting it daily?
I have a NAS which I've re-installed with DEBAIN. Mostly its all working great but when I tell it to ping a NetBIOS name it takes 10 seconds per attempt rather than 1. Despite this it actually resolves the NetBIOS names very quickly (the first line from the ping including the IP address appears almost instantly) it just sits there for 10 secs every ping.
# ping -c3 qnap PING qnap (192.168.1.100) 56(84) bytes of data. 64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=0.175 ms 64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=0.167 ms 64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=0.158 ms
--- qnap ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 20036ms rtt min/avg/max/mdev = 0.158/0.166/0.175/0.016 ms # # ping -c 3 [URL] PING www.l.google.com (173.194.36.104) 56(84) bytes of data. 64 bytes from lhr14s01-in-f104.1e100.net (173.194.36.104): icmp_seq=1 ttl=49 time=40.3 ms 64 bytes from lhr14s01-in-f104.1e100.net (173.194.36.104): icmp_seq=2 ttl=49 time=25.4 ms 64 bytes from lhr14s01-in-f104.1e100.net (173.194.36.104): icmp_seq=3 ttl=49 time=25.7 ms --- www.l.google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2022ms rtt min/avg/max/mdev = 25.491/30.518/40.313/6.926 ms
I'm really struggling to track down what may be causing this as it is strictly when resolving NetBIOS names yet it finds the IP immediately.
Back in April I set up a Ubuntu DHCP server and a multiple VLAN network [URL] to migrate our various servers, workstations, etc off the 192.168.1.1 /24 network that everything was on because we where running out of address space. I built out the new network and everything worked great except our AD server would never get an IP address from the DHCP server (static reservation) and even if I set the IP statically on the AD server it couldn't ping the gateway and noone could log in. After several attempts to resolve this, including bringing in outside help, we where never able to figure out what the problem was.
Now 6 months later I have time to revisit the issue without effecting the live network. I used Acronis and imaged the AD server last Friday, cloned it on to another box with the same hardware, and put it up on the new network that's been sitting unused for the last 6 months. Today when I statically set the IP on the AD server (which is what I want) it connects and I can ping it's gateway 192.168.1.1 and all the way across vlans to a test sales agent workstation at 192.168.8.xxx on vlan 800 but only if I statically assign the agents station an IP address. When I try to get an IP address via DHCP it fails as destination unreachable. Nothing has changed in the last 6 months on the DHCP server but now it for some reason can't ping its default gateway 192.168.1.1. All of the config files are the same as they where left from the post linked above aside from the vlan id's used where changed from 1's to 100's (i.e. vlan 3 is now vlan 300) /etc/network/interfaces
Code:
auto lo iface lo inet loopback auto vlan100 iface vlan100 inet static
[code]....
why it can't reach the gateway, when I do a tcpdump I can see the DHCP requests come in on eth0 but the server never responds and I'm pretty sure its because it isn't "seeing" them since it thinks there isn't a network connection but I don't know how to trouble shoot to find out where the problem lies.
I just installed my first EVER bind DNS server. I am running bind9 on Ubuntu 10.04. Everything seems to be working great except one thing: If I ping a host that I have set up in bind by its HOSTNAME the pings take 5-6 seconds to reply/print to the screen between each echo response. If I ping by the host's IP address, they echo back very quickly.
I have read that IPv6 can cause this, but I have disabled it in /etc/sysctl.conf and the problem still exists.
I know everyone says this can't be a DNS issue, but this never was an issue with dnsmasq (which i was using prior), and it doesn't make sense that the ping are ONLY slow when pinging by hostname and not IP.
Configs below:
Ping by hostname - there is a 5-6 second delay between each one of the responses:
Code:
Ping by IP - the responses come VERY quickly one after the other:
Can't understand what's going on... Running 'apt-get update' I see that diffs are downloading with a normal speed (11.3 Mbyte by 49 seconds = ~ 227 Kbyte/sec - it's OK, my 'up' limit is 384 Kbyte/sec). But - running 'apt-get dist-upgrade' I see that packages are downloading w/ around 4000 byte/sec. WTF? What's the difference between downloading packages' diffs and packages themselves?
I've changed 6 mirrors - from oficcial (ftp.us.debian.org) to local (ftp.mgts.by). I've tried netselect-apt - no result. Still normall speed on 'apt-get update' and terrifying speed on 'apt-get dist-upgrade'.
My several-weeks-ago-installed squeeze KDE is very slow when browsing the files and directories, and also opening applications as compared to my WinXP.
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
I am now working with squeeze, and my page load time on my Vista laptop, which is working off of a wireless connection, is much faster than my linux desktop, which is a direct connection.
While Blender 2.5 may be stable, the Python API is not. According to the Blender website... Note: The Blender Python API has areas which are still in development. The following areas are subject to change. -operator behavior, names and arguments -mesh creation and editing functions.
I recently just installed Squeeze on an ia64 system and was having some troubles with running VNC.I get the following error, more specifically for some reason I get a malloc - memory corruption error:
Xtightvnc(9165): unaligned access to 0x60000000001ea06c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea074, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea07c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea084, ip=0x4000000000268280
[code]...
After display all the code above, it just stops. The port 5901 is still closed - if it runs properly, would it open automatically?Is there something that is incompatible? Or am I missing some system configuration component?
i am running debian testing and the last few days i was trying to ssh to another pc on my network and i was getting an error like there was no machine with that ip! then i tried pinging to it with no luck! ARP was the only tool that returned the MAC address of the machine and that is strange i think. i realised then that i could only ping the gateway and localhost (127.0.0.1 not my ip). after editing my /etc/hosts, i could ping my ip as well. what is so wrong? here are some useful things:
my new /etc/hosts: jack@debian:~$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 debian.local debian
I have one headless squeeze and two notebooks (one squeeze, one lenny).
When I have X (on headless squeeze) on lenny notebook, it is unacceptably slow. Something like it takes 3-10 seconds to redraw window (acroread, iceweasel, possibly xterm.)
It is not so slow when I use squeeze notebook. Yesterday, I upgraded lenny one to squeeze. Then, it is not slow any more!
I recently did a clean install of Debian 5, and a backup program called BackupPC. Both machines are on a small local network served by a router. Both machines have statically mapped IP addresses, done by the router via matching MAC addresses in a table of corresponding IP addresses (192.168.0.2 (HP-PC-XP), 192.168.0.3 (Debian). I configured Backup PC correctly (I think)...Upon running Backuppc, the first thing it tries to do when its time to run a backup is to ping the machine to be backed up. The name of the PC is stored in a backup pc config file. (I believe BackupPC does a DHCP request with the machine name to get the ip address, but not sure). Running the backup results in BackupPC tells me that it can't ping my xp machine. If I open up a terminal window in debian, i can successfully ping my xp machine when i use the ip address. 92.160.0.2 If I ping using the host name of the xp machine (e.g. HP-PC_XP), the ping command displays some ip address i've never seen...something like 63.123.155.104....how is it getting that and how can it be corrected?
I recall that nslookup looks at the local hosts file first to resolve the name....i look in my hosts file and found no such address (only contained localhost)....now what?
I've been using Debian for about 6-7 months now. I've had a bit of a major networking problem for the past 4 months or so that I've been trying to fix - specifically, it started when I upgraded to Jessie. I can connect to wifi just fine, and sometimes I can even use the internet for brief periods of time (exceedingly rarely). Then... nothing. No network access, period. I can't ping any outside servers, I can't ping other computers on my network, and I can't even ping my router. Pages I try to load just stay "connecting" for all eternity, network printing fails, and so on.
So after four months of searching online (I've read through way more wireless documentation than I care to say), I finally gave up and admitted that maybe I screwed something up during upgrade to Jessie (as a matter of fact, I did, I had to do the upgrade in two increments [somehow] because my root partition was too tiny by mistake) and I did a clean install. Since I had /home on a separate partition, I was able to keep all my user files, but all settings regarding networking were wiped. So after installing firmware-iwlwifi so I can use my wireless card, I tried connecting to wireless! Success! Then I tried connecting to the internet... success! Briefly. The next morning I tried using the internet again, and it failed in exactly the same pattern as before.
I don't know much about what's going on here, but here's what I do have available:
I do have to use firmware-iwlwifi, which I installed by doing apt-get install firmware-iwlwifi. I don't think it's an issue with the wireless card itself (hardware-wise), the laptop dual-boots Windows 7 (that I never use anymore), and Windows 7 is able to connect to the internet just fine. Connecting directly to my router by ethernet cable works fine, I have perfect internet/network access then.
I can confirm that my laptop is receiving an IP address and that it is using ARP correctly to get the MAC address of my router (I confirmed this by doing the arp command, it has the MAC address correct, I checked from another computer with my router's config page) All other computers on my network work perfectly with my router. To confirm the router/its configuration isn't at fault, I did a full factory reset of the router, but to no avail.
Out of curiosity I tried installing Wireshark (using an ethernet cable to download it) to monitor what happens when I try to access a webpage. I'm no expert on networking, but I noticed something out place when I compare a capture from the affected computer to a capture from one operating normally - there are a lot of STP packets showing up. I did some checking around, it looks like STP is involved in bridging and more complex networking setups (involving switches, for example)... but it shouldn't be found on a home network, especially where there's no bridging whatsoever. These STP packets don't show up on packet captures done from any other computer. I've attached a packet capture from the affected computer here, since the forums won't let me attach a .pcapng file.
Here's the output from a few commands I ran during past troubleshooting sessions:
Code: Select allsudo ifconfig eth0   Link encap:Ethernet HWaddr e0:db:55:b5:fe:06      UP BROADCAST MULTICAST MTU:1500 Metric:1      RX packets:12455 errors:0 dropped:0 overruns:0 frame:0      TX packets:7781 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:1000
I would like to ask something. Today my network Internet access suddenly slowed down, after inspecting the problem the hard way we disconnected one of our servers(ip=190, debian squeeze) from network and the network was alright again. When we plugged it back in, following symptoms were observed: computer 190 pinged gateway app. each 6th time. gateway(debian lenny) pinged computer 190 app each 6th time whole network Internet access was slowed down, local network functioned just fine
While pinging themselves, i ran iptraf on icmp packets on gateway and I saw what i thought was ping attack, lots of echo request coming from external address to computer 190. Blocking that address in iptables didn't help but restarting the gateway did, network Internet conenction is at full speed and gateway and computer 190 ping just fine.
My question is, what steps should I undertake in similar case (it's second time in 2 months) - to debug similar problems. Is it even possible for ping DOS to this kind of damage?
I have installed Debian Squeeze 6.0.1a i386 via download DVD image from [URL]. Eventhough I specifically selected "Desktop" from installation menu, only basic system is installed.
I have only 1st DVD, which I understand is sufficient for desktop setup. if I have missed any of the steps or any saperate installation is required.
how to install Dropbox for Debian Squeeze from source.Please read everything before you begin. I prepared it as I installed Dropbox for my own system. Please Note: I use sudo, you may have to use root or 'su' from the command line. If you don't know the difference between sudo and su, then you shouldn't try this until you know. At the time I did this, the lastest dropbox version was 0.6.7.
I have a very strange problem.ometimes, yes sometimes not all the time, I get a Destination Host Unreachable when I ping a computer on my network. If I switch to root using su I can ping that same computer. Here is a screen shot:
joseph@laptop:~$ ping 192.168.1.14 PING 192.168.1.14 (192.168.1.14) 56(84) bytes of data. From 192.168.1.9 icmp_seq=2 Destination Host Unreachable
When I activate Tor in Iceweasel, it forbids me access to the internet completely. Even attempting Google results in "Iceweasel is configured to use proxy server that is refusing connection".
I have seen this in Lenny, too - it was caused by activating Tor without having installed privoxy. I installed privoxy and everything was okay. In Squeeze, Tor is using polipo. Polipo is installed and running. I have not played with settings of polipo or Tor, the configuration is the same as it was after installation.
What can be wrong? I am a rather an user than a networking guru. I am connected to internet by means of DHCP, no local lans, no special routings, no additional proxies. I have already tired to reinstall polipo.
