wget --limit-rate 90k
This seemed to work. Verizon just doubled my DSL speed and I guess my old pc couldn't take it.
]]>(or run "ps axjf" - it will display in treemode the processes - check the parrent of the dhcpcd, and the status of pacman).
My ideas...
]]>/usr/sbin/dhcpcd -t 30 -h LinuxHippy eth0
I found before in Slackware that if I execute dhcpcd eth0 that my router will reset trying to find an IP. Pacman started dhcpcd this time (not me) or something else.
Stepping down my transfer rate sounds good-I'll look into that.
]]>Probably a network thing-not sure what to do.
]]>Maybe it's pacman?
I highly doubt it... pacman is working 100% fine on hundreds of computers, wireless and wired...
Also, there is no way you can tell a computer "hey, boot joe's PC off the network" - are you sending floods of broadcast packets? I'm 99% sure this has to do with networking... what wireless driver are you using?
you also said that you had already uncommented the wget line... have you tried both with and without the wget line? and it does the same thing?
hmmmm the only difference between my "test" and what pacman does is that it hits multiple servers in sequence... maybe try testing that way?
]]>Maybe it's pacman?
]]>try downloading (from the terminal) something .... let's say:
wget ftp://ftp.archlinux.org/other/pacman/pacman-2.9.5.tar.gz
see if that does the same thing... then try
snarf ftp://ftp.archlinux.org/other/pacman/pacman-2.9.5.tar.gz
and check that
it sounds like a network issue (e.g. not a software issue)
if both of those work, try uncommenting the wget line in pacman.conf (to use wget to download things)
]]>