> -----Original Message----- > From: Jeff [mailto:[EMAIL PROTECTED] > Sent: Monday, November 12, 2001 8:37 AM > To: Debian List > Subject: Re: Frustration (cablemodem woes) > > > Michael Patterson, 2001-Nov-11 16:33 -0700: > > > > > When I hook up my linux box to it, I get terrible performance, and > > > > > eventually my connection to the cablemodem fails. I can get > > > the connection > > > > > back by powercycling the cablemodem. I'm using dhcp-client. > > > > Unfortunately, I'm having significant performance issues, and I > don't have > > the knowledge to know how to start debugging this. Web searches haven't > > turned up anything, and I've made a couple pleas on the topic > here with no > > luck. > > Mike, > > Better characterize your performance issue please. > > Does it take a long time to initially make the connection to a > web site and then after it finally connects the web page popps up > quickly?
The web page takes a noticable, but not prohibitively long time to connect. it appears that the site "www.thex-files" (to name a specific page) will load part of the flash presentation, then pause for a long period of time before continuing. > Do downloads go really slow? Do uploads go really slow? Downloads go extremely slow. The "game of the hour" here is Dark Age of Camelot, and I've been using the install of this program as a method of testing download speeds. (it gives a download rate while updating over the net) A win98 machine hooked directly to the cablemodem gets 60k/sec download. A win98 machine masqueraded through my debian box on wantweb gets 10k/sec. A win98 masqueraded through my debian box on the cablemodem gets 0.3k/sec before stopping entirely. The fact that DaoC stops downloading entirely after a short period of time is puzzling. It worked fine with masquerading through wantweb. As a second test to verify, I told Morpheus to download a number of files at once. It seems to be doing significantly better. The speed of the files being downloaded adds up to 12k/sec. > Does network traffic simply stop altogether for a period of time? Yes. Eventually, the traffic stops completely, requiring a reboot of the cable modem for it to start up again. > Add anything else you can think of. I had someone come out from the cable company to check my setup. They verified that the cablemodem was working fine (which I also verified by hookng up a win98 box directly to it). The connection has stoped three times since I started this email. In all cases, the "PC" light has remained on, and the cable light has blinked slowly (in normal behavior, the PC light blinks off with traffic, and the cable light blinks faster as traffic is transmitted). The modem is a scientific atlantic. > Also, check your /var/log/syslog file for messages regarding > dhcp, your ethernet interface and aything else suspicious. There is one string of messages that appears suspicious, and repeats itself over and over again. Nov 12 10:51:47 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=148 F=0x0000 T=64 (#7) Nov 12 10:51:47 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=149 F=0x0000 T=64 (#7) Nov 12 10:51:47 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=150 F=0x0000 T=64 (#7) Nov 12 10:51:47 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=151 F=0x0000 T=64 (#7) Nov 12 10:51:47 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=152 F=0x0000 T=64 (#7) Nov 12 10:51:47 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 8 24.8.30.255:138 L=255 S=0x00 I=158 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=162 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=163 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=164 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=165 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=166 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=172 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=173 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=174 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=175 F=0x0000 T=64 (#7) Nov 12 10:51:49 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=176 F=0x0000 T=64 (#7) Nov 12 10:51:51 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=187 F=0x0000 T=64 (#7) Nov 12 10:51:51 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=188 F=0x0000 T=64 (#7) Nov 12 10:51:51 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=189 F=0x0000 T=64 (#7) Nov 12 10:51:51 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=190 F=0x0000 T=64 (#7) Nov 12 10:51:51 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 7 24.8.30.255:137 L=96 S=0x00 I=191 F=0x0000 T=64 (#7) Nov 12 10:52:57 white kernel: Packet log: input DENY eth0 PROTO=17 24.8.30.89:13 8 24.8.30.255:138 L=255 S=0x00 I=233 F=0x0000 T=64 (#7)
