Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mattlwil]

This is supposedly how the CMTS runs in "maintenance mode"

I captured this during a hiccup.


And here are some hiccups I captured over the months.The were accompanied by T3's.






While this was going on sometimes I would be playing COD and I would start lagging. So I would lay down and hit 'select' and watch the pings go to one red bar or it would boot me from the room altogether >.<

[Trikein]

Hmm, probably the story you got from Comcast is half true. Alot of times they call it it to maintenance, but unless you have a maintenance ticket to track it, its not a official thing. Its like calling up your town and reporting a pot hole. Eventually it will get fixed, but it doesn't mean a guy is on your street the next day paving. Then again, usually you get a pretty good answer from DSL reports, so if he gave it a green light,  that is good enough for me...for now.

As for your graphs, could you give me some context? From what I can find online, usually NetMeter measures from your NIC, your WAN(Router) and your Modem. Which is that for? Also I can find documentation on how it graphs upload vs download. And last, whats the X axis. Hours? MS? Is that per throttling cycle?

Also you might want to look into a program called Pingplotter. Netmeter looks to give your a capacity test, which is good, but there can be many reasons for speed decrease. Now if your doing a ping test along side of it to a IP inside your ISP's network (say their DNS or DHCP server) and see a latency spike next to a speed decrease, then you have black and white proof where the problem is. Ofcourse this is only relevant when you have a direct connection between the PC running the test and the modem.

Let me know about those graphs. Visually speaking, it looks like there could be something there. That looks too steady to be environmental (wind, storm,temp,etc). And where did you get that info on "maintenance mode"? Sounds like theres more to that story.

[Trikein]

"I have 2 Xboxes, one wired, one wireless. The wired xbox is the one I have to reset the router for. The wired xbox is the only one with QoS setup for it via Gaming/Gamerfuel. I can leave the xbox on for a month straight no problems but when I start turning it on/off when I'm not using it every once in awhile it won't connect and I have to reset the router for it to reconnect. "

Actually, I think we may have gotten off topic here. Looking at your OP, it looks like the issue isn't intermident connetivity with the 360, but a issue with it not connecting when you turn it on and off? If so, I think someone else on this forum had a simular issue. Searched the forums and found this post:

http://forums.dlink.com/index.php?topic=14226.0
Problem:
The only strange thing is that every time I start up either XBox, it displays a message that it cannot connect to XBox Live.  On that same message screen there is an option to test the XBox Live connection.  Invariably, the test passes, and the XBox indicates that XBox Live is "Up and Running".  With that step performed, I can connect to XBox Live as normal, and play away.  I have now gotten into the habit of booting up the Xbox console, and skipping right to the network connection test screen before even attempting to log in with an XBox Live profile.  It's an extra step that I would rather not have to perform each time.

Possible solution found:
I explained the problem to one of the systems guys at work and he said it sounded like a DNS problem.  I looked through some XBox Live support forum posts, and hit on the following.  On each of the XBox consoles, I changed the DNS settings from automatic to manual, and entered the appropriate primary and secondary DNS for my ISP.  So far so good.  No need to test the XBox Live connection before signing into an XBL profile.

[FurryNutz]

Tricky, I have 2 xboxes and both are wired and have never had to reset the router. You shouldn't have to do this either. Makes me wonder why you do.

"I have 2 Xboxes, one wired, one wireless. The wired xbox is the one I have to reset the router for. The wired xbox is the only one with QoS setup for it via Gaming/Gamerfuel. I can leave the xbox on for a month straight no problems but when I start turning it on/off when I'm not using it every once in awhile it won't connect and I have to reset the router for it to reconnect. "

[mattlwil]

Here is what I found out about the x-axis for Net Meter. The chart can be configured to auto-scale to network activity levels, and you can specify the bandwidth per interface, but the time/x-axis can't be configured, making inspection of details at specific points in time challenging.

Those graphs were captured from my PC doing a multiple file download from dl.tv during a hiccup through the router. The "maintenance mode" graph is my PC direct to the modem. Steve on DSL reports mentioned that the graph looked like the CMTS was in maintenance mode. That's where I got that from.

I have a graph of an Upload speed test right here

I have pingplotter now. But I have not gotten a chance to use it.

I was on last.fm last night and got disconnected from live and it reconnected manually through the menu right away. I viewed modem and router logs and didn't see anything indicating a problem. I can post the router logs when I get home leading up to the disconnect.

[mattlwil]

Router logs minutes before the disconnect while using Last.fm. The last T3 on the modem logs was Aug 26th at 7:30 in the morning. There was another T3 on Aug 22nd at 6:30 P.M.

