CODA-4582 - Open Issues for Investigation

[RogersDave]

*** This post was last edited May 2, 2017 ***

Good morning Community,

As I mentioned in a post two days ago, we have received the next firmware 2.0.10.20 from Hitron. We are currently running initial testing on this version and will push it out to participants in the firmware trial program as soon as it passes initial testing.

However, while running these tests, we discovered abnormal behavior with ICMP and are awaiting feedback from Hitron today to asses how this will be addressed. As soon as I this is confirmed, I’ll update the change log with the correct version information and start pushing it out.

In parallel, we are still working on the following high priority items. In some cases below, I requested affected customers to reach out to me via private message. If you do so, please include your modem MAC address in the subject line (even if we exchange messages daily) as there are a lot of you reaching out to me daily 🙂

UDP Packet Loss

The investigation for what has been reported as UDP packet loss is still ongoing. We have deployed a probe at one fellow forum member on both a CODA-4582 and a CGNM-3552 to collect additional data. We are actively working with Hitron and Intel on the results observed.

Based on what we know so far, in most instances UDP packet loss is coupled with higher uplink usage in the area. Although the impact is noticeable in specific logs (League of Legends), the root cause for the perceivable impact (while playing) is likely related to bufferbloat (see next issue).

Bufferbloat

When comparing the performance of a CODA-4582 to a CGNM-3552 in the same network conditions, the CODA-4582 consistently reports higher bufferbloat when tested on DSLReports.

Update April 12: The solution for this problem will come in two folds. It will require a change in software which will possibly be included in 2.0.10.27 but more likely in 2.0.10.28 and a change in network configuration.

The network configuration change is not compatible with the current firmware so this change will only come after a vast majority of the modems are running the new code. We are however looking at a way to make the change only for specific modems to support testing in the community.

Update April 22: This problem seems resolved in firmware 2.0.10.27

5 GHz WiFi Low range for channels 36 to 48

Lower WiFi channels on the modem have a much smaller range. This is due in part to the limit imposed by Industry Canada to maximum transmit power.

Furthermore, the current automatic channel selection (auto mode) tends to select the lower channels when in similar load conditions.

Workaround: manually select higher channels (149-153-157-161)

Update April 22: The channel selection algorithm has been improved in firmware 2.0.10.27

Loss of OFDM Channel Lock

Under some RF conditions, the modem fails to lock properly on the OFDM channel. This typically result in variable performance.

Update April 12: This problem is resolved in 2.0.10.26T2

List of connected device does not get fully populated

This is a known issue that has been tracked since firmware 2.0.10.13. We are making improvements at every firmware but it is not a perfect system.

The situation is worst after a reboot or firmware upgrade as the list gets reset and must be repopulated as devices renew their DHCP lease.

NAT Loopback not working for wired clients

When setting up port forwarding to an internal server, it is possible for a client on WiFi to reach the server using the external IP/port. If the client is on a wired interface, it doesn't work.

Update April 12: This problem is resolved in 2.0.10.26T2 (not confirmed)

LAN Counters not working

Some customers reported that LAN counters (especially in bridge mode) are reporting inaccurate values.

This problem has been reported to Hitron for investigation.

Unexpected modem reboot

Some customers reported their modem reboots unexpectedly. We have also seen this behavior in our lab.

Update April 12: This problem is resolved in 2.0.10.26T2

Missing SC-QAM Channels

After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 2.0.10.26T2 to address this behavior but it has not corrected all scenarios.

Investigation continues with Hitron.

WiFi Survey

The WiFi Survey functionality in firmware 2.0.10.26T2 (and possibly before) reports incorrect SSID names.

Guest Network

When connecting to the Guest Network, an error message is displayed "only allow DHCP client to use this wireless".  This has been reported in firmware 2.0.10.26T2.

Update April 22: This issue has been resolved in firmware 2.0.10.27

Update May 2: It seems this issue is not fully resolved and still experienced by some users

---

Future Planned Improvements

The following are items that we are working on in parallel of the above.

• Improvement in WiFi speeds
• Improvement in latency / bufferbloat

Dave

*Edited Labels*

[Jeffj]

---

@rjmaxim wrote:

---

@Jeffj wrote:

---

@Hwaiting wrote:

---

@Jeffj wrote:

---

@RogersDave wrote:

---

@gp-se wrote:

@RogersDave got .24 a few hours ago, network is SLOW, so I checked my DOCSIS Logs: 

---

@gp-se, I just ran a remote test on your modem and can clearly see signs of interference at 591 MHz and possibly at 597 MHz.

For the geeks out there, this is really close to a quarter wavelength of WiFi channel 1 (2401-2423 MHz).

My best recommendation is to swap this modem whenever you have a chance.

Dave

---

