[kwlug-disc] Ubuntu 12.04 LTS localhost* and internet fail - where to start?

Wed Apr 9 19:28:59 EDT 2014

Sounds like the dsl modem is not in bridged mode (if the modem is separate from the router).

Blog: http://www.charlesmccolm.com/
Sent from my cell phone.

-----Original Message-----
From: unsolicited <unsolicited at swiz.ca>
Sender: "kwlug-disc" <kwlug-disc-bounces at kwlug.org>
Date: Wed, 09 Apr 2014 19:26:16 
To: KWLUG discussion<kwlug-disc at kwlug.org>
Reply-To: KWLUG discussion <kwlug-disc at kwlug.org>
Subject: Re: [kwlug-disc] Ubuntu 12.04 LTS localhost* and internet fail -
 where to start?

 > ifconfig now shows IP 209.183.xxx.yyy not 192.168.0.100 as before (at 
7:30 to 11:30 am)

Then the box didn't receive DHCP from your router, it got it from the 
internet. Something not reset when you returned off dsl modem. (Or DHCP 
turned off on router and passing it through - which is ... unusual.)

This is all very confusing.

Put things as they were. Go back to baseline.

i.e. Get Windows happy as it was. Get haystack back to Linux only, 
taking much possibility off the table.

Distinguish between name resolution and routing issues as per prior.

It feels like some sort of firewall/malware blocker came into effect. 
Not that his makes sense. Perhaps on the router (but doesn't make sense, 
as from your description the problem is linux ip specific). [Test: 
Change linux static ip see if problem follows.] Easy way to see if IP 
related somewhere, swap linux and windows static ips, see where problem 
follows.

Don't worry about 'localhost' - not the core issue. Resolve afterwards.

Post again when you get yourself back together, with windows all happy, 
and exactly what the linux issue is.

And also the results of:

nslookup google.com

traceroute 8.8.8.8

- note also, ping / traceroute are by name. No http:// in either 
anywhere at all.