Log viewed by IP address 192.168.0.199
[INFO]   Mon May 10 14:54:55 2004   Above message repeated 3 times
[INFO]   Mon May 10 14:54:53 2004   Allowed configuration authentication by IP address 192.168.0.199
[INFO]   Mon May 10 14:53:54 2004   Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:24760
[INFO]   Mon May 10 14:52:45 2004   Above message repeated 8 times
[INFO]   Mon May 10 14:50:01 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 75.64.160.153:2301
[INFO]   Mon May 10 14:50:01 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 75.64.160.153:9090
[INFO]   Mon May 10 14:50:01 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 75.64.160.153:8080

[mattlwil]

Just got disc from last.fm. The other xbox which is wirelss is on COD currently, no problems. Just the wired xbox got booted. I'm also watching football via stream torrent on my PC and its still playing fine. I had netmeter screen up and didn't see any pauses or interruptions.

Router Logs

Tue May 11 12:34:58 2004   Log viewed by IP address 192.168.0.199
[INFO]   Tue May 11 12:34:56 2004   Allowed configuration authentication by IP address 192.168.0.199
[INFO]   Tue May 11 12:33:54 2004   Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:32054
[INFO]   Tue May 11 12:32:42 2004   Above message repeated 8 times




Booted again about 10 minutes after I signed back in.

Tue May 11 12:46:14 2004   Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:32520
[INFO]   Tue May 11 12:44:45 2004   Above message repeated 7 times
[INFO]   Tue May 11 12:42:50 2004   Blocked outgoing TCP packet from 192.168.0.150:57632 to 195.24.232.207:443 as PSH:ACK received but there is no active connection
[INFO]   Tue May 11 12:41:42 2004   Blocked incoming TCP connection request from 122.227.164.71:6000 to 75.64.160.153:7212
[INFO]   Tue May 11 12:41:42 2004   Blocked incoming TCP connection request from 122.227.164.71:6000 to 75.64.160.153:8000

No modem logs.


No modem logs to report lol >.<

Got any ideas?

I suppose it could be a last.fm problem too eh?

[Trikein]

Tricky, I have 2 xboxes and both are wired and have never had to reset the router. You shouldn't have to do this either. Makes me wonder why you do.

"I have 2 Xboxes, one wired, one wireless. The wired xbox is the one I have to reset the router for. The wired xbox is the only one with QoS setup for it via Gaming/Gamerfuel. I can leave the xbox on for a month straight no problems but when I start turning it on/off when I'm not using it every once in awhile it won't connect and I have to reset the router for it to reconnect. "

Oh, I wasn't saying I had that problem, please, me with a 360? Ppsssh. Hehe, J/k. I was quoting his orginal problem. And re-reading it it seemed like he only had a problem with the wired 360. And if that is the case, that makes it hard to be the modem. Could still be, but less likly.  Also, I was quoting from someone who had a similar problem with DNS and having to run the connection test each time before connecting with the 360. It seemed relevant.

[FurryNutz]

AH ok, got cha. Sure can get lost in some posts on here. LOL

[Trikein]

Router Logs

Tue May 11 12:34:58 2004   Log viewed by IP address 192.168.0.199
[INFO]   Tue May 11 12:34:56 2004   Allowed configuration authentication by IP address 192.168.0.199
[INFO]   Tue May 11 12:33:54 2004   Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:32054
[INFO]   Tue May 11 12:32:42 2004   Above message repeated 8 times


Booted again about 10 minutes after I signed back in.

Tue May 11 12:46:14 2004   Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:32520
[INFO]   Tue May 11 12:44:45 2004   Above message repeated 7 times
[INFO]   Tue May 11 12:42:50 2004   Blocked outgoing TCP packet from 192.168.0.150:57632 to 195.24.232.207:443 as PSH:ACK received but there is no active connection
[INFO]   Tue May 11 12:41:42 2004   Blocked incoming TCP connection request from 122.227.164.71:6000 to 75.64.160.153:7212
[INFO]   Tue May 11 12:41:42 2004   Blocked incoming TCP connection request from 122.227.164.71:6000 to 75.64.160.153:8000

Well your 75.64.160.153 and XBL is 65.55.42.180. Port 3074 is the port for XBL as per

http://support.xbox.com/support/en/us/nxe/kb.aspx?category=xboxlive&ID=908874&lcid=1033

So it looks like its a much simpler problem. Your router is blocking the port for 360. When it does, your 360 disconnects. Also found this post that might be relevant.

http://forums.dlink.com/index.php?topic=14654.0

Either way, can you post your Forwarding rules(or gamefuel if your using that instead) which can be found: http://192.168.0.1/Advanced/Gaming.shtml

PS. As for that TCP blocked, that belonged to some spam site out of China so..you can keep that one blocked LOL.