Just to explain to the non geek a little further and to geek out a bit my self lol

Cable operates between 100MHz to 1000MHZ  area. so much ofthat range is with in a quarter to half wave legnth of the 2.4ghz spectrum.  The fact that most consumer routers sue quarter wave, quarter wave di pole or half wave antennas due to the form factor they need to achieve. this probably has a signifigant factor in the interference as well. 

Also the antenna placement on these access points is not optimal, again due totheformfactor they have to achieve so they actually generate some noise in the spectrum them selves, but typically this doesnt matter because it can still cover the average household so no one notices or cares untill something like interfering with your CM happens. 

Back a few yeats ago, i did an experiment and shielded a TPlink WR-1040D antennas from them selves so they dont cross talk, and essentially doubled the range of the unit, but it changed it from a omni directional unit to a directional due to the shielding. I was also able to reduce the transmit power by almost 60% and still gain better range and thus reducing noise signifigantly. 

Wireless is a cruel mistress sometimes. 

---

So in the case where the modem is experiencing interference, is it experiencing the interference from it's own radio antennas?  And if we are using it in bridge mode with our own routers, does separation from the modem and router make much of a difference if the waves are omnidirectional?  Is there a minimal distance we should have them separated by?  Thanks.

---

As long at the modem is the black dot with the proper shielding distance *shouldnt* matter and it shouldnt interfear with its self. Otherwise Rogers recommended having your wireless 2.4 turnedo ff on the Coda if its not a black dot and have your router 6 feet minimum away. 

---

Just my 2cts of ignorance...isn't the interference only when you are running Coda in Gateway and also attach a router, when both units are broadcasting WiFi frequencies.....I cannot see how the Coda in Bridge mode can be affected by the WiFi frequencies of a router to slow it down. I am not a DataCom guru and would like to understand. Cheers...     

---

No, If your CODA modem suffers from interference, it does not matter the source of the 2.4 GHZ interference, Be its self or a seperate AP. This is why they recommend you to get a Black dot modem if you have issues and keep your seperate AP at minimum 6 feet away from the CM.  If you suffer from the interfernce using the built in 2.4 GHz will be unusable and you will notice issues. 

[lethalsniper]

HI @RogersDave seems like my modem has rebooted on its own last night around 4am I have been on .24 since Thursday wondering was there any work being done or does my modem suffer from interference

[gp-se]

@lethalsniper

if you have interference issues you'll notice "sync errors" in the DOCSIS logs.

[JohnBeaudin]

My DOCSIS log is loaded with errors but no synch error at least.

Some people on D3.1 mention that they have no more errors in their log since 3.1 , looks like D3.1 is the answer to many issues.

[lethalsniper]

I have had those error messages before and I'm on 3.1 and was on .23

[rjmaxim]

---

@gp-se wrote:

@lethalsniper

if you have interference issues you'll notice "sync errors" in the DOCSIS logs.

---

@gp-se Thx ...Good to know. My Blk Dot .24....and Signal strength on 13 channels between 0 and -6.0

and Log over last 3 days showing one synch error. Does this mean I have some interference. Maybe the  Blkdot 4582 Diplexer is not shielded enough.....I am running in bridge mode but if the 4582 is not sufficiently shielded it could get interference from my router 2.4Ghz . Will test by turning this frequency off on the router. Also note the date on the first message....1970? Maybe some other mysterious force is at play... LOL.  

No.	Time	Type	Priority	Event
1	01/01/1970 00:01:05	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
2	02/16/2017 22:51:28	90000000	warning	MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC= xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
3	02/17/2017 05:35:49	84000500	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC= xx:xx:xx:xx:xx:xx:c0;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
4	02/17/2017 17:58:26	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC= xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
5	02/17/2017 18:21:45	90000000	warning	MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC= xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
6	02/18/2017 03:58:08	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC= xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

[prateeck7]

@gp-sewhat about this? I am on Docsis3.1

No.	Time	Type	Priority	Event
1	02/17/2017 16:36:01	82000400	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
2	02/17/2017 16:36:30	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
3	02/17/2017 16:36:45	90000000	warning	MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
4	02/17/2017 16:36:46	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
5	02/17/2017 16:44:28	84000500	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
6	02/17/2017 16:44:34	84020200	warning	Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
7	02/17/2017 16:45:23	82000400	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
8	02/17/2017 16:45:51	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
9	01/01/1970 00:00:02	68000401	warning	ToD request sent - No Response received;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
10	02/17/2017 16:46:09	90000000	warning	MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
11	02/17/2017 16:46:28	82000500	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
12	02/17/2017 16:49:41	84000500	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
13	02/17/2017 16:49:46	84020200	warning	Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
14	02/17/2017 16:50:37	82000400	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
15	02/17/2017 16:51:06	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
16	02/17/2017 16:51:16	68000401	warning	ToD request sent - No Response received;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
17	02/17/2017 16:51:20	90000000	warning	MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18	02/17/2017 17:07:17	68010300	error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19	02/17/2017 17:18:31	90000000	warning	MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20	02/18/2017 17:18:50	84020200	warning	Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

