drewis
Premium
join:2006-09-04
Hamilton, ON
 ·Cogeco Cable
 ·TekSavvy Solutions..
3 edits | reply to planiwa
Re: Connection Surges - Re: DCCNET/EASLINK - Packet loss/stutter
if this continues to be an issue without resolve, you can always try and get your hands on a proxy server. when i played q3 semi-pro our clan had a few proxies all over the US. Some close to the eastern seaboard for clans we'd play in austrailia.. and asia * 6 years ago the backbone to many of our isps had issues like this for a year or more without resolve..
edit: that is, assuming that the problem doesnt originate from you 
EDITED: spelling |
|
planiwa
join:2009-02-19
Toronto M5S |  reply to Vyper28
Might want to read
»Re: Torrents crash my Router |
|
jobr
join:2004-10-21
Halifax, NS | reply to Vyper28
Re: DCCNET/EASLINK - Packet loss/stutter?
said by Vyper28 :
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
That's the problem. Too many simultaneous connections. |
|
hellsatan
join:2008-12-08
Delta, BC
| reply to Vyper28
When playing these games is there anybody else on the computers. You said in previous posts that you have 4 machines. From my experience with delta cable because they have such a crappy upload limit for basic users even 25kb of upload (which isn't a lot for a decent BT radio) will lag the shit out of me in any of the games you said. I play a few and had same problems when my family surfed when dccnet had those old school modems [I use to play a lot of cs back in my day had lots of cl_flushes wasn't good to be in a 5v5 match and get packets loss]. Seems to be fine now with SB modems. The upload issue is still there and always will.. uploading = slow interweb.
I doubt its either your modem or your router because both are very good equipment. You never know you might have a virus also that is uploading. I had one of those and wasn't fun
Gl m8. |
|
Vyper28
@dccnet.com
| reply to Vyper28
As I suspected, my tracert's didn't really help at all. times out on a random hop between 3-15, different each time. I did get some new reports in my router logs though
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:13 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:19 ? user.warn kernel: NET: 142 messages suppressed.
Jul 4 22:57:19 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 22:57:26 ? user.warn kernel: NET: 3 messages suppressed.
Jul 4 22:57:26 ? user.warn kernel: ip_conntrack: table full, dropping packet.
Jul 4 23:00:01 ? syslog.info root: -- MARK --
Jul 5 00:00:01 ? syslog.info root: -- MARK --
Jul 5 00:03:57 ? daemon.info dnsmasq[136]: DHCPINFORM(br0) 192.168.1.100 00:1a:92:7d:5a:f0
Jul 5 00:03:57 ? daemon.info dnsmasq[136]: DHCPACK(br0) 192.168.1.100 00:1a:92:7d:5a:f0 user-e781d77954
Those tell anyone anything? because They sure as heck look like gibberish to me =) |
|
Vyper28
@cronos-comp.com
| reply to Vyper28
I've read several posts like that, and I concluded that it's likely not my issue simply because it affects ANYTHING I'm doing.
quote:
It seems to me that whatever "90% packet loss" you are experiencing is a consequence of what you are doing, rather than an underlying network problem that won't let you do it.
This is the problem, I would understand that but.. Browsing the web causes it, Xfire causes it, Ventrilo causes it, WoW causes it, Counterstrike Source causes it, Steam causes it.... I suppose i could sit and watch the blinking light on the network adapter.. but it's not really what I was hoping to get for $80 a month =(
I've tried dozens of servers and they are all affected equally. I hunted down a server hosted close by (seattle) and I get the same spikes as to my wow server.
When the problem is occurring a ping will time out to pretty much anything, I try: www.worldofwarcraft.com, www.msn.com, www.google.ca, www.yahoo.com and they all exprience time outs. My tracert's have not helped me at all. I will take a few more tonight, but essentially they all "time out" at some point, it's just different every time. Sometimes 3rd hop, sometime 5th, sometimes it just takes 800ms to get to me 3rd hop.
I'll grab as much info as I can tonight and post it up |
|
Gman
join:2007-11-01
| reply to Vyper28
»forums.worldofwarcraft.com/threa···pageNo=1
Sound familiar? Don't dismiss just because of the ISP name of the post. People from multiple ISPs have the same problem. |
|
planiwa
join:2009-02-19
Toronto M5S
2 edits | reply to Vyper28
The Tomato logs look unremarkable. The DHCP/DNSMASQ messages are LAN-related. As I suspected, you appear to have no *disconnections*. You may have problems on the LAN or on the Net beyond your ISP.
Your router free space is plenty.
If you use QoS you may want to keep an eye on connections for a while: QoS>View Graphs
Or else take a look at connections here:
Advanced>NF/Conntrack
If you see >1000 connections, chances are that connection spikes are crashing your router. But that doesn't seem to be the case, since you've had no router crashes. So it could be other LAN problems or distant Internet routing problems.
The important thing is that you don't appear to have "Near-end Internet" problems, i.e. problems that have to do with your ISP.
The modem log does not show a "disconnect" problem, and neither does the Router log. The Router log is much too detailed to be readable. I suggest logging everything except Cron, Scheduler, NTP. Skip the "Marks". Reduce the clutter so that you can see important messages better.
If you are worried about packet loss, use ping or maybe traceroute to see what is going on.
It seems to me that whatever "90% packet loss" you are experiencing is a consequence of what you are doing, rather than an underlying network problem that won't let you do it.
If your game tells you you have high packet loss. stop the game completely. Then use ping to measure packet loss on the network.
If your game server says "packet loss", you want to ask whether it is near you, near it, or in between.
Ping your WAN gateway to measure packet loss over your cable link. Or you can ping your ISP. Or a central site. Preferably from your router.
Be aware that network routers may not respond to pings or traceroutes, especially when there is congestion.
Please run traceroute -In 4.2.2.1
--
»[RFC] Connection / Speed Problems Checklist |
|
Gman
join:2007-11-01
| reply to Vyper28
A quick search on some of those games forums would tell you that the problem you are most likely facing is a bad hop on a router not even in Canada. Many people who use Bell, Rogers, and all resellers of these ISPs can be affected. This isn't to say that EVERYONE is affected, it's random since the data doesn't flow through the same path all the time. This issue has been ongoing for quite some time. You would think the bad hop would have been fixed by now, but it isn't. Their license should be revoked but yet again, it isn't. Long story short, it most likely is not on your end and there is nothing you can do about it. |
|
hellsatan
join:2008-12-08
Delta, BC | reply to Vyper28
looks normal. what about upstream? |
|
Vyper28
@dccnet.com | reply to Vyper28
Frequency 111000000 Hz
Signal To Noise Ratio 40.8 dB
Power Level 2.0 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading |
|
hellsatan
join:2008-12-08
Delta, BC | reply to Vyper28
that all looks normal. what are you signal levels? (Signal To Noise Ratio, Power Level)
my log = »pastebin.com/d33ae1e3c
looks very similar |
|
Vyper28
@dccnet.com
| reply to Vyper28
Modem Logs:
You still reading this planiwa?
2009-06-12 22:35:47 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-05-10 09:07:50 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-05-10 09:07:44 6-Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-05-10 09:07:14 6-Notice E112.0 SW download Successful - Via Config file
2009-05-10 09:06:48 6-Notice E102.0 SW Download INIT - Via Config file ~GM8Aq1X7vE/SnthzN5frCV3JRqt3OK18Th+9ostpBhwQ
1970-01-01 00:00:58 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:00:54 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:52 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:34 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:23 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-05-10 09:04:02 6-Notice M572.0 Tftp Init Failed - Reinitialize MAC...
2009-05-10 09:04:02 3-Critical D006.0 TFTP failed - configuration file NOT FOUND
2009-05-10 09:02:56 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1)
2009-05-10 09:02:51 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-05-10 09:02:46 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 09:02:45 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 09:02:31 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 09:02:30 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 09:02:27 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 09:02:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 09:02:15 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 09:01:47 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 09:01:44 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 09:01:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 09:01:31 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 09:01:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 09:01:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 09:00:46 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 09:00:44 6-Notice M572.0 Ds Lock Failed - Reinitialize MAC...
2009-05-10 09:00:44 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 09:00:43 6-Notice M572.0 Tftp Init Failed - Reinitialize MAC...
2009-05-10 09:00:43 3-Critical D006.0 TFTP failed - configuration file NOT FOUND
1970-01-01 00:00:53 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:00:49 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:47 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:37 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:36 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:35 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:31 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:20 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:20 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:00:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active |
|
hellsatan
join:2008-12-08
Delta, BC
1 edit | reply to Vyper28
Hey I was wondering if you wanna do a little cable modem trick with me. Its hard to find people with Delta Cable since its such a small internet provider. I use to be able to get these speeds for with my modem ( www.speedtest.net/result/277114970.png ) but now they put a new security on and I need a little help now getting them back.
msn me @ hellz_satanz@hotmail.com or aim me at w00tmuh00t. if your interested. |
|
Vyper28
@cronos-comp.com
| reply to Vyper28
I live in Ladner, I'm pretty tech savvy although not so much on the networking front. I'll try my modems logs when i get home, I think i tried to do that once already and it barked at me about invalid IP's or something... we will see in a couple hours.
I'm going to reset my router back to defaults (tomato defaults) and see if i get any different errors in the logs. I seem to recall when i first started having the problem I was getting Conntrack errors. I did some research and I believe I tweaked the idle connection drop/max connection settings in the router (was 4092 and I set it to 3092 i think?). I'm also going to see if maybe a borrowed router from work (asus as opposed to linksys) changes anything. |
|
hellsatan
join:2008-12-08
Delta, BC
| reply to Vyper28
go here »192.168.100.1/
and look in logs
I have dccnet also its been fine ever since they got bought out.
Where do you live? Delta, Langley, tsawwassen?? I might be able to help ya out |
|
Vyper28
@cronos-comp.com | reply to Vyper28
Mind giving me some tips on how to view my modem's logs? |
|
Vyper28
@dccnet.com
| reply to Vyper28
The spikes have continued consistently, dropping all teh machines on the network repeatedly. Really getting frustrated. I went into my router settings and turned on all the types of logging, and these are the only messages I'm getting:
Jul 1 19:30:01 ? cron.err crond[31121]: USER root pid 31805 cmd rcheck --cron
Jul 1 19:40:01 ? cron.err crond[31121]: USER root pid 31809 cmd ntpsync --cron
Jul 1 19:40:12 ? user.info ntpc[31810]: Time Updated: Wed, 01 Jul 2009 19:40:12 -0700 [+11s]
Jul 1 19:45:01 ? cron.err crond[31121]: USER root pid 31823 cmd rcheck --cron
Jul 1 20:00:01 ? cron.err crond[31121]: USER root pid 31826 cmd logger -p syslog.info -- -- MARK --
Jul 1 20:00:01 ? cron.err crond[31121]: USER root pid 31827 cmd rcheck --cron
Jul 1 20:00:01 ? syslog.info root: -- MARK --
Jul 1 20:15:01 ? cron.err crond[31121]: USER root pid 31832 cmd rcheck --cron
Jul 1 20:30:01 ? cron.err crond[31121]: USER root pid 31835 cmd rcheck --cron
Jul 1 20:45:01 ? cron.err crond[31121]: USER root pid 31839 cmd rcheck --cron
Jul 1 20:53:49 ? daemon.info dnsmasq[136]: DHCPREQUEST(br0) 192.168.1.108 04:4b:80:80:80:03
Jul 1 20:53:49 ? daemon.info dnsmasq[136]: DHCPACK(br0) 192.168.1.108 04:4b:80:80:80:03 user-f3045470bf
Jul 1 20:53:49 ? daemon.warn dnsmasq[136]: not giving name mom-26452b09508 to the DHCP lease of 192.168.1.106 because the name exists in /etc/hosts.dnsmasq with address 192.168.1.110
Jul 1 20:53:49 ? daemon.warn dnsmasq[136]: not giving name user-e781d77954 to the DHCP lease of 192.168.1.100 because the name exists in /etc/hosts.dnsmasq with address 192.168.1.105
Jul 1 21:00:01 ? cron.err crond[31121]: USER root pid 31842 cmd logger -p syslog.info -- -- MARK --
Jul 1 21:00:01 ? cron.err crond[31121]: USER root pid 31843 cmd rcheck --cron
Jul 1 21:00:01 ? syslog.info root: -- MARK --
Jul 1 21:06:59 ? daemon.info dnsmasq[136]: DHCPINFORM(br0) 192.168.1.100 00:1a:92:7d:5a:f0
Jul 1 21:06:59 ? daemon.info dnsmasq[136]: DHCPACK(br0) 192.168.1.100 00:1a:92:7d:5a:f0 user-e781d77954
Jul 1 21:15:01 ? cron.err crond[31121]: USER root pid 31883 cmd rcheck --cron
Jul 1 21:30:01 ? cron.err crond[31121]: USER root pid 31885 cmd rcheck --cron
Jul 1 21:45:01 ? cron.err crond[31121]: USER root pid 31898 cmd rcheck --cron
Jul 1 22:00:01 ? cron.err crond[31121]: USER root pid 31900 cmd logger -p syslog.info -- -- MARK --
Jul 1 22:00:01 ? cron.err crond[31121]: USER root pid 31901 cmd rcheck --cron
Jul 1 22:00:01 ? syslog.info root: -- MARK --
Are they any help in finding out what the problem is? |
|
Vyper28
@dccnet.com
| reply to Vyper28
I've had a couple spikes tonight so far, and those messages are the only thing that repeat over and over O-o.
Name WRT54GL
Model Linksys WRT54G/GS/GL
Time Tue, 30 Jun 2009 21:52:53 -0700
Uptime 51 days, 11:11:17
CPU Load (1 / 5 / 15 mins) 0.00 / 0.00 / 0.00
Total / Free Memory 14.19 MB / 2,124.00 KB (14.62%)
Should my memory be that full? |
|
Vyper28
@dccnet.com
| reply to Vyper28
Jun 30 18:13:04 ? daemon.info dnsmasq[136]: DHCPREQUEST(br0) 192.168.1.106 00:22:15:54:d6:ff
Jun 30 18:13:04 ? daemon.info dnsmasq[136]: DHCPACK(br0) 192.168.1.106 00:22:15:54:d6:ff mom-26452b09508
Jun 30 18:13:04 ? daemon.warn dnsmasq[136]: not giving name mom-26452b09508 to the DHCP lease of 192.168.1.106 because the name exists in /etc/hosts.dnsmasq with address 192.168.1.110
Jun 30 18:13:04 ? daemon.warn dnsmasq[136]: not giving name user-e781d77954 to the DHCP lease of 192.168.1.100 because the name exists in /etc/hosts.dnsmasq with address 192.168.1.105
Jun 30 18:58:30 ? daemon.info dnsmasq[136]: DHCPREQUEST(br0) 192.168.1.100 00:1a:92:7d:5a:f0
Jun 30 18:58:30 ? daemon.info dnsmasq[136]: DHCPACK(br0) 192.168.1.100 00:1a:92:7d:5a:f0 user-e781d77954
Jun 30 18:58:30 ? daemon.warn dnsmasq[136]: not giving name mom-26452b09508 to the DHCP lease of 192.168.1.106 because the name exists in /etc/hosts.dnsmasq with address 192.168.1.110
Jun 30 18:58:30 ? daemon.warn dnsmasq[136]: not giving name user-e781d77954 to the DHCP lease of 192.168.1.100 because the name exists in /etc/hosts.dnsmasq with address 192.168.1.105
Jun 30 18:59:32 ? daemon.info dnsmasq[136]: DHCPINFORM(br0) 192.168.1.100 00:1a:92:7d:5a:f0
Jun 30 18:59:32 ? daemon.info dnsmasq[136]: DHCPACK(br0) 192.168.1.100 00:1a:92:7d:5a:f0 user-e781d77954
Jun 30 19:00:02 ? syslog.info root: -- MARK -- Is all I see in my routers logs, Is this relevant? I'll try check right after I experience the spikes as well tonight. |
|