[mattlwil]

I really appreciate you guys looking into this.

Gaming isn't used as per the sticky.

Game Fuel Settings

Enable GameFuel : checked

Automatic Classification : checked

Dynamic Fragmentation : un-checked

Automatic Uplink Speed : checked

Measured Uplink Speed : 5507 kbps

Manual Uplink Speed : 128  kbps  << 128kbps

Connection Type : Cable Or Other Broadband Network

Detected xDSL or
Other Frame Relay Network : No

          Name     Priority     Local IP Range     Remote IP Range     Protocol / Ports           
   XBL1    1    192.168.0.150 - 192.168.0.150    0.0.0.0 - 255.255.255.255
   Both
0 / 65535
0 / 65535

[Trikein]

Yea, thats what I thought. We were overthunking it.

You need to forward specific ports, not just all of them..and all to one place.

"A GameFuel Rule identifies a specific message flow and assigns a priority to that flow. "

So it priotized traffic, it doesn't direct it. You still need to forward the connection from the WAN to the LAN. And then the gamerules priortize the traffic on your network. The thing is, both the PS3 and 360 have UPnP so most forwarding is redudent. If however you have a game fuel rule that conflicts with UPnP you need to set up a rule around it.

I will actually write up some instructions for you tommorow. I am beat right now. But yea, I think your problem is with that configuration.

[mattlwil]

Aight, I was thinking the same thing... crash time...

TTYL

[FurryNutz]

You could do this, try changing the Protocol / Ports from 0/65535 to 3074 for both from and to. I have been experimenting and believe that Trikien is correct in that not all ports should be used. I have been using my 2nd xbox with the settings detailed in the gameing sticky however have set the protocol ports to be specific and to use 3074 for XBL. Been working just as good as the more global port setting. Give that a go and see how it it does. Let us know how it goes. Hope we can help.

[Trikein]

First, my settings:

This is assuming 192.168.0.150 is your Xbox 360. If not, please replace each occurrence of that IP mentioned with your 360's IP. Also, this is assuming you have a DHCP reservation set for that IP and it is set as static on your 360's settings.

http://192.168.0.1/Advanced/Gaming.shtml

Enable: Yes
Name: Xbox Live
IP Address: 192.168.0.150
TCP Ports: 53, 80, 3074
UDP Ports: 53, 88, 3074
Schedule: Always
Inbound Filter: Allow All

http://192.168.0.1/Advanced/Traffic_Shaping.shtml

Enable: Yes
Name: Xbox Live 1
Priority: 96
Protocol: 257  << Both
Local IP Range:  192.168.0.150   to   192.168.0.150
Local Port Range:  3074     to     3074
Remote IP Range: 65.52.0.0   to   65.55.255.255
Remote Port Range:   3074     to     3074

Enable: Yes
Name: Xbox Live 2
Priority: 105
Protocol: 257  << Both
Local IP Range:  192.168.0.150   to   192.168.0.150
Local Port Range:  53     to     53
Remote IP Range: Your Primary DNS Server here   to   Your Second DNS Server here
Remote Port Range:   53     to     53


Note1: Here is a break down of which each port does:
Port 53     - DNS
Port 80     - HTTP (Website traffic)
Port 88     - Kerberos (Password system for Xbox Live)
Port 3074  - Xbox Live (Multi-player traffic)

TCP vs UDP: Think of TCP as being a walkie talkie and UDP being a phone. Each time your done saying something and before each time you go to say something with TCP you need to ask for permission. UDP doesn't do that. Not accurate, but just to give you a idea.

Note2: I set the priority to 96 and 105 for a reason. Alot of people make the mistake of setting this to one. QoS is traffic managerment. Another words, you have a finite amount of bandwidth and certian things trying to use it. Also, you have different bottlenecks of that bandwidth. A bottleneck is a point in the chain of connections from your Xbox to the game server you are connecting to, and back again, where the performces decreases. The point of QoS tagging is to try to move that bottleneck to inside your router where you have some control of it.  Also, notice I set the IP range to a pretty wide birth since it was a unknown. All Xbox Live in the US gets routed somehow through Seatle WA servers, so most likly you could set it to 1-3 servers, but since 65.52.0.0   to   65.55.255.255 are all IP's ownder by Microsoft, I thought it was pretty safe. Just incase they have multiple servers or change them.

Note3: This is for 1 Xbox 360. If you have two, I suggest disabling the Gaming rule and allowing UPnP to manage the connection and have the Gamefuel settings set give priority to one connection and allow the other to defatlt to the 125 QoS priority to create separation of the streams to help prevent packet collision.

PS. As always, let me know how it works and I can advise it. Thanks