[gp-se]

I am not sure how many Sync Errors are acceptable, but from my own experience when I cause interference on my modem I will get a Log full of Sync Errors. However some Sync Errors could be caused from other issues besides interference. Anytime there is a Sync Error the data connection drops, so it's something that needs to be addressed.

[Jeffj]

0 sync error are acceptible as they cause a disruption in service. The first step would be to rebooot the modem.  and ask rogers to do a sync test on your CM. Then go from there. If you are already on .24 which solved my sync issues then you have a hardware or infrastructure issue it seems. 

[Triple_Helix]

Working well here on my 250/20 plan!

[rjmaxim]

---

@Jeffj wrote:

0 sync error are acceptible as they cause a disruption in service. The first step would be to rebooot the modem.  and ask rogers to do a sync test on your CM. Then go from there. If you are already on .24 which solved my sync issues then you have a hardware or infrastructure issue it seems. 

---

@Jeffj 

---

@Jeffj wrote:

0 sync error are acceptible as they cause a disruption in service. The first step would be to rebooot the modem.  and ask rogers to do a sync test on your CM. Then go from there. If you are already on .24 which solved my sync issues then you have a hardware or infrastructure issue it seems. 

---

Turned-off 2.4 on Router, no diff on Negative  Signal strength or Speed. Will ask Rogers to do Synch test and infrastructure. Appreciate the advise. 

[gp-se]

@rjmaxim

---

@rjmaxim wrote:

Turned-off 2.4 on Router, no diff on Negative  Signal strength or Speed. Will ask Rogers to do Synch test and infrastructure. Appreciate the advise. 

---

there is nothing wrong with having negative signal levels, the spec is: -10 to +10, 0 is optimal.

[Hwaiting]

---

@gp-se wrote:

@rjmaxim

---

@rjmaxim wrote:

Turned-off 2.4 on Router, no diff on Negative  Signal strength or Speed. Will ask Rogers to do Synch test and infrastructure. Appreciate the advise. 

---

there is nothing wrong with having negative signal levels, the spec is: -10 to +10, 0 is optimal.

---

Are the same factors that affect interference the same that affect signal strength?  Or are these 2 separate beasts all together?  What would cause signal strength to fluctuate?  I often see fluctuations that are 2-3dBs for a given downstream channel throughout the day.

[gp-se]

@Hwaiting

---

Hwaiting wrote:

Are the same factors that affect interference the same that affect signal strength?  Or are these 2 separate beasts all together?  What would cause signal strength to fluctuate?  I often see fluctuations that are 2-3dBs for a given downstream channel throughout the day.

---

Signal strength will always fluctuate. Resistance changes in the conductor based on different variables such as temperature, etc. 

However you are within spec so you shouldn't have any issues, being at optimal 0"" wont make your connection any faster than being at -6 for example.

[prateeck7]

@RogersDaveGood progress. Ever since in Docsis3.1, I have a better bufferbloat consistently below 200ms in download end. Upload is abelow 500ms.

Also, thank you for upgrading me to .24.

Best internet speed so far 949/47mbps at the morning.

I am still getting 940+mbps on download. But upload won't get past 30mbps now.

My signals:

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	591000000	256QAM	3.200	7	38.983
2	567000000	256QAM	1.400	3	38.605
3	573000000	256QAM	1.000	4	38.605
4	579000000	256QAM	0.800	5	38.605
5	585000000	256QAM	2.300	6	38.605
6	561000000	256QAM	2.000	2	38.605
7	597000000	256QAM	2.300	8	38.983
8	603000000	256QAM	1.500	9	38.605
9	609000000	256QAM	2.600	10	38.605
10	615000000	256QAM	3.500	11	38.605
11	621000000	256QAM	3.300	12	38.983
12	633000000	256QAM	1.900	13	38.605
13	639000000	256QAM	1.800	14	38.983
14	645000000	256QAM	1.900	15	38.605
15	651000000	256QAM	1.800	16	38.605
16	657000000	256QAM	1.300	17	38.605
17	663000000	256QAM	1.000	18	38.605
18	669000000	256QAM	1.300	19	38.605
19	675000000	256QAM	1.400	20	37.636
20	681000000	256QAM	1.200	21	37.636
21	687000000	256QAM	1.200	22	38.983
22	693000000	256QAM	0.900	23	38.605
23	699000000	256QAM	1.300	24	38.605
24	705000000	256QAM	1.700	25	38.605
25	711000000	256QAM	0.900	26	38.605
26	717000000	256QAM	1.000	27	38.983
27	723000000	256QAM	1.900	28	38.605
28	825000000	256QAM	-4.200	29	36.610
29	831000000	256QAM	-6.600	30	35.780
30	837000000	256QAM	-8.100	31	35.595
31	843000000	256QAM	-7.500	32	35.595
32	555000000	256QAM	1.400	1	38.983