On 14-04-09 05:30 PM, John Johnson wrote:
> Resisted. continuing. Ubuntu issues w/router persist.
>
> Lost count of troubleshooting exercises.
>
> Recap: At 7:30 am all was OK and that during a session on a website via
> the Linux box, the internet access to that site went down.
> This leads be to believe that the configuration of the Linux box was
> correct.
>
> Dlink router: downloaded and installed latest firmware. Reset
> configuration to factory defaults.
> Windows box: internet access continues to be OK.
> Linux box: Previously configured to dial through DSL modem to ISP.
> Linux box: Now does the same through router.
> ifconfig now shows IP 209.183.xxx.yyy not 192.168.0.100 as before (at
> 7:30 to 11:30 am)
>
> Linux box Changed Settings > Network > Options > wired not DSL
> Rebooted. NADDA ifconfig now shows IP 209.183.xxx.yyy not 192.168.0.100
> as before.
>
> Linux box: ping 127.0.0.1 OK
> Linux box: ping localhost OK *
> * sometimes fails (not sure what I was doing when I saw the failure)
>
> Router: moving wires between physical ports. NO WIRELESS.
>
> I am shutting everything down for a cold boot boot later this evening
> and will pick up on this at that time.
>
> Thanks
> JohnJ
>
>
> On 2014-04-09 10:51, John Johnson wrote:
>> Thanks for the tip: was looking for something like this.
>> http://etherealmind.com/what-is-the-best-ip-address-to-ping-to-test-my-internet-connection/
>>
>>
>> Troubleshooting round four:
>> Pings with named ping destinations fail on both the Linux and Windows
>> boxes.
>> e.g. c:\>ping https://www.google.ca  c:\>ping http://www.google.ca
>>
>> One of the destinations recommended in the link above, ping 8.8.8.8
>> works on the Windows box.
>> The Linux box however is still failing.
>>
>> On the Linux box, the error message returned for ping 8.8.8.8 is
>> different from ping http://www.google.ca.
>> For the google.ca, I see "unknown host".
>> For 8.8.8.8 I see: from 192.168.0.1 icmp_ .... Destination Net
>> Unreachable.
>>
>> Looks like the router is blocking the Linux box.
>> Rebooted router. NADDA.
>>
>> Troubleshooting round five:
>>
>> Bypassed the Dlink router. Connected Linux box direct to DSL modem.
>> Setup Ubuntu > Settings > Network as req'd to dial on the DSL modem as
>> opposed to wired connection.
>>
>> FF on Linux box works.
>>
>> The issue with the Dlink router not the Linux box per se.
>> Disconnected the Linux box, reconnected router and Windows box.
>>
>> OT (slightly):
>> How do I set up Ubuntu with more than Network connection configuration?
>> 1) (default) wired connection through router (w/o 'dialer' settings)
>> 2) DSL modem with 'dialer' settings
>>
>> Thanks
>> JohnJ
>>
>>
>> On 2014-04-09 09:53, L.D. Paniak wrote:
>>> Can you ping a site on the internet from clients? eg 4.2.2.2
>>> If not, you have no connectivity to the internet. Check
>>> cables/routing/gateway config.
>>>
>>> If so, can you ping a site by name: google.ca
>>> If not, check DNS.
>>>
>>>
>>> On 04/09/2014 09:46 AM, John Johnson wrote:
>>>> Ubuntu 12.04 LTS localhost* and internet fail (w/FF)- where to start?
>>>>
>>>> My Linux box is, all of a sudden, failing to connect to the internet.
>>>> I was on a site earlier when the site (and others) started returning
>>>> the FF "server not found" (404) message.
>>>>
>>>> Actually, I have made, I think, a good start (see below).
>>>> I am asking where do I go now?
>>>>
>>>> Troubleshooting round one:
>>>> Boot. Reboot. Ubuntu restart. etc.
>>>> re-wired Linux box to Router connections.
>>>>
>>>> Troubleshooting round two:
>>>> Linux box>  terminal>  ping 192.168.0.1 (Dlink router) are OK
>>>> Linux box>  terminal>  ping 192.168.0.115 (Windows box) OK
>>>> Linux box>  terminal>  ping 192.168.0.101 (loop back to Linux box) OK
>>>> Linux box>  terminal>  ping localhost (loop back to Linux box via
>>>> LAMP) OK *
>>>> Windows box>  cmd window>  ping 192.168.0.1 (Dlink router) are OK
>>>> Windows box>  cmd window>  ping 192.168.0.101 (Linux box) are OK
>>>> Windows box>  cmd window>  ping 192.168.0.115 (loop back Windows box)
>>>> are OK
>>>> Windows box>  cmd window>  ping localhost (loop back to Windows box
>>>> via XAMPP) are OK
>>>>
>>>> *ping localhost was failing on the Linux box when I started
>>>> troubleshooting. Working now.
>>>> FF internet access still fails.
>>>>
>>>>
>>>> Troubleshooting round three:
>>>> Suspecting that the issue may be isolated to FF:
>>>> FF restarted in safe-mode. i.e. with add-ons disabled: still fails
>>>> Attempted bypass of FF through Ubuntu Software Centre and install of
>>>> Chromium browser: fail.
>>>>
>>>> Analysis: The issue does not look to be isolated to FF.
>>>>
>>>> Thanks
>>>> JohnJ
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> kwlug-disc mailing list
>>>> kwlug-disc at kwlug.org
>>>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>>>
>>>
>>> _______________________________________________
>>> kwlug-disc mailing list
>>> kwlug-disc at kwlug.org
>>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>>>
>>>
>>> -----
>>>
>>> Checked by AVG -www.avg.com
>>> Version: 2014.0.4355 / Virus Database: 3882/7318 - Release Date:
>>> 04/08/14
>>
>>
>> _______________________________________________
>> kwlug-disc mailing list
>> kwlug-disc at kwlug.org
>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>>
>>
>>
>> Checked by AVG - www.avg.com <http://www.avg.com>
>> Version: 2014.0.4355 / Virus Database: 3882/7318 - Release Date: 04/08/14
>>
>
>
>
>
> _______________________________________________
> kwlug-disc mailing list
> kwlug-disc at kwlug.org
> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>

_______________________________________________
kwlug-disc mailing list
kwlug-disc at kwlug.org
http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org