[opensuse] Re: Periodic problem resolving URLs?
Clayton a écrit :
perfectly... only resolving URLs fails.
I don't know if the MTU change will help you. I don't understand why it should only once on a while... it looks for me like a DNS outage. The provider Domain Name service is out of order (may be rebooting). Try using an other one as secondary any URL already soled (that is with known IP) have no problem It's easy to test, just use ping and see if the IP works and the URL don't (of course with written down known URL) I have also this problem from time to time jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I don't know if the MTU change will help you. I don't understand why it should only once on a while...
That's what has caught me up too. It's once in a while.. not all the time, and not always one particular site. When it happens, it's all websites...
it looks for me like a DNS outage. The provider Domain Name service is out of order (may be rebooting). Try using an other one as secondary
Right, but you'd think then that the ISP would report it as a DNS outage when I contact them about it... and since it's been happen for at least 8 weeks now... I'd expect customers to be complaining. :-P
any URL already soled (that is with known IP) have no problem
It's easy to test, just use ping and see if the IP works and the URL don't (of course with written down known URL)
This is the next step. Write down the IP address of some website... eg google.com and then when I get the dropout go direct via IP address. This is interesting though so far... I've learned about MTUs ;-) C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 16 Sep 2009 13:46:22 Clayton wrote:
Right, but you'd think then that the ISP would report it as a DNS outage when I contact them about it... and since it's been happen for at least 8 weeks now... I'd expect customers to be complaining. :-P
A lot of ISP's will just use the easy way out to keep from getting egg on their faces and say it's your end at fault when it is so plainly their DNS that has kicked the can . I have had that with BT , FreeNet, Orange , the older Onet, and a few others i cant remember the names of now . Pete .
Guys, It is almost trivial to run your own dns caching server. Just a few clicks in yast. And it really does not use that much ram / cpu. I have it running on one of my servers with about 20 workstations pointed at it. It is currently only using 18megs of ram and about 75megs is paged out to swap space. And that server has been up for 146 days, so this is in the fully operational mode. Assuming you have the ram to work with, if your ISP is unreliable for dns services you should consider just running your own without even forwarding requests to your ISP. In a small business environment like mine, even if the ISP is reliable you should be running your own local dns primary and backup caching server. And they should be setup to forward requests that can't answer locally to the ISPs dns server. That way if you keep needing to lookup the same domain name repeatedly, the traffic all stays within your local network. You only have to ask the ISPs dns server for new info. And by using the forwarding aspect, you get to leverage the fact the ISPs dns should have a lot more info in its cache than your server does. Thus the dns traffic on the internet is cutdown by having a couple tiers of dns servers like that. The only bad part is your local dns servers need to be machines that run 24 hours a day, or at least any time a user might need to be doing a dns query. For a home user with a single suse box, this is easy. You just have named (dns) start as a daemon during startup. And if you have a reliable ISP dns server, forward unanswered requests to it. If it is not reliable, then don't forward at all. That means unanswered requests cause direct queries out to the various domain dns servers. Note: I guess it is possible an ISP would firewall off outbound dns requests, but I've never had that problem. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer Preservation and Forensic processing of Exchange Repositories White Paper - <http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html> The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I don't know if the MTU change will help you. I don't understand why it should only once on a while...
That's what has caught me up too. It's once in a while.. not all the time, and not always one particular site. When it happens, it's all websites...
The plot thickens. I'm beginning to wonder if it's actually my ISP after all. I just had another outage where I was not able to load any websites, but other web services continued to work as normal. During that "outage" I attempted to connect to my Netgear router using the usual 192.168.1.1 IP address... nothing. no connect until web access (being able to connect to websites) returned. Then i was able to log into and browse my router config. So... nothing has changed in my router config prior to this problem appearing. It's the same config I've used for the last 2 years. On the PC side, I've recently added a new hard drive and done a clean install of 11.1 using the defaults... clean /home as well. It's looking likely that the problem is inside the local network (all of 2 computers)... but where to look next? Hmmm this is an odd problem. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu September 17 2009 4:41:14 pm Clayton wrote:
The plot thickens. I'm beginning to wonder if it's actually my ISP after all. I just had another outage where I was not able to load any websites, but other web services continued to work as normal. During that "outage" I attempted to connect to my Netgear router using the usual 192.168.1.1 IP address... nothing. no connect until web access (being able to connect to websites) returned. Then i was able to log into and browse my router config.
So... nothing has changed in my router config prior to this problem appearing. It's the same config I've used for the last 2 years. On the PC side, I've recently added a new hard drive and done a clean install of 11.1 using the defaults... clean /home as well.
It's looking likely that the problem is inside the local network (all of 2 computers)... but where to look next? Hmmm this is an odd problem.
To be sure, try adding OpenDNS, which is free and fast. The OpenDNS nameservers are 208.67.222.222 and 208.67.220.220. --- Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
I don't know if the MTU change will help you. I don't understand why it should only once on a while...
That's what has caught me up too. It's once in a while.. not all the time, and not always one particular site. When it happens, it's all websites...
The plot thickens. I'm beginning to wonder if it's actually my ISP after all. I just had another outage where I was not able to load any websites, but other web services continued to work as normal. During that "outage" I attempted to connect to my Netgear router using the usual 192.168.1.1 IP address... nothing. no connect until web access (being able to connect to websites) returned. Then i was able to log into and browse my router config.
So... nothing has changed in my router config prior to this problem appearing. It's the same config I've used for the last 2 years. On the PC side, I've recently added a new hard drive and done a clean install of 11.1 using the defaults... clean /home as well.
It's looking likely that the problem is inside the local network (all of 2 computers)... but where to look next? Hmmm this is an odd problem.
C.
Hmmm, sounds like the hard-slog route to solve.... NIC sitting firmly in the sockets, cables OK, is it the router (direcxt connect to the modem), is it the modem...? Good luck :-) . BC -- Once, in the wilds of Afghanistan, I lost my corkscrew and we were forced to live on nothing but food and water for days. W C Fields. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
Clayton wrote:
I don't know if the MTU change will help you. I don't understand why it should only once on a while...
That's what has caught me up too. It's once in a while.. not all the time, and not always one particular site. When it happens, it's all websites...
The plot thickens. I'm beginning to wonder if it's actually my ISP after all. I just had another outage where I was not able to load any websites, but other web services continued to work as normal. During that "outage" I attempted to connect to my Netgear router using the usual 192.168.1.1 IP address... nothing. no connect until web access (being able to connect to websites) returned. Then i was able to log into and browse my router config.
So... nothing has changed in my router config prior to this problem appearing. It's the same config I've used for the last 2 years. On the PC side, I've recently added a new hard drive and done a clean install of 11.1 using the defaults... clean /home as well.
It's looking likely that the problem is inside the local network (all of 2 computers)... but where to look next? Hmmm this is an odd problem.
C.
Hmmm, sounds like the hard-slog route to solve.... NIC sitting firmly in the sockets, cables OK, is it the router (direcxt connect to the modem), is it the modem...? Good luck :-) .
BC
Just to follow-up on this. Which version of Firefox are you using - IF you are using FF? Both my wife and I have found some strange behaviour with FF (which I have been exclusively using sine the Netscape days) that recently we do not get pages appearing when selected. The usual "excuse" is that the URL cannot be accessed. Close down FF, start it again, and the wanted web page is loaded without a problem. This only started in the past couple of weeks (give or take - nobody really keeps daily notes, you know :-) .) BC -- Once, in the wilds of Afghanistan, I lost my corkscrew and we were forced to live on nothing but food and water for days. W C Fields. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Which version of Firefox are you using - IF you are using FF?
Firefox 3.5.3 as well as Seamonkey (latest) and others. It doesn't seem to be related directly to the browser. I still have to spend some time trying some of the recent suggestions. When this problem hits, it only seems to affect loading webpages in any browser... like port 80 was briefly closed or something. I have to dig deeper into the Router logs to see if there is something there... and also test the access to the router itself is actually interrupted or if it was co-incidental. Interesting about the Firefox thing. I might have to try downgrading to an earlier FF version... just to see if it makes a difference. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
Which version of Firefox are you using - IF you are using FF?
Firefox 3.5.3 as well as Seamonkey (latest) and others. It doesn't seem to be related directly to the browser.
I still have to spend some time trying some of the recent suggestions.
When this problem hits, it only seems to affect loading webpages in any browser... like port 80 was briefly closed or something.
So when you encounter this problem and you open a shell and do a DNS lookup with dig, it works? /Per -- Per Jessen, Zürich (19.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Which version of Firefox are you using - IF you are using FF?
Firefox 3.5.3 as well as Seamonkey (latest) and others. It doesn't seem to be related directly to the browser.
I still have to spend some time trying some of the recent suggestions.
When this problem hits, it only seems to affect loading webpages in any browser... like port 80 was briefly closed or something.
So when you encounter this problem and you open a shell and do a DNS lookup with dig, it works?
OK, just had it happen again. As soon as I had the dropout (while using Firefox), I started up SeaMonkey and tried browsing to several sites... the same there.. no connectivity. I opened a terminal and did a ======================== dig google.com ; <<>> DiG 9.5.0-P2 <<>> google.com ;; global options: printcmd ;; connection timed out; no servers could be reached ======================== I think the lack of connectivity to the router was a coincidence, as in the last 3 outages, I was able to contact the router directly via 192.168.1.1 and log into the router. After connectivity returned, dig google.com returned a "normal" result with details of the lookup. Through this outage, I was on a Skype call which was no interrupted, I was playing an online MMORPG game (very sensitive to network latency and timeouts/disconnects), I had a Torrent downloading/uploading, IRC (using Konversation) was not interrupted, and other services like Pidgin did not disconnect/reconnect. This only affected browsing to websites, and was duplicatable in more than one browser (ie not restricted to just FireFox). Next outage, I will also try to test in Konqueror and Opera as well. Oh, I also have a KDE4 widget that pings a few predefined websites every 2 minutes, and it also errors out when connectivity drops (ie it cannot ping the configured webservers, pinging on URL not IP address). I still have to properly test browsing direct to a IP instead of a URL on the next outage. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
OK, just had it happen again. As soon as I had the dropout (while using Firefox), I started up SeaMonkey and tried browsing to several sites... the same there.. no connectivity.
I opened a terminal and did a ======================== dig google.com
; <<>> DiG 9.5.0-P2 <<>> google.com ;; global options: printcmd ;; connection timed out; no servers could be reached ========================
Okay - next time, can you ping <any known address> ? Try 194.150.245.35. If that works, your internet connection is fine. Then try to ping your ISPs name-servers. If that works, try tcpdump on port 53 to see your DNS request going out - and maybe in. /Per -- Per Jessen, Zürich (16.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Okay - next time, can you ping <any known address> ? Try 194.150.245.35.
Pinging any known address outside of my LAN doesn't work during the outage.
If that works, your internet connection is fine. Then try to ping your ISPs name-servers. If that works, try tcpdump on port 53 to see your DNS request going out - and maybe in.
Pinging any address... even the ISP nameservers fails until the connection "returns". I'm going to try connecting another computer to the LAN, and then trying to catch the problem (in the 30 or 60 seconds of the outage) C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
Okay - next time, can you ping <any known address> ? Try 194.150.245.35.
Pinging any known address outside of my LAN doesn't work during the outage.
Okay, then at least you can forget any possible DNS problem. When your internet connection drops like this, it should be visible in your router log. I would expect to see evidence of the router login in again etc. /Per -- Per Jessen, Zürich (17.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Okay - next time, can you ping <any known address> ? Try 194.150.245.35.
Pinging any known address outside of my LAN doesn't work during the outage.
Okay, then at least you can forget any possible DNS problem. When your internet connection drops like this, it should be visible in your router log. I would expect to see evidence of the router login in again etc.
OK... but what confuses me about all this is it's not a 100% drop. Torrents are not interrupted, VoIP calls are not interrupted and there is no quality drop during a call while this is happening. Online gaming never hiccups either, and that is particularly susceptible to network latency and disconnects. Time to dig deeper into the firewall log... :-P C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
Okay - next time, can you ping <any known address> ? Try 194.150.245.35.
Pinging any known address outside of my LAN doesn't work during the outage.
Okay, then at least you can forget any possible DNS problem. When your internet connection drops like this, it should be visible in your router log. I would expect to see evidence of the router login in again etc.
OK... but what confuses me about all this is it's not a 100% drop. Torrents are not interrupted, VoIP calls are not interrupted and there is no quality drop during a call while this is happening. Online gaming never hiccups either, and that is particularly susceptible to network latency and disconnects.
Yet you can't ping anything or anyone? That would appear to suggest that ICMP traffic is blocked, whilst UDP and TCP keeps working .... weird. The question is - you say that torrents, voip and games are not interrupted, but do they all keep going? /Per -- Per Jessen, Zürich (15.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
OK... but what confuses me about all this is it's not a 100% drop. Torrents are not interrupted, VoIP calls are not interrupted and there is no quality drop during a call while this is happening. Online gaming never hiccups either, and that is particularly susceptible to network latency and disconnects.
Yet you can't ping anything or anyone? That would appear to suggest that ICMP traffic is blocked, whilst UDP and TCP keeps working .... weird. The question is - you say that torrents, voip and games are not interrupted, but do they all keep going?
Yes, that is correct.. during the 30 to 60 second outage, I cannot ping anyone outside my local LAN. I used several IPs that responded to pings while things were working normally. During an outage on Sunday it was as if I had pulled the CAT-5 out of the back of the PC... but during this same outage I was talking to a friend via Skype, and had a Torrent ISO downloading, as well as an online game running (WoW in Cedega to be specific). None of these experienced any dropouts at all.. only the browser/ping/traceroute/dig etc. This would be so much easier to trace down if it was a 100% dropout :-P Just for completeness, I've also rebooted the ADSL modem, the Router, and then the PC... just to see if there was some service running that was interrupting things. I haven't had time/opportunity to test a second computer connected to the router yet. I've set up a second machine running WindowsXP (to have a different OS environment to test with), and I hope that this evening I'll be able to try pings, web browsing etc from that second machine during an outage on the first. Maybe this will show something helpful... like if it also fails on the second machine, then the problem is likely in the router, modem or ISP... if it works, then the problem is likely to be something on the first machine. Also, I've noticed periodic short term (2 seconds or so) system freezes since the latest 11.1 re-install I've done.... that may or may not be related. I can't yet link the two events (a freeze with a loss of internet connectivity). I'm still poking through the messages log, trying to see if anything odd pops up. It's getting to the point that I'm seriously tempted to re-install again just to have that clean slate. :-P (I've had a lot of other annoying little issues since the latest reinstall.. like I still cannot get fetchmail to grab the mail from my host since the reinstall despite using the same config files as before, but that's another issue for another day). C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
OK... but what confuses me about all this is it's not a 100% drop. Torrents are not interrupted, VoIP calls are not interrupted and there is no quality drop during a call while this is happening. Online gaming never hiccups either, and that is particularly susceptible to network latency and disconnects.
Yet you can't ping anything or anyone? That would appear to suggest that ICMP traffic is blocked, whilst UDP and TCP keeps working .... weird. The question is - you say that torrents, voip and games are not interrupted, but do they all keep going?
Yes, that is correct.. during the 30 to 60 second outage, I cannot ping anyone outside my local LAN. I used several IPs that responded to pings while things were working normally.
Okay, so contrary to indication, your internet connection is still up when this happens. What happens if you do a "ping -n <known addr>" ? If that also doesn't work, try "traceroute -n <known addr>". If ICMPs for some reason are being dropped during one of these outages, the "ping -n" wont work either, but the "traceroute -n" might just show how far they do get. /Per -- Per Jessen, Zürich (16.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Okay, so contrary to indication, your internet connection is still up when this happens.
Exactly...
What happens if you do a "ping -n <known addr>" ? If that also doesn't work, try "traceroute -n <known addr>". If ICMPs for some reason are being dropped during one of these outages, the "ping -n" wont work either, but the "traceroute -n" might just show how far they do get.
OK, I think you are on to something here. I still want to test some more to be 100% sure though. I had 2 "outages" last night where I was at the computer (was busy with other things so didn't have a lot of time to test). During the outage, Skype was, as usual, connected, and a call was in progress. There was no interruption in the VoIP service, but web browsing did not work. I tried ping -n and got the same results as a regular ping (both to a URL and an IP)... no replies back. traceroute -n did produce results... a lot of lines with *'s and various IPs. I need to test this some more with known URL/IP combinations that reply normally and then hit them again during an outage to see the difference. I hope to be able to do this tonight. Is it possible that the dropped ICMPs could be a result of some misconfig on my end? I know little about ICMPs (I'm reading up on it though). C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
What happens if you do a "ping -n <known addr>" ? If that also doesn't work, try "traceroute -n <known addr>". If ICMPs for some reason are being dropped during one of these outages, the "ping -n" wont work either, but the "traceroute -n" might just show how far they do get.
[snip]
I tried ping -n and got the same results as a regular ping (both to a URL and an IP)... no replies back.
Okay. (the -n bit was just to switch off dns lookups).
traceroute -n did produce results... a lot of lines with *'s and various IPs.
Can you post some of the output perhaps?
I need to test this some more with known URL/IP combinations that reply normally and then hit them again during an outage to see the difference. I hope to be able to do this tonight.
Just use an IP address - using a hostname only causes DNS lookups, that we don't really care about. 194.150.245.35 = www.sbb.ch.
Is it possible that the dropped ICMPs could be a result of some misconfig on my end? I know little about ICMPs (I'm reading up on it though).
It is possible, but you said you got something through with the traceroute, so I think it's happening elsewhere. /Per -- Per Jessen, Zürich (17.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I tried ping -n and got the same results as a regular ping (both to a URL and an IP)... no replies back.
Okay. (the -n bit was just to switch off dns lookups).
traceroute -n did produce results... a lot of lines with *'s and various IPs.
Can you post some of the output perhaps?
Will do. I was going to post last night but I was not 100% certain that the results were during the outage... I want to test over more than one outage - not a problem since it happens fairly frequently. I have to wait until I'm home though... not sure I'll get valid results over a VNC connection.
Is it possible that the dropped ICMPs could be a result of some misconfig on my end? I know little about ICMPs (I'm reading up on it though).
It is possible, but you said you got something through with the traceroute, so I think it's happening elsewhere.
Yes, I am pretty certain the traceroute -n gave usable results... but I want to test a few more times to get a more accurate sample. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Can you post some of the output perhaps?
Will do. I was going to post last night but I was not 100% certain that the results were during the outage... I want to test over more than one outage - not a problem since it happens fairly frequently. I have to wait until I'm home though... not sure I'll get valid results over a VNC connection.
True to form, I had time last night to do more testing... and guess what... no problems or outages. Grrrr... maybe the ISP sorted out the prob? Naaah... probably not. I expect the problem will be back soon. That's the problem with chasing down an intermittent prob :-( C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Clayton wrote:
Okay - next time, can you ping <any known address> ? Try 194.150.245.35. Pinging any known address outside of my LAN doesn't work during the outage.
Okay, then at least you can forget any possible DNS problem. When your internet connection drops like this, it should be visible in your router log. I would expect to see evidence of the router login in again etc.
I'm not sure but reading this thread it looks like there may be some confusion about when a domain name is being used and when an IP address is used. It might be useful to be absolutely explicit about what was done each time. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
Which version of Firefox are you using - IF you are using FF?
Firefox 3.5.3 as well as Seamonkey (latest) and others. It doesn't seem to be related directly to the browser.
I still have to spend some time trying some of the recent suggestions.
When this problem hits, it only seems to affect loading webpages in any browser... like port 80 was briefly closed or something.
I have to dig deeper into the Router logs to see if there is something there... and also test the access to the router itself is actually interrupted or if it was co-incidental.
Interesting about the Firefox thing. I might have to try downgrading to an earlier FF version... just to see if it makes a difference.
C.
These sorts of problems are a bugger to try and resolve :-( . Especially when people either do not provide the correct answers or deliberately mislead you when answering your questions -- but none of this refers to the above, just a preamble to the following about trying to solve problems.... I spent 3 months of agonising over why one particular person could not stay connected more than 10 minutes to the BBS I was operating. Of course the problem ONLY happened when he connected to "my" BBS and not any other BBS in the city (naturally!). I told him to try quite a number of things to try and eliminate step at a time where the problem may lie. One of the things I asked him to do was to either, or both, go to friend's house in a different suburb/telephone exchange and see if the problem persisted, or borrow another modem and see if the problem of disconnection persisted. He told me that he did both -- and the problem persisted. (Yet nobody else of the other 600+ users was having the same problem). This particular person was living with 2 or 3 other fellows, sharing the house and the phone line. The problem was finally resolved by another person living in the same house whose name, would you believe it, was (Andrew) *Clayton* :-) , really, who pulled the phone cord from the socket one night when X was connected to "my" BBS (we had dial-up connections at the time) - and the problem disappeared. X who kept complaining about his inability to maintain a connection to "my" BBS was telling me BS stories about doing what I asked him (about going to another suburb, etc) - he didn't do anything of the kind. The problem all along lay in the new telephone model which our telco was installing for new customers: the phone would draw power from the 'phone line every 10 minutes to recharge its NVAM and this caused line noise which the modem(s) would see as unacceptable line noise and therefore drop the connection. Problem solved, but for 3 months I was given the run around by a person who could not tell the truth about doing what I asked him to do. (And he ended up in the IT industry! :'( ) But that's history now...... :-) . BC -- Once, in the wilds of Afghanistan, I lost my corkscrew and we were forced to live on nothing but food and water for days. W C Fields. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 18 Sep 2009 22:53:39 Basil Chupin wrote:
Clayton wrote:
Which version of Firefox are you using - IF you are using FF?
Firefox 3.5.3 as well as Seamonkey (latest) and others. It doesn't seem to be related directly to the browser.
I still have to spend some time trying some of the recent suggestions.
When this problem hits, it only seems to affect loading webpages in any browser... like port 80 was briefly closed or something.
I have to dig deeper into the Router logs to see if there is something there... and also test the access to the router itself is actually interrupted or if it was co-incidental.
Interesting about the Firefox thing. I might have to try downgrading to an earlier FF version... just to see if it makes a difference.
C.
These sorts of problems are a bugger to try and resolve :-( .
Especially when people either do not provide the correct answers or deliberately mislead you when answering your questions -- but none of this refers to the above, just a preamble to the following about trying to solve problems....
I spent 3 months of agonising over why one particular person could not stay connected more than 10 minutes to the BBS I was operating. Of course the problem ONLY happened when he connected to "my" BBS and not any other BBS in the city (naturally!). I told him to try quite a number of things to try and eliminate step at a time where the problem may lie. One of the things I asked him to do was to either, or both, go to friend's house in a different suburb/telephone exchange and see if the problem persisted, or borrow another modem and see if the problem of disconnection persisted. He told me that he did both -- and the problem persisted. (Yet nobody else of the other 600+ users was having the same problem).
This particular person was living with 2 or 3 other fellows, sharing the house and the phone line. The problem was finally resolved by another person living in the same house whose name, would you believe it, was (Andrew) *Clayton* :-) , really, who pulled the phone cord from the socket one night when X was connected to "my" BBS (we had dial-up connections at the time) - and the problem disappeared. X who kept complaining about his inability to maintain a connection to "my" BBS was telling me BS stories about doing what I asked him (about going to another suburb, etc) - he didn't do anything of the kind. The problem all along lay in the new telephone model which our telco was installing for new customers: the phone would draw power from the 'phone line every 10 minutes to recharge its NVAM and this caused line noise which the modem(s) would see as unacceptable line noise and therefore drop the connection. Problem solved, but for 3 months I was given the run around by a person who could not tell the truth about doing what I asked him to do. (And he ended up in the IT industry! :'( ) But that's history now...... :-) .
BC
Ah, yes. The good old days of dial-up modems and the early Telstra "Touch Phones"... -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rodney Baker wrote:
On Fri, 18 Sep 2009 22:53:39 Basil Chupin wrote:
Clayton wrote:
Which version of Firefox are you using - IF you are using FF?
Firefox 3.5.3 as well as Seamonkey (latest) and others. It doesn't seem to be related directly to the browser.
I still have to spend some time trying some of the recent suggestions.
When this problem hits, it only seems to affect loading webpages in any browser... like port 80 was briefly closed or something.
I have to dig deeper into the Router logs to see if there is something there... and also test the access to the router itself is actually interrupted or if it was co-incidental.
Interesting about the Firefox thing. I might have to try downgrading to an earlier FF version... just to see if it makes a difference.
C.
These sorts of problems are a bugger to try and resolve :-( .
Especially when people either do not provide the correct answers or deliberately mislead you when answering your questions -- but none of this refers to the above, just a preamble to the following about trying to solve problems....
I spent 3 months of agonising over why one particular person could not stay connected more than 10 minutes to the BBS I was operating. Of course the problem ONLY happened when he connected to "my" BBS and not any other BBS in the city (naturally!). I told him to try quite a number of things to try and eliminate step at a time where the problem may lie. One of the things I asked him to do was to either, or both, go to friend's house in a different suburb/telephone exchange and see if the problem persisted, or borrow another modem and see if the problem of disconnection persisted. He told me that he did both -- and the problem persisted. (Yet nobody else of the other 600+ users was having the same problem).
This particular person was living with 2 or 3 other fellows, sharing the house and the phone line. The problem was finally resolved by another person living in the same house whose name, would you believe it, was (Andrew) *Clayton* :-) , really, who pulled the phone cord from the socket one night when X was connected to "my" BBS (we had dial-up connections at the time) - and the problem disappeared. X who kept complaining about his inability to maintain a connection to "my" BBS was telling me BS stories about doing what I asked him (about going to another suburb, etc) - he didn't do anything of the kind. The problem all along lay in the new telephone model which our telco was installing for new customers: the phone would draw power from the 'phone line every 10 minutes to recharge its NVAM and this caused line noise which the modem(s) would see as unacceptable line noise and therefore drop the connection. Problem solved, but for 3 months I was given the run around by a person who could not tell the truth about doing what I asked him to do. (And he ended up in the IT industry! :'( ) But that's history now...... :-) .
BC
Ah, yes. The good old days of dial-up modems and the early Telstra "Touch Phones"...
Yes... the ol' (?)1000 Series wasn't it? :-) (But *not* Telstra 'Touch Phone". It was Telecom - which later became Telstra after being partially privatised and had that middle-management AT&T hack (for the life of me I cannot remember his name!) appointed by President Johnson to run it.) BC -- Once, in the wilds of Afghanistan, I lost my corkscrew and we were forced to live on nothing but food and water for days. W C Fields. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
Rodney Baker wrote:
On Fri, 18 Sep 2009 22:53:39 Basil Chupin wrote:
Clayton wrote:
Which version of Firefox are you using - IF you are using FF?
Firefox 3.5.3 as well as Seamonkey (latest) and others. It doesn't seem to be related directly to the browser.
I still have to spend some time trying some of the recent suggestions.
When this problem hits, it only seems to affect loading webpages in any browser... like port 80 was briefly closed or something.
I have to dig deeper into the Router logs to see if there is something there... and also test the access to the router itself is actually interrupted or if it was co-incidental.
Interesting about the Firefox thing. I might have to try downgrading to an earlier FF version... just to see if it makes a difference.
C.
These sorts of problems are a bugger to try and resolve :-( .
Especially when people either do not provide the correct answers or deliberately mislead you when answering your questions -- but none of this refers to the above, just a preamble to the following about trying to solve problems....
I spent 3 months of agonising over why one particular person could not stay connected more than 10 minutes to the BBS I was operating. Of course the problem ONLY happened when he connected to "my" BBS and not any other BBS in the city (naturally!). I told him to try quite a number of things to try and eliminate step at a time where the problem may lie. One of the things I asked him to do was to either, or both, go to friend's house in a different suburb/telephone exchange and see if the problem persisted, or borrow another modem and see if the problem of disconnection persisted. He told me that he did both -- and the problem persisted. (Yet nobody else of the other 600+ users was having the same problem).
This particular person was living with 2 or 3 other fellows, sharing the house and the phone line. The problem was finally resolved by another person living in the same house whose name, would you believe it, was (Andrew) *Clayton* :-) , really, who pulled the phone cord from the socket one night when X was connected to "my" BBS (we had dial-up connections at the time) - and the problem disappeared. X who kept complaining about his inability to maintain a connection to "my" BBS was telling me BS stories about doing what I asked him (about going to another suburb, etc) - he didn't do anything of the kind. The problem all along lay in the new telephone model which our telco was installing for new customers: the phone would draw power from the 'phone line every 10 minutes to recharge its NVAM and this caused line noise which the modem(s) would see as unacceptable line noise and therefore drop the connection. Problem solved, but for 3 months I was given the run around by a person who could not tell the truth about doing what I asked him to do. (And he ended up in the IT industry! :'( ) But that's history now...... :-) .
BC
Ah, yes. The good old days of dial-up modems and the early Telstra "Touch Phones"...
Yes... the ol' (?)1000 Series wasn't it? :-)
(But *not* Telstra 'Touch Phone". It was Telecom - which later became Telstra after being partially privatised and had that middle-management AT&T hack (for the life of me I cannot remember his name!) appointed by President Johnson to run it.)
My memory of history is all shot to bits :-( . Pres. Johnson went out of office in, what, 1969, and it was to Telecom that he appointed that AT&T middle-management hack as it's CEO. I saw the interview with that hack on TV where he stated that Johnson called him in and told him that he wanted the hack to go and run Telecom in Australia. Telecom was partially privatised later (stages 1, 2, and 3) and became known as Testra. BC -- Once, in the wilds of Afghanistan, I lost my corkscrew and we were forced to live on nothing but food and water for days. W C Fields. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 18 Sep 2009 23:30:21 Basil Chupin wrote:
Rodney Baker wrote:
On Fri, 18 Sep 2009 22:53:39 Basil Chupin wrote:
Clayton wrote:
Which version of Firefox are you using - IF you are using FF?
Firefox 3.5.3 as well as Seamonkey (latest) and others. It doesn't seem to be related directly to the browser.
I still have to spend some time trying some of the recent suggestions.
When this problem hits, it only seems to affect loading webpages in any browser... like port 80 was briefly closed or something.
I have to dig deeper into the Router logs to see if there is something there... and also test the access to the router itself is actually interrupted or if it was co-incidental.
Interesting about the Firefox thing. I might have to try downgrading to an earlier FF version... just to see if it makes a difference.
C.
These sorts of problems are a bugger to try and resolve :-( .
Especially when people either do not provide the correct answers or deliberately mislead you when answering your questions -- but none of this refers to the above, just a preamble to the following about trying to solve problems....
I spent 3 months of agonising over why one particular person could not stay connected more than 10 minutes to the BBS I was operating. Of course the problem ONLY happened when he connected to "my" BBS and not any other BBS in the city (naturally!). I told him to try quite a number of things to try and eliminate step at a time where the problem may lie. One of the things I asked him to do was to either, or both, go to friend's house in a different suburb/telephone exchange and see if the problem persisted, or borrow another modem and see if the problem of disconnection persisted. He told me that he did both -- and the problem persisted. (Yet nobody else of the other 600+ users was having the same problem).
This particular person was living with 2 or 3 other fellows, sharing the house and the phone line. The problem was finally resolved by another person living in the same house whose name, would you believe it, was (Andrew) *Clayton* :-) , really, who pulled the phone cord from the socket one night when X was connected to "my" BBS (we had dial-up connections at the time) - and the problem disappeared. X who kept complaining about his inability to maintain a connection to "my" BBS was telling me BS stories about doing what I asked him (about going to another suburb, etc) - he didn't do anything of the kind. The problem all along lay in the new telephone model which our telco was installing for new customers: the phone would draw power from the 'phone line every 10 minutes to recharge its NVAM and this caused line noise which the modem(s) would see as unacceptable line noise and therefore drop the connection. Problem solved, but for 3 months I was given the run around by a person who could not tell the truth about doing what I asked him to do. (And he ended up in the IT industry! :'( ) But that's history now...... :-) .
BC
Ah, yes. The good old days of dial-up modems and the early Telstra "Touch Phones"...
Yes... the ol' (?)1000 Series wasn't it? :-)
(But *not* Telstra 'Touch Phone". It was Telecom - which later became Telstra after being partially privatised and had that middle-management AT&T hack (for the life of me I cannot remember his name!) appointed by President Johnson to run it.)
BC
Quite right - it was Telecom Australia back then. I may be showing my age, but I can remember as a young boy when the PMG was split up to form Telecom Australia and Australia Post (way before the days of push-button phones, tone dialling and all that...but now we're getting way OT... -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin pecked at the keyboard and wrote:
Basil Chupin wrote:
Clayton wrote: <snip> BC
Just to follow-up on this.
Which version of Firefox are you using - IF you are using FF?
Both my wife and I have found some strange behaviour with FF (which I have been exclusively using sine the Netscape days) that recently we do not get pages appearing when selected. The usual "excuse" is that the URL cannot be accessed. Close down FF, start it again, and the wanted web page is loaded without a problem. This only started in the past couple of weeks (give or take - nobody really keeps daily notes, you know :-) .)
BC
Now that others are seeing random problems I also have been seeing random lockups, pages won't load, etc. The last update on my system for Mozilla was on August 21st and the problems seem to have started right after that. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ken Schneider - openSUSE wrote:
Basil Chupin pecked at the keyboard and wrote:
Basil Chupin wrote:
Clayton wrote:
<snip>
BC
Just to follow-up on this.
Which version of Firefox are you using - IF you are using FF?
Both my wife and I have found some strange behaviour with FF (which I have been exclusively using sine the Netscape days) that recently we do not get pages appearing when selected. The usual "excuse" is that the URL cannot be accessed. Close down FF, start it again, and the wanted web page is loaded without a problem. This only started in the past couple of weeks (give or take - nobody really keeps daily notes, you know :-) .)
BC
Now that others are seeing random problems I also have been seeing random lockups, pages won't load, etc. The last update on my system for Mozilla was on August 21st and the problems seem to have started right after that.
Thanks for the feedback, Ken. One really never knows if it is something which is only applicable to oneself or applicable to others until one gets feedback from others. My wife and I are using FF 3.5.3-1.2 20090909 which was only upgraded a day or so ago (I think) but the "funnies" - which you also describe - has been around for a bit longer than a couple of days. This is on 11.1 with KDE4.3.1. I am having a "hassle" with kaffeine - which I never had before - and the author/maintainer tells me that it is only a 'temporary' regression because of having to 'port' to kde43. Me thinks KDE43 has a lot to answer for. I suspect that the oS fiddles for FF to fit in with KDE43 have a part to play with the glitches we are experiencing with FF. That's what I think - but, what do I know? BC. -- Once, in the wilds of Afghanistan, I lost my corkscrew and we were forced to live on nothing but food and water for days. W C Fields. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 17 September 2009 15:41:14 Clayton wrote:
I don't know if the MTU change will help you. I don't understand why it should only once on a while...
That's what has caught me up too. It's once in a while.. not all the time, and not always one particular site. When it happens, it's all websites...
The plot thickens. I'm beginning to wonder if it's actually my ISP after all. I just had another outage where I was not able to load any websites, but other web services continued to work as normal. During that "outage" I attempted to connect to my Netgear router using the usual 192.168.1.1 IP address... nothing. no connect until web access (being able to connect to websites) returned. Then i was able to log into and browse my router config.
Did you check router logs ? Connect computer directly to the modem ? (don't forget to turn on firewall :) Log in connection attempts. Reset router and configure again. -- Regards, Rajko People of openSUSE editor. Latest interviews: http://news.opensuse.org/category/people-of-opensuse/ About us: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
The plot thickens. I'm beginning to wonder if it's actually my ISP after all. I just had another outage where I was not able to load any websites, but other web services continued to work as normal. During that "outage" I attempted to connect to my Netgear router using the usual 192.168.1.1 IP address... nothing. no connect until web access (being able to connect to websites) returned. Then i was able to log into and browse my router config.
Does the router/modem have status lights? What do they show while the problem is present? As others have said, power-cycle everything. Is your inability to contact http://192.168.1.1/ a network problem or a browser problem? Can you contact it using lynx, or wget or even telnet (to port 80)? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (11)
-
Basil Chupin -
Clayton -
Dave Howorth -
Greg Freemyer -
jdd -
Ken Schneider - openSUSE -
Per Jessen -
Peter Nikolic -
Rajko M. -
Richard -
Rodney Baker