Print

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

[hajekmarek]

First, why does this forum give me a message that "The message exceeds the maximum allowed length (20000 characters)." I am nowhere near 20,000 characters. I continued to chop off the log from 19,000 down to around 1500 characters before the message went away.

About one month ago my DSL modem died so I reordered the service and upgraded to 6MB/s down speed (AT&T) and obtained a new DSL modem with it. Ever since then I've had issues with my DSL connection and can't figure out what is causing this. The new DSL modem is a DSL/Router combo, the Westell DSL/Router modem, SKU: F90-610025-06. I set the DSL modem to bridged mode and configured the DIR-655 router to handle the PPPoE connection. Since the first time I set it up like that I have completely reset the router several times via the reset button on its back(held for 10s or so) and manually reentered the connection info. I turn everything off, turn the DSL modem on and let it power up. Then I turn the DIR-655 on and let it establish connection. Everything works for a while but then I continue to get strange behavior such as the browser occasionally sits there trying to connect to (different) sites and then a page shows up with the Try Again button. While this is happening I can always log into the router and view its log. The log usually doesn't show anything unusual happening and definitely does not show any attempts to reconnect. Then 30 seconds later everything works again (without re-establishment of PPPoE connection in the log). At other times the connection fails and the router has to re-acquire WAN access.
I should also mention that I upgraded to the latest version of the firmware(1.35NA) after this behavior became common without any success in resolving this. I have the regular version of DIR-655, not the rev. B. I occasionally see a "INTERNET PPPoE session protocol fault.  Connection attempt failed." and "WAN interface speed measurement aborted as they did not converge"
Below is a snapshot of my log. Any ideas on what to do?
Oh, and just to be thorough, here is how my PPPoE connection is setup
Under Manual Internet Settings I have:
My Internet connection is: PPPoE (Username/Password)
Dynamic IP
Username & password filled in
Reconnect Mode: Always on
No primary or secondary DNS
MTU: 1492
My computer MAC address cloned here

I also setup the wireless connection and the dlink time server to sync time on router but no other configuration on the router.

LOG:

