uh..oh.. I think I blew up my network..
Hello, last night was crazy for my bandwith. I had two torrents downloading (legal torrents, Slackware 10.2 actually), YaST running an update (from an FTP server), downloading patches for a game, and doing some other stuff. Suddenly the network just quit. The whole box just slowed down for a sec, all torrents went down to 0 B/S, and when I tried to ping google it just sat there. I was stumped. I went out into the other room and saw that the third light for my 2Wire router was out. Great, it kicked me off the network because I overloaded it. No big deal I thought, a simple reboot and I'll be in my suse system again with my network up. I rebooted and nothing happened, still no network, this puzzled me.. so then I ran dmesg to see if this was a hardware problem. What I found was a bit disturbing:
now picture about 50 of those, up and down. This was around midnight and I didn't feel like doing anything except sleeping, so I did that. When I got up I saw that my dad was on Firefox, so apparently it didn't effect his box as his network is still up (three pc's in the house are linked together with ethernet cables). My mom's computer still has a network up otherwise I wouldn't be able to type this. Now here's the kicker.. my mom and dad run Windows 2000 SP4 :?
eth0: link up
eth0: link down
Operating system error? Did I blow up my network by overloading it making it a hardware issue? Did my ISP get pissed and boot me out? I'm confused here..
EDIT: oh, and I'm almost ruling out a hardware issue as when I plug in my eth cable there are two blinking lights that come from my mobo, indicating a network connection has been made.