This site is now 100% read-only, and retired.

XML logo

Yeah - fresh install debian etch lenny!
Posted by Grimnar on Sun 6 May 2007 at 05:26
Tags: none.
So after a few weeks with painfully slow ftp/samba speeds I finally gave up. I downloaded debian netinst iso and booted away. Erased /dev/hda1 to really get rid of the ooooold system. Was very satisfied when I discovered all my other disks and files where untouched. And this time my third netcard was discovered during the install and I figured I might as well could try that one. So I configured that eth2 to 192.168.0.1 NAT and it worked like a charm. For about 3 hours. God damn, I'm still having problems with the speeds!! What the hell can this be? I been googling the last 4 hours and I'm soon going to break something! Now, some facts before my gf wakes up (It's 06:18 in the moring here)
boot up script.
ifconfig eth2 192.168.0.1
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -F
iptables -F -t nat
iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o eth0 -j MASQUERADE
mii-tool -F 100baseTx-FD eth2                                         

uname -a
Linux gwdebian 2.6.18-4-486 #1 Mon Mar 26 16:39:10 UTC 2007 i686 GNU/Linux
ifconfig eth2
gwdebian:/etc/proftpd# ifconfig eth2
eth2      Link encap:Ethernet  HWaddr 00:04:61:61:2A:35  
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::204:61ff:fe61:2a35/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2429482 errors:0 dropped:27 overruns:0 frame:7665
          TX packets:1863736 errors:1 dropped:0 overruns:1 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:227068955 (216.5 MiB)  TX bytes:2527109377 (2.3 GiB)
          Interrupt:201 Base address:0xec00
Top
    1 root      15   0  1940  644  548 S  0.0  0.1   0:01.46 init                                                                                            
    2 root      34  19     0    0    0 S  0.0  0.0   0:00.00 ksoftirqd/0                                                                                     
    3 root      10  -5     0    0    0 S  0.0  0.0   0:03.03 events/0                                                                                        
    4 root      19  -5     0    0    0 S  0.0  0.0   0:00.00 khelper                                                                                         
    5 root      10  -5     0    0    0 S  0.0  0.0   0:00.00 kthread                                                                                         
    8 root      10  -5     0    0    0 S  0.0  0.0   0:00.03 kblockd/0                                                                                       
    9 root      20  -5     0    0    0 S  0.0  0.0   0:00.00 kacpid                                                                                          
   93 root      10  -5     0    0    0 S  0.0  0.0   0:00.00 kseriod                                                                                         
  135 root      15   0     0    0    0 S  0.0  0.0   0:00.00 pdflush 
Firewall: None; Other limiters: none; This is really a fresh install. Only Gnome 2.18 installed as the culprit, but all gnome* as been stopped. No dns-issues in proftpd.conf, and the "speed hack" in samba.conf is in use. Passive/active transfers both been tried out in my ftp client. Still no dice. Please help me solve this. Someone. (formated in html text, preview showed ok format)

 

Comments on this Entry

Re: Yeah - fresh install debian etch lenny!
Posted by Grimnar (85.221.xx.xx) on Sun 6 May 2007 at 15:08
[ View Weblogs ]
Google have me a hint on this, install wireshark. So I did and understood nothing of course. But I'm not giving up on this. So right now I'm creating a swap-file(?) since I never had that in the past. And yeah, I just checked all my cables today. Both ethernet and wireless. From windows and mac. Still same very slow 30kbs. Oh well.

[ Parent ]

Re: Yeah - fresh install debian etch lenny!
Posted by mwr (24.158.xx.xx) on Sun 6 May 2007 at 16:42
[ View Weblogs ]

The first thing I'd check (and maybe you have) is swapping out the cabling and the NICs. Generally, my experience has been that any time you have to force a NIC to a particular speed and duplex, that something's wrong in the physical layer, and fixing that will let it autonegotiate to the higher speed you want. If the physical layer is good enough to autonegotiate, it doesn't care if you force it. If the laws of physics dictate that the physical environment isn't good enough to autonegotiate, then telling your cards to insist on the higher speeds would lead to lost/dropped packets, retransmissions, etc.

[ Parent ]

Re: Yeah - fresh install debian etch lenny!
Posted by Anonymous (85.221.xx.xx) on Sun 6 May 2007 at 21:31
Great. I swapped the cabling on the computer and everything seems to be working.
So far.
The network got a bit f***ed up for a moment there but I think I got that right now.
The only problem so far is ftp clients cannot "download" folders that are been symlinks. Very strange.

Second, Swap space. Problem having / and /swap on the same disk? should it on a different disk? Perhaps on a raided disk?


[ Parent ]

Re: Yeah - fresh install debian etch lenny!
Posted by mwr (24.158.xx.xx) on Mon 7 May 2007 at 02:49
[ View Weblogs ]
In general, shouldn't matter. My old file server (K6/2-550, IDE disks) can deliver 50-55% utilization of the 10/100 network here, when downloading a single large file over Samba. Generally, until you get to gigabit, your network link should be the bottleneck. And at gigabit, a regular 32-bit PCI bus could be the next bottleneck.

[ Parent ]

Re: Yeah - fresh install debian etch lenny!
Posted by mwr (24.158.xx.xx) on Mon 7 May 2007 at 03:27
[ View Weblogs ]
And as another data point: same file, via Apache -- pretty solid 35% utilization (around 4000 kbps). Both tests to the same WinXP client.

[ Parent ]

Re: Yeah - fresh install debian etch lenny!
Posted by Grimnar (85.221.xx.xx) on Mon 7 May 2007 at 14:57
[ View Weblogs ]
Thats pretty poor? I have like 90-95% utilization now. Both cable and wired. Osx and winxp. Except when it drops to like 30 Kbs. That really sucks.

[ Parent ]

Re: Yeah - fresh install debian etch lenny!
Posted by Anonymous (195.35.xx.xx) on Fri 11 May 2007 at 18:29
I had the same problems with my network, thought it was samba too. However after using iperf -s on the server along with iperf -c [ip of server] on a client i discovered it was the poor performance of the switch.

After i installed my new switch i happely run any protocol with 99,8% network performance, at least if i dont count the diskrates along.

iperf is a great tool along with tcpdump to test your physical net. Don't blame it per default on samba. But samba is the first protocol (smb) that will run into problems with poor networks.

[ Parent ]