[INFO] Wed Jan 26 20:32:50 2011 Blocked incoming TCP connection request from 96.17.157.62:49624 to 99.162.254.120:50236
[INFO] Wed Jan 26 20:32:50 2011 Log viewed by IP address 192.168.0.199
[INFO] Wed Jan 26 20:32:47 2011 Blocked incoming TCP connection request from 96.17.157.62:49624 to 99.162.254.120:50236
[INFO] Wed Jan 26 20:32:45 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:45 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:45 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:45 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:45 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:45 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Above message repeated 2 times
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:44 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:43 2011 Above message repeated 2 times
[INFO] Wed Jan 26 20:32:43 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:43 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:43 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:43 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:43 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:43 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:32:43 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:43 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:43 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:43 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Above message repeated 2 times
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Above message repeated 2 times
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:42 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Above message repeated 2 times
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:41 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:32:41 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Above message repeated 2 times
[INFO] Wed Jan 26 20:32:40 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:32:40 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.254.120:54333
[INFO] Wed Jan 26 20:32:40 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:32:35 2011 Time synchronized
[INFO] Wed Jan 26 20:32:37 2011 Requesting time from 74.80.219.11
[INFO] Wed Jan 26 20:32:37 2011 Time server ntp1.dlink.com is at IP address 74.80.219.11
[INFO] Wed Jan 26 20:32:37 2011 Requesting time from 61.67.210.241
[INFO] Wed Jan 26 20:32:37 2011 Time server ntp1.dlink.com is at IP address 61.67.210.241
[INFO] Wed Jan 26 20:32:33 2011 WAN interface speed measurement aborted as they did not converge
[INFO] Wed Jan 26 20:32:32 2011 Estimating speed of WAN interface
[INFO] Wed Jan 26 20:32:32 2011 PPP network up with IP Address 99.162.254.120
[INFO] Wed Jan 26 20:32:32 2011 LCP sets local options: ACCM: 00000000, ACFC: 1, PFC: 0, MRU: 1492
[INFO] Wed Jan 26 20:32:32 2011 LCP sets remote auth: C023
[INFO] Wed Jan 26 20:32:32 2011 LCP sets remote options: ACCM: FFFFFFFF, ACFC: 1, PFC: 0, MRU: 1492
[INFO] Wed Jan 26 20:32:32 2011 Established INTERNET PPPoE connection, session id 1362
[INFO] Wed Jan 26 20:32:32 2011 Issuing request for offer for INTERNET PPPoE Session
[INFO] Wed Jan 26 20:32:32 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:32:32 2011 Offer of service [any] accepted for INTERNET PPPoE Session
[INFO] Wed Jan 26 20:32:32 2011 Discovering PPPoE servers for INTERNET PPPoE Session
[INFO] Wed Jan 26 20:32:32 2011 Trying to establish INTERNET PPPoE connection
[INFO] Wed Jan 26 20:32:31 2011 Log viewed by IP address 192.168.0.199
[CRIT] Wed Jan 26 20:32:14 2011 INTERNET PPPoE session timed out waiting for connection.  Connection attempt failed.
[INFO] Wed Jan 26 20:32:10 2011 Log viewed by IP address 192.168.0.199
[INFO] Wed Jan 26 20:32:08 2011 Issuing request for offer for INTERNET PPPoE Session
[INFO] Wed Jan 26 20:32:02 2011 Above message repeated 5 times
[INFO] Wed Jan 26 20:32:02 2011 Offer of service [any] accepted for INTERNET PPPoE Session
[INFO] Wed Jan 26 20:32:02 2011 Discovering PPPoE servers for INTERNET PPPoE Session
[INFO] Wed Jan 26 20:32:02 2011 Trying to establish INTERNET PPPoE connection
[INFO] Wed Jan 26 20:31:32 2011 PPP network down
[INFO] Wed Jan 26 20:31:32 2011 INTERNET PPPoE session protocol fault.  Connection attempt failed.
[INFO] Wed Jan 26 20:31:16 2011 Log viewed by IP address 192.168.0.199
[INFO] Wed Jan 26 20:31:13 2011 Allowed configuration authentication by IP address 192.168.0.199
[WARN] Wed Jan 26 20:30:25 2011 A network computer never renewed its 'lease' of 192.168.0.171 and has lost its right to use that address.  If the device continues to use that address it may cause IP address conflicts.
[INFO] Wed Jan 26 20:26:16 2011 Blocked incoming TCP packet from 216.252.125.64:443 to 99.162.255.22:50043 as RST received but there is no active connection
[INFO] Wed Jan 26 20:26:16 2011 Blocked incoming TCP packet from 216.252.125.65:443 to 99.162.255.22:50037 as RST received but there is no active connection
[INFO] Wed Jan 26 20:24:55 2011 Administrator logout
[INFO] Wed Jan 26 20:21:35 2011 Blocked incoming ICMP packet (ICMP type from 64.140.23.214 to 99.162.255.22
[INFO] Wed Jan 26 20:21:35 2011 Blocked incoming ICMP packet (ICMP type from 209.221.27.243 to 99.162.255.22
[INFO] Wed Jan 26 20:20:39 2011 Blocked incoming ICMP packet (ICMP type from 64.140.23.214 to 99.162.255.22
[INFO] Wed Jan 26 20:20:39 2011 Blocked incoming ICMP packet (ICMP type from 209.221.27.243 to 99.162.255.22
[INFO] Wed Jan 26 20:19:55 2011 Log viewed by IP address 192.168.0.199
[INFO] Wed Jan 26 20:19:29 2011 Above message repeated 2 times
[INFO] Wed Jan 26 20:19:26 2011 Allowed configuration authentication by IP address 192.168.0.199
[INFO] Wed Jan 26 20:15:01 2011 Log viewed by IP address 192.168.0.199
[INFO] Wed Jan 26 20:14:46 2011 Above message repeated 2 times
[INFO] Wed Jan 26 20:14:43 2011 Allowed configuration authentication by IP address 192.168.0.199
[INFO] Wed Jan 26 20:13:51 2011 Blocked incoming TCP connection request from 125.56.208.187:49516 to 99.162.255.22:49654
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:49 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:48 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 124.40.51.159:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Above message repeated 1 times
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 124.40.51.142:3478 to 99.162.255.22:55446
[INFO] Wed Jan 26 20:13:47 2011 Blocked incoming UDP packet from 125.56.208.194:3478 to 99.162.255.22:55446

[robertMN]

Cloning the computer MAC address, is that necessary for DSL?  I know it is for comcast.
I have Qwest DSL and my computer's mac address is not cloned to my knowledge.

[hajekmarek]

I can certainly reset the router as before and not clone the MAC address. I didn't think it matters whether the ISP sees my PC's MAC address or the router's MAC address but have chosen to be cautious and clone the PC MAC address in case the ISP noted my PC's mac address when I initially activated their DSL modem/router. I'll post the results after I let it run like that for a day or so.

[FurryNutz]

I wouldn't clone the Mac address as most DSL operators don't require it. They only want to be able to see the DSL modem to check the status, send any FW updates if needed and to troubleshoot if needed. They really don't care whats behind the router.

You seem to post alot of information with your log so no wonder why you got a warning. If you have additional information, just post in another message. Spaces in the logs also count for data thus take up room.

You said "No primary or secondary DNS". These need to be filled in on the 655 router. So the router can pass this information to the PCs and then the browser will connect and get internet data correctly. Find the Primary and 2ndary DNS addresses from your ISP and put them in. Sometimes they should auto fill but sometimes they don't.

If your 655 is not a rev B, check and see if you have Automatic DNS Services options. Turn this feature OFF.

Let us know how it goes.

[hajekmarek]

I suspect the forum limits message length to 2,000 characters and not to 20,000 characters like the message said.

I've reset the router and did not clone the MAC address this time.
I also filled in the Primary and Secondary DNS IP addresses.

I am continuing to experience connection drops...not sure what to do at this point. The drops sometimes happen every 10 or 20 minutes. What exactly causes the message "INTERNET PPPoE session protocol fault.  Connection attempt failed." ?

Could there be some possible conflict with DIR-655 and the new ADSL2+ version of DSL? I am not sure which one my ISP uses but the DSL modem/router is ADSL2+ router(of course operating in bridged mode). I was running an older speedstream 5100 DSL modem (only) for a week or so at nearly 6 MB/s until AT&T delivered the new ADSL2+ modem/router and don't recall having any weird issues like this.

The latest log once again.

[INFO] Thu Jan 27 21:13:48 2011 Time synchronized
[INFO] Thu Jan 27 21:13:49 2011 Requesting time from 61.67.210.241
[INFO] Thu Jan 27 21:13:49 2011 Time server ntp1.dlink.com is at IP address 61.67.210.241
[INFO] Thu Jan 27 21:13:49 2011 Requesting time from 74.80.219.11
[INFO] Thu Jan 27 21:13:49 2011 Time server ntp1.dlink.com is at IP address 74.80.219.11
[INFO] Thu Jan 27 21:13:48 2011 Blocked outgoing TCP packet from 192.168.0.199:50070 to 64.4.61.217:1863 as PSH:ACK received but there is no active connection
[INFO] Thu Jan 27 21:13:45 2011 WAN interface speed measurement aborted as they did not converge
[INFO] Thu Jan 27 21:13:44 2011 Estimating speed of WAN interface
[INFO] Thu Jan 27 21:13:44 2011 PPP network up with IP Address 99.162.254.31
[INFO] Thu Jan 27 21:13:43 2011 LCP sets local options: ACCM: 00000000, ACFC: 1, PFC: 0, MRU: 1492
[INFO] Thu Jan 27 21:13:43 2011 LCP sets remote auth: C023
[INFO] Thu Jan 27 21:13:43 2011 LCP sets remote options: ACCM: FFFFFFFF, ACFC: 1, PFC: 0, MRU: 1492
[INFO] Thu Jan 27 21:13:43 2011 Established INTERNET PPPoE connection, session id 14923
[INFO] Thu Jan 27 21:13:43 2011 Issuing request for offer for INTERNET PPPoE Session
[INFO] Thu Jan 27 21:13:43 2011 Above message repeated 1 times
[INFO] Thu Jan 27 21:13:43 2011 Offer of service [any] accepted for INTERNET PPPoE Session
[INFO] Thu Jan 27 21:13:43 2011 Discovering PPPoE servers for INTERNET PPPoE Session
[INFO] Thu Jan 27 21:13:43 2011 Trying to establish INTERNET PPPoE connection
[INFO] Thu Jan 27 21:13:37 2011 Log viewed by IP address 192.168.0.199
[CRIT] Thu Jan 27 21:13:26 2011 INTERNET PPPoE session timed out waiting for connection.  Connection attempt failed.
[INFO] Thu Jan 27 21:13:19 2011 Discovering PPPoE servers for INTERNET PPPoE Session
[INFO] Thu Jan 27 21:13:13 2011 Above message repeated 5 times
[INFO] Thu Jan 27 21:13:13 2011 Trying to establish INTERNET PPPoE connection
[INFO] Thu Jan 27 21:12:43 2011 PPP network down
[INFO] Thu Jan 27 21:12:43 2011 INTERNET PPPoE session protocol fault.  Connection attempt failed.
[INFO] Thu Jan 27 21:12:31 2011 Log viewed by IP address 192.168.0.199

[FurryNutz]

By the looks of it, the router is doing what its supposed to however it's possible the ISP modem is not handing off or correctly getting the traffic through to the router, thus the router is timing out and dropping connection due to the possible ISP modem not getting the traffic through. Can you assess the logs on the modem and see if there are any errors or connection issues on the modem?

One other way of checking your router is if you have a friend or a neighbor close by that you can connect your router too for a test. See if this issue tracks.

[hajekmarek]

As a token of my appreciation for the replies to my problem I wanted to post what appears to be a solution to the problems I experienced for the last 6 weeks. I tried numerous combinations to resolve the problem over several weeks and in the end called AT&T who sent a technician over.

I tried connecting to the DSL with the DIR-655, then I bought another router (Belkin), and also directly connecting my PC to the DSL modem using the Westel DSL modem. Every combination yielded an intermittent drop in connectivity and the DSL light on the modem either blinking green or red.

Just to reiterate, my problems started when I upgraded my DSL service from 3Mb/s to 6Mb/s.

When the AT&T technician showed up he had a handheld tool that measured the throughput at the phone box outside my house and then at the modem. He said he saw a significant drop in connection speed (25% drop) inside the house and that the problem is most likely the wiring in the house. After talking with him a bit he gave me a DSL filter that is mounted outside the house.

So, the problem appeared to be high impedance in the lines in my house. At this point two and two came together. It is not unusual for a signal to go through at 3Mb/s but not at 6Mb/s due to the impedance in the line. My background is i electrical engineering and this finally made sense.

I went onto switching the wiring at the phone outlets in the house in the following manner.

All phones now use a pair of wires (orange & orange stripe) without a DSL filter and hook up to the DSL filter mounted at the box outside my house. Then, the two wires coming from the filter is connected to the incoming phone lines from the street.
I dedicated another pair of wires (blue & blue stripe) to the DSL phone jack. This way the phone and DSL are not talking on the same pair of wires inside my house. The DSL modem plugs directly into the phone jack without the filter-splitter. The pair of wires attached directly to the incoming phone lines from the street. This is where the DSL lines and the phone lines (that pass through the filter) meet.

Previously, I experienced a drop in connection as often as every 10 minutes. After I rewired, I haven’t had a drop in connection since (ok, it’s only 36 hours so far).

So, to those folks that experience a similar problem after upgrading connection speed, it is quite possible your router is working perfectly but your wiring inside the house won’t support it. Your DSL provider can send out a technician to measure your connection outside and inside the house and from what I understand they’ll do this free of charge. See what he finds out. I battled with this for six weeks, resetting the modem and router at least 30 times, along the way tried not to give in and blame AT&T or DLink which was not easy given some of the flaming comments I’ve seen for both providers. I am not a fan of AT&T considering how much wrong information I’ve gotten from customer service and the way they mis-schedule appointments but DLink has helped me in the past pretty well.

I wanted to mention one more thing. How to configure the DIR-655 and the Westell DSL/Router modem, SKU: F90-610025-06. Since the DSL device is a router/modem you have two choices of configuration. (1) As a DSL modem & router (2) In bridged mode as a DSL modem only. I’ve used both configurations successfully.

(1) As a modem/router you configure the modem exactly as you would if you were connecting directly to the PC. Then, reset the router to factory setting via the pinhole on the back of the router held for 20 seconds or so (this is actually important as the router must save some measurements it performs on the line that only seem to be resettable this way).
Go to the internet configuration of the router and select Setup –> Internet –> Manual Internet Connection Setup
Select Dynamic IP (DHCP)
Enter primary and secondary DNS from your provider
Set the MTU to the same value the Westel modem is set to. In my case it was 1492.
Save settings and reboot router.

(2) As a modem, set the Westell DSL/Router to bridged mode.
Then, reset the router to factory setting via the pinhole on the back of the router held for 20 seconds or so (this is actually important as the router must save some measurements it performs on the line that only seem to be resettable this way).
Go to the internet configuration of the router and select Setup –> Internet –> Manual Internet Connection Setup
Select PPPoE
Enter your login and password you have with your DSL provider.
Enter primary and secondary DNS from your provider.
Set the MTU to the same value the Westel modem was set to. In my case it was 1492. Save settings and reboot router.

Good luck!

[FurryNutz]

Good to hear you found the issue. Sorry you had to go thru all that with your ISP. This isn't the first time I've seen this. Helped my buddy with his ISP on DSL. They had him 9000ft beyond signal speed limits on his line and to make it worse the lines at the phone pole going into the house were not set up or filter correctly and were actually feeding back on to a different line. After months, a tech finally noticed the problems and got him set up correctly. Was never the router as claimed by the ISP.

Always check the ISP lines going to the house, then check the ISP Modem, then check the router I always say. Glad you got it all working.