Jump to content

DSL Modem/ Connection, hosed? or just need to tweak?


Recommended Posts

I've attached my modem logs as they currently are, seems like tonight its especially bad, I've been concerned lately with the overwhelming number of "DNS Query failed" entries they seem to be almost flooding the logs at times but these other errors are completely new and I've never seen them on in the logs before. I have tried changing the modem to use the google public DNS and Ive tried using the ones that our ISP auto assigns, it seems to have no bearing on the DNS issue. Our connection seems to be unstable at times, I don't know if the whole thing is hosed or if there is just some setting that needs changing or what but i'd rather take my chances here than bother with our ISP's support, its a small , local ISP and they are about as helpful as a .jpg is to Helen Keller.

 

Any help or ideas as to what the [email protected]#$ is going on would be greatly appreciated

Date/Time	Facility	Severity	Message
Feb 9 22:28:18	user	warn	dnsprobe[1436]: dns query failed 
Feb 9 22:34:33	user	warn	dnsprobe[1436]: dns query failed 
Feb 9 22:39:14	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 16:28:24	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 16:28:57	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:09:16	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:33:36	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:35:11	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:35:44	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:36:48	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:37:21	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:37:54	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:38:58	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:40:02	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:41:06	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:42:42	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:43:15	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:44:50	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:46:25	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:49:02	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:51:08	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:53:14	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:53:47	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 18:55:22	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 19:00:03	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 19:00:05	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 19:00:07	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 19:02:44	user	warn	dnsprobe[1436]: dns query failed 
Feb 11 19:02:46	user	warn	dnsprobe[1436]: dns query failed 
Feb 12 06:59:43	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 02:23:20	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 02:25:57	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 02:25:59	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 03:47:11	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 03:49:17	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 03:59:08	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:08:28	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:09:33	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:10:06	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:16:51	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:17:55	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:22:36	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:27:17	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:31:28	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:31:30	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:35:39	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:49:40	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:51:14	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 04:52:49	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:01:39	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:05:49	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:05:51	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:07:26	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:07:28	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:11:07	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:14:46	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:19:28	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:23:38	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:23:40	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:24:13	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:28:23	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:28:56	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:32:04	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:32:06	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:34:12	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:36:18	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:36:51	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 05:38:26	user	warn	dnsprobe[1436]: dns query failed 
Feb 13 21:40:57	user	warn	dnsprobe[1436]: dns query failed 
Feb 14 04:51:07	user	warn	dnsprobe[1436]: dns query failed 
Feb 14 12:17:16	user	warn	dnsprobe[1436]: dns query failed 
Feb 14 12:18:52	user	warn	dnsprobe[1436]: dns query failed 
Feb 16 02:19:30	user	warn	dnsprobe[1436]: dns query failed 
Feb 16 19:41:32	user	warn	dnsprobe[1436]: dns query failed 
Feb 19 02:15:17	user	warn	dnsprobe[1436]: dns query failed 
Feb 19 02:15:19	user	warn	dnsprobe[1436]: dns query failed 
Feb 19 09:24:54	user	warn	dnsprobe[1436]: dns query failed 
Feb 19 23:17:44	user	warn	dnsprobe[1436]: dns query failed 
Feb 20 01:55:25	user	warn	dnsprobe[1436]: dns query failed 
Feb 20 22:11:14	user	crit	kernel: OAM loopback response not received on VPI/VCI 0/35. 
Feb 20 22:11:15	user	crit	kernel: OAM loopback response not received on VPI/VCI 0/35. 
Feb 20 22:17:29	user	crit	kernel: OAM loopback response not received on VPI/VCI 0/35. 
Feb 20 22:17:31	user	crit	kernel: OAM loopback response not received on VPI/VCI 0/35. 
Feb 21 10:28:25	user	warn	dnsprobe[1436]: dns query failed 
Feb 21 11:07:14	user	warn	dnsprobe[1436]: dns query failed 
Feb 24 04:15:49	user	warn	dnsprobe[1436]: dns query failed 
Feb 24 04:33:58	user	warn	dnsprobe[1436]: dns query failed 
Feb 24 15:25:18	user	warn	dnsprobe[1436]: dns query failed 
Feb 25 00:00:41	user	warn	dnsprobe[1436]: dns query failed 
Feb 25 04:17:39	user	warn	dnsprobe[1436]: dns query failed 
Feb 25 10:36:31	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:38:19	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:38:19	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:38:22	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:38:23	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:38:28	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:38:29	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:40:09	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:40:09	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:40:12	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:40:13	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:40:18	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:40:19	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:46:46	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:46:46	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:46:49	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:46:49	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:46:55	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 10:46:56	user	warn	kernel: 201.21.105.190 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:14:56	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:14:56	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:14:59	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:15:00	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:15:05	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:15:06	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:16:32	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:16:32	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:16:32	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:16:35	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:16:35	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:16:41	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:16:42	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:21:19	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:21:19	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:21:22	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:21:22	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:21:28	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 11:21:28	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 12:12:02	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 12:12:02	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 12:12:05	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 12:12:05	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 12:12:11	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 12:12:11	user	warn	kernel: 200.232.248.148 sent an invalid ICMP type 3, code 0 error to a broadcast: 0.0.0.0 on ppp_0_35_1 
Feb 25 12:15:18	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:16:35	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:20:33	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:35:57	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:38:54	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:40:35	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:42:14	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:43:32	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:45:50	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:47:43	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:50:23	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:51:57	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:55:01	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:55:13	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:55:37	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 12:57:40	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:00:24	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:11:43	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:14:36	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:18:29	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:20:03	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:22:51	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:24:40	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:25:57	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:29:29	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:31:00	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:34:40	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:36:27	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:37:28	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:40:27	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:44:19	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:45:28	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 13:49:22	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 14:05:19	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 14:08:15	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 14:13:14	user	err	kernel: ipt_tcpmss_target: bad length (41 bytes) 
Feb 25 16:12:36	user	warn	dnsprobe[1436]: dns query failed 
Feb 25 17:33:17	user	warn	dnsprobe[1436]: dns query failed 
Feb 25 22:14:16	user	crit	kernel: OAM loopback response not received on VPI/VCI 0/35. 
Feb 25 22:14:18	user	crit	kernel: OAM loopback response not received on VPI/VCI 0/35. 
Edited by CA3LE
removed .doc and included info within post
Link to post
Share on other sites

Google DNS has been litterally 100% reliable for me (Google Public DNS IPs are 8.8.8.8 and 8.8.4.4 in case anyone needs that info - make the changes on your router so it will be global to all clients resolving to the router IP for DNS) - I'd normally suggest that... but you've tried that.  So I guess I can't blame the other DNS server.  <_<

 

What operating system?  What ISP?  Are only some addresses not resolving?  Is it intermittent?

 

Quote of the day...  :evil6:

"...its a small , local ISP and they are about as helpful as a .jpg is to Helen Keller." Lee Yokum

Link to post
Share on other sites

Yea love that hellen keller reference lol

 

The ICMP warnings appear to be caused by something on your network (possibly internal yet doubtful due to the DNS errors) sending data to no real address. This would account for the DNS issues if it were coming from your ISP, which as you state is having issues.

 

However if I remember correctly the error " kernel: OAM loopback response not received on VPI/VCI 0/35 " explains the connection is down at the ISP end. The vpi/vci 0/35 - circuit is hopefully the correct one.

 

I might change the VPI/VCI circuits to the following ~

post-9745-0-34485800-1393445924.png

 

Make sure I have correctly found your provider as "telefonica" before changing.

 

As I understand this will be a secondary channel for doing many "things" the ISP might need or want to do.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...