- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have just about had it. I have to hurry cause my dsl will probably go out again. It has cut out about 5 times since 6am this am.
Attached is a log that was done earlier. the time is 1 hour behind. I'm going nuts. Support is useless. I spent 2 hrs last week and got no where.
Jan 17 07:35:12 | user.err | syslog: | Unexpected message received on UDP port 137 (opcode=0,resp=0,len=50) |
Jan 17 07:33:10 | user.err | syslog: | Unexpected message received on UDP port 137 (opcode=0,resp=0,len=50) |
Jan 17 07:32:56 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.34 50:ea:d6:4d:1b:3b EHKs-iPhone |
Jan 17 07:32:56 | daemon.info | dnsmasq[315]: | DHCPREQUEST(br0) 192.168.1.34 50:ea:d6:4d:1b:3b |
Jan 17 07:29:01 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.46 e0:b9:a5:1e:d8:f0 Asus |
Jan 17 07:29:01 | daemon.info | dnsmasq[315]: | DHCPINFORM(br0) 192.168.1.46 e0:b9:a5:1e:d8:f0 |
Jan 17 07:29:01 | user.err | syslog: | WSTLIB_HTTP: protocol error |
Jan 17 07:25:23 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.46 e0:b9:a5:1e:d8:f0 Asus |
Jan 17 07:25:23 | daemon.info | dnsmasq[315]: | DHCPINFORM(br0) 192.168.1.46 e0:b9:a5:1e:d8:f0 |
Jan 17 07:22:14 | user.err | syslog: | Unexpected message received on UDP port 137 (opcode=0,resp=0,len=50) |
Jan 17 07:22:13 | user.err | syslog: | WSTLIB_HTTP: protocol error |
Jan 17 07:18:58 | user.err | syslog: | WSTLIB_HTTP: protocol error |
Jan 17 07:18:11 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.34 50:ea:d6:4d:1b:3b EHKs-iPhone |
Jan 17 07:18:11 | daemon.info | dnsmasq[315]: | DHCPREQUEST(br0) 192.168.1.34 50:ea:d6:4d:1b:3b |
Jan 17 07:06:52 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.34 50:ea:d6:4d:1b:3b EHKs-iPhone |
Jan 17 07:06:52 | daemon.info | dnsmasq[315]: | DHCPREQUEST(br0) 192.168.1.34 50:ea:d6:4d:1b:3b |
Jan 17 07:05:35 | user.err | syslog: | WSTLIB_HTTP: protocol error |
Jan 17 07:03:21 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.34 50:ea:d6:4d:1b:3b EHKs-iPhone |
Jan 17 07:03:21 | daemon.info | dnsmasq[315]: | DHCPREQUEST(br0) 192.168.1.34 50:ea:d6:4d:1b:3b |
Jan 17 06:53:53 | user.err | syslog: | WSTLIB_HTTP: protocol error |
Jan 17 06:53:12 | user.err | syslog: | WSTLIB_HTTP: protocol error |
Jan 17 06:52:51 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.34 50:ea:d6:4d:1b:3b EHKs-iPhone |
Jan 17 06:52:51 | daemon.info | dnsmasq[315]: | DHCPREQUEST(br0) 192.168.1.34 50:ea:d6:4d:1b:3b |
Jan 17 06:50:39 | user.err | syslog: | WSTLIB_HTTP: protocol error |
Jan 17 06:48:31 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.34 50:ea:d6:4d:1b:3b EHKs-iPhone |
Jan 17 06:48:31 | daemon.info | dnsmasq[315]: | DHCPREQUEST(br0) 192.168.1.34 50:ea:d6:4d:1b:3b |
Jan 17 06:38:20 | user.err | syslog: | Unexpected message received on UDP port 137 (opcode=0,resp=0,len=50) |
Jan 17 06:36:14 | user.err | syslog: | Unexpected message received on UDP port 137 (opcode=0,resp=0,len=50) |
Jan 17 06:36:13 | user.err | syslog: | WSTLIB_HTTP: protocol error |
Jan 17 06:32:17 | user.err | syslog: | Unexpected message received on UDP port 137 (opcode=0,resp=0,len=50) |
Jan 17 06:32:17 | user.err | syslog: | WSTLIB_HTTP: protocol error |
Jan 17 06:31:15 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.46 e0:b9:a5:1e:d8:f0 Asus |
Jan 17 06:31:15 | daemon.info | dnsmasq[315]: | DHCPINFORM(br0) 192.168.1.46 e0:b9:a |
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
#1 In the logs, I saw the term Asus.
What is the brand and model of that device?
#2 What is the brand and model of your router?
#3 What is the brand and model of the device that, you are showing part of the logs from?
#4 What is the brand and model of your modem?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Asus Laptop Model G73S
My modem/router provided by Verizon is the westell 7500
The log came from Verizon Gateway. Inputing my IP, it comes up. It's a great way to monitor.
Here is a more up to date log:
Jan 17 15:21:09 | daemon.info | dnsmasq[315]: | DHCPACK(br0) 192.168.1.46 e0:b9:a5:1e:d8:f0 Asus |
Jan 17 15:21:09 | daemon.info | dnsmasq[315]: | DHCPINFORM(br0) 192.168.1.46 e0:b9:a5:1e:d8:f0 |
Jan 17 15:19:46 | daemon.notice | pppd[3325]: | Westell PPP Environment:device:nas1 linkname:config0 iplocal:96.233.2.189 ipremote:10.9.67.1 ppplogname:root orig_uid:0 connect_time:380128633 bytes_sent:26847179 bytes_rcvd:103511093 usepeerdns:1 dns1:71.243.0.12 dns2:71.250.0.12 |
Jan 17 15:19:46 | daemon.warn | pppd[3325]: | pppd[3325] EXIT_PPPOE_TIMEOUT_PADO caused InternetFail light to be lit |
Jan 17 15:19:46 | daemon.notice | pppd[3325]: | PPPD Exit Status changed EXIT_OK->EXIT_PPPOE_TIMEOUT_PADO during phase PHASE_SERIALCONN->PHASE_HOLDOFF |
Jan 17 15:19:46 | daemon.notice | pppd[3325]: | Westell phase_hook PHASE=PHASE_HOLDOFF(11) |
Jan 17 15:19:46 | daemon.notice | pppd[3325]: | Westell Random Holdoff returning 449 seconds |
Jan 17 15:19:46 | daemon.warn | pppd[3325]: | Leaving destroy_pppoesessionfile |
Jan 17 15:19:46 | daemon.err | pppd[3325]: | Unlinking PPPoE session file:/WFIO/ppp-config0 |
Jan 17 15:19:46 | daemon.warn | pppd[3325]: | Enter destroy_pppoesessionfile |
Jan 17 15:19:46 | daemon.err | pppd[3325]: | Unable to complete PPPoE Discovery |
Jan 17 15:19:46 | daemon.warn | pppd[3325]: | Timeout waiting for PADO packets |
Jan 17 15:19:46 | daemon.warn | pppd[3325]: | waitForPADO: timed out |
Jan 17 15:19:36 | daemon.warn | pppd[3325]: | waitForPADO: timed out |
Jan 17 15:19:31 | daemon.warn | pppd[3325]: | waitForPADO: timed out |
Jan 17 15:19:26 | daemon.notice | pppd[3325]: | Westell PPP Environment:device:nas1 linkname:config0 iplocal:96.233.2.189 ipremote:10.9.67.1 ppplogname:root orig_uid:0 connect_time:380128633 bytes_sent:26847179 bytes_rcvd:103511093 usepeerdns:1 dns1:71.243.0.12 dns2:71.250.0.12 |
Jan 17 15:19:26 | daemon.notice | pppd[3325]: | PPPD Exit Status changed EXIT_USER_REQUEST->EXIT_OK during phase PHASE_DORMANT->PHASE_SERIALCONN |
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
#1 Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that the final hop (bottom-most line of the trace) will contain a hop with your IP address in it. Remove that line. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.
#2 Can you provide the Transceiver Statistics from your modem?
1: If you see a Blue and White Westell page, mouse over Troubleshooting, go to DSL, and choose Transceiver Statistics. Copy/Paste the information on that page.
2: Otherwise: Go to System Monitoring > Advanced Monitors > Transceiver Statistics. Copy/Paste the information on that page.
3: Try visiting http://192.168.1.1/transtat.htm which is a direct link to the Stats on older modems.
If you need a Username and Password, try the following:
admin/password
admin/password1
admin/admin
admin/admin1
admin/Serial Number.
By Serial Number, I don't mean type in the words Serial Number. I mean find and type in the serial number found on the bottom of this router.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Transceiver stats:
Transceiver Statistics |
| |||||||||||||||
|
Internet up
news.giganews.com
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 xe-2-3-0.er1.iad10.us.above.net (209.66.64.189) 0 ms 0 ms 0 ms
3 xe-0-0-0.er2.iad10.us.above.net (64.125.26.234) 0 ms 0 ms 0 ms
4 above-uu.iad10.us.above.net (64.125.13.174) 0 ms 0 ms 0 ms
5 0.ae1.RES-BB-RTR2.verizon-gni.net (152.63.32.157) 1 ms 2 ms 2 ms
6 P12-0-0.BSTNMA-LCR-06.verizon-gni.net (130.81.29.175) 18 ms 16 ms 16 ms
7 P9-0.BSTNMA-LWRNMACA-ERXG02.verizon-gni.net (130.81.33.175) 21 ms 18 ms 20 ms
8 * * *
9 * * *
10 * * *
Max number of unresponsive hops reached (firewall or filter?)
I hope this is what you need. I could not find troubleshooting for the westell. The only thing I found was finding if an firmware update is available. Cant find that either.
Thank you so much for your follow up.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content