OFDM Downstream Overview

Receiver	FFT type	Subcarr 0 Frequency(MHz)	PLC locked	NCP locked	MDC1 locked	PLC power(dBmv)
0	4K	275600000	YES	YES	YES	3.299999
1	NA	NA	NO	NO	NO	NA

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	30596000	ATDMA - 64QAM	31.000	1	6400000
2	38596000	ATDMA - 64QAM	36.250	3	3200000
3	23700000	ATDMA - 64QAM	30.500	2	6400000

OFDM/OFDMA Overview

Channel Index	State	lin Digital Att	Digital Att	BW (sc's*fft)	Report Power	Report Power1_6	FFT Size
0	DISABLED	0.5000	0.0000	0.0000	-inf	-1.0000	4K
1	DISABLED	0.5000	0.0000	0.0000	-inf	-1.0000	4K

[gp-se]

@prateeck7 

Upload speed usually drops off during peak hours. Try testing it again either tonight after 11pm, or early in the morning before 8am. If it still stops right at 30mb/s then I would contact Rogers and ask if you are provisioned for 30mb/s upload or 50mb/s upload. Some areas only support 30mb/s upload, perhaps your provisioning changed for whatever reason.

Also some of your downstream signal levels are all over the place, however since you're on DOCSIS 3.1 it shouldn't matter since it's not using those channels.

[VivienM]

---

@gp-se wrote:

Also some of your downstream signal levels are all over the place, however since you're on DOCSIS 3.1 it shouldn't matter since it's not using those channels.

---

Do we know how to read the OFDM D3.1 signal data?

I would be concerned that whatever physical problem is causing all over the place signal levels on the D3.0 channels would also be messing with the D3.1 carrier in some unknown way...

[gp-se]

---

@VivienM wrote:

---

@gp-se wrote:

Also some of your downstream signal levels are all over the place, however since you're on DOCSIS 3.1 it shouldn't matter since it's not using those channels.

---

Do we know how to read the OFDM D3.1 signal data?

I would be concerned that whatever physical problem is causing all over the place signal levels on the D3.0 channels would also be messing with the D3.1 carrier in some unknown way...

---

The 3.0 Channels could be all over the place because they are being refarmed and tweaked for 3.1

I'm guessing there is a lot of fine tuning that still needs to be done to keep speeds good for 3.0 customers and 3.1 customers.

[tonytoronto]

  Good morning,

 Had something weird happen this morning,  wired and wireless devices were connected to 4582 but had no internet. tried pinging test from within the router GUI and 100% packet loss.  I checked the logs and nothing there, checked signal levels and they were all between -2 to -6 and nothing i could see would cause that. Reboot and works again. That was the first time ive seen that, no internet at all.  I'm on .24, anyone experienced anything like that?

[Telek]

@prateeck7

So although your signal strengths are all within range, what's concerning to me is how much they fluctuate, especially in the 825-843MHz range.  I'm not an expert, but that tells me that there's some sort of problem.

Interestingly enough that's also 1/3rd the 2.4GHz range. I wonder if there's a shielding problem? The 1/4 wavelength is strong, so not the same problem that we saw before.

Telltale sign though - if you reboot the modem, does your upload speed come back?

[Telek]

Note to everyone in this thread (might be worth making a new thread for this, but...):

I'm not certain that speedtest.net is the best place to use for gigabit testing. From what I gather from their support page, they do all testing to a single server. For 250mbit and below connections this may be fine if the servers are sitting on fat pipes. For gigabit and above, I don't know if it's reliable.

For example, depending on which server I hit, sometimes it'll be pretty spikey, but then I'll immediately reload and get a different server and it'll be more solid.

DSLReports has a different test where they have a couple dozen servers and split the load between them. They seem to report higher speeds, unfortunately they don't show a breakdown of the speed test over the entire run, and their conclusion scores are ... interestingly low. I think their test is setup better in terms of maximum speed, but they expect gigabit connections to be symmetric and fiber, so cable-based connections get "scored" very poorly. This can also lead us to believe that there's a bigger problem than we actually have.

What do you guys think? Putting 100% faith in speedtest.net may be exacerbating concerns that aren't actually a problem.  I'm not sure what the most reliable way to actually do proper connection testing is.

I would also like to find something that can monitor my connection as frequently as possible constantly so that we can detect drop-outs, latency spikes, etc.  Any ideas?