🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: aus.computers.linux
11 messages
11 total messages Started by Polly the Parrott Sat, 10 Dec 2011 01:04
Network connects .. but no software will.
#481
Author: Polly the Parrott
Date: Sat, 10 Dec 2011 01:04
31 lines
2129 bytes
Lubuntu 11.10; Atheros AR8132 PCI-E Ethernet card; Realtek RTL8191SE
Wireless Lan 802.11n PCI-E NIC. Toshiba laptop Satellite T110.

Until this morning, no connection issues either by wireless or
Ethernet.

Now, the connection indicator shows as connected for either (depending
of course on which one I select to be active), and shows in case of
the wireless the signal strength, but in actual fact cannot browse,
get mail etc etc.

Firefox & others come up with "no network connection" sort of error.

Dual boot, no such issue with Windoze.

 ifconfig shows all RX & TX as errors, and I can ping the router ok.

On reflection, what happened yesterday was that I had to rush to catch
a flight, the laptop had been on all night, and was locked up in a
screen saver, no response. I had to press the on/off key to shut down.
Maybe this caused the issue?

Would appreciate assistance getting both cards up again in Lubuntu,
also some sort of idea why this happened.

And, as usual, thanks in advance!

(Originally posted in general linux ng, no assistance so far,
apologies if you have read before.)

PS this happens in multiple locations, so not an isp problem, thanks!
Re: Network connects .. but no software will.
#482
Author: Zebee Johnstone
Date: Sat, 10 Dec 2011 02:06
119 lines
5513 bytes
In aus.computers.linux on Sat, 10 Dec 2011 12:04:55 +1100
Polly the Parrott <flatulantdingo@deadspam.com> wrote:
>
> Now, the connection indicator shows as connected for either (depending
> of course on which one I select to be active), and shows in case of
> the wireless the signal strength, but in actual fact cannot browse,
> get mail etc etc.
>
> Firefox & others come up with "no network connection" sort of error.
>
> Dual boot, no such issue with Windoze.
>
>  ifconfig shows all RX & TX as errors, and I can ping the router ok.
>


Hmm... if you can ping the router, packets are getting out.  But they
might just be getting as far as the router.

There are two possiblities - network and firewall.  

Quick test - turn off any firewall at all.  Try again.  If it all now
works your firewall setup is corrupt and you might need to find an
Ubuntu forum to work out how to fix that.

You might need to check it really *is* off,  so get to a terminal
session and do
  sudo iptables -L
you should see something like

hain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

that is, everything as accept.  If not, then you have to get to that
point.

If your firewall is off and you still can't connect then it's network,
the first job is to check the simplest case, which is ethernet.  So
turn off wireless.

I know nothing about ubuntu, but presumably all the command line tools
work and show something intelligent so try getting to a terminal and
doing
   netstat -r -n

You should get something like
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window
irtt Iface
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0 0 eth1
0.0.0.0         192.168.1.124   0.0.0.0         UG        0 0 0 eth1

see that last line?  The many 0's are the "default route" and that
line is telling me that all packets destined for the great wide world
will head out via 192.168.1.124 which is my router.  

Check what yours says.

Then  do the same on Windows.  (I think the output is the same on
Windows, don't have one of those either...)

If you don't have a default route in netstat then somethng's amiss
with your network connection.  You can test it by doing 

  route add default gw www.xxx.yyy.zzz
where www.xxx.yyy.zzz is the IP address of your router, in my example
I'd do
  route add default gw 192.168.1.124

Now try firefox or something.  If that works then that's the
problem... fixing it means looking at your network configuration.  I
presume you are using something like Network Manager?  Find your
network configuration icon or look for how you configure your network
and check that everything is as it should be.  At a rough guess you
want to make sure you are using DHCP for everything.

If you are, and it's still a gateway problem we run into the "Zebee
knows nothing about Ubuntu" and you might need to head over to an
Ubuntu forum.  Else you can try telling it to use your router as a
gateway and sort it like that.

Now... supposing you do have a default route and it's the right one,
but not passing packets.

That gets more annoying :)

It means that your router is objecting to something about linux and
not windows.  

Check if you are using the same IP address in both.  In windows on the
command line do 
  ipconfig
and in linux
  ifconfig

the out put is not quite identical from memory but the basics should
be easy to see.

If you aren't getting the same IP, why not....  If your network is set
for DHCP that means something in the router, look there.

If you are, and the route's the same, and there's nothing obviously
set in the router, then I fear it is something
busted in your Network Manager (or whatever Ubuntu uses).

It is possible you have a corrupted file.  I suppose before finding
a forum you could delete your ethernet and wireless information
from your network manager setup, reboot (to make sure it really is
all clear, I don't trust NetworkManager...) and re-create your
setup.  That should clear any corrupted file.


Zebee
Re: Network connects .. but no software will.
#483
Author: Polly the Parrott
Date: Sat, 10 Dec 2011 11:08
12 lines
1512 bytes
On Sat, 10 Dec 2011 02:06:22 +0000 (UTC), Zebee Johnstone
<zebeej@gmail.com> wrote:

>It is possible you have a corrupted file.  I suppose before finding
>a forum you could delete your ethernet and wireless information
>from your network manager setup, reboot (to make sure it really is
>all clear, I don't trust NetworkManager...) and re-create your
>setup.  That should clear any corrupted file.


What software do I use to recreate the setup?  (says he with little
knowledge)
Re: Network connects .. but no software will.
#484
Author: Zebee Johnstone
Date: Sat, 10 Dec 2011 12:21
33 lines
2477 bytes
In aus.computers.linux on Sat, 10 Dec 2011 22:08:12 +1100
Polly the Parrott <flatulantdingo@deadspam.com> wrote:
> On Sat, 10 Dec 2011 02:06:22 +0000 (UTC), Zebee Johnstone
><zebeej@gmail.com> wrote:
>
>>It is possible you have a corrupted file.  I suppose before finding
>>a forum you could delete your ethernet and wireless information
>>from your network manager setup, reboot (to make sure it really is
>>all clear, I don't trust NetworkManager...) and re-create your
>>setup.  That should clear any corrupted file.
>
>
> What software do I use to recreate the setup?  (says he with little
> knowledge)

Remember... I dunno Ubuntu :)

But in your menus somewhere or a right click on the network item in
the systray there should be a configuration menu.

In my Fedora I right click on the network thing in the systray and it
says "network management settings".

You see what it says now, and you re-create that after deleting it.

If you are using your usual home ADSL router than just deleting the
ethernet (probably called eth0) and recreating it accepting all
defaults will do.

Have a hunt around google and/or the Ubuntu sites for "setting up
networking on Ubuntu" 

Zebee
Re: Network connects .. but no software will.
#485
Author: Polly the Parrott
Date: Sat, 10 Dec 2011 18:53
38 lines
2481 bytes
On Sat, 10 Dec 2011 12:21:57 +0000 (UTC), Zebee Johnstone
<zebeej@gmail.com> wrote:

>In aus.computers.linux on Sat, 10 Dec 2011 22:08:12 +1100
>Polly the Parrott <flatulantdingo@deadspam.com> wrote:
>> On Sat, 10 Dec 2011 02:06:22 +0000 (UTC), Zebee Johnstone
>><zebeej@gmail.com> wrote:
>>
>>>It is possible you have a corrupted file.  I suppose before finding
>>>a forum you could delete your ethernet and wireless information
>>>from your network manager setup, reboot (to make sure it really is
>>>all clear, I don't trust NetworkManager...) and re-create your
>>>setup.  That should clear any corrupted file.
>>
>>
>> What software do I use to recreate the setup?  (says he with little
>> knowledge)
>
>Remember... I dunno Ubuntu :)
>
>But in your menus somewhere or a right click on the network item in
>the systray there should be a configuration menu.
>
>In my Fedora I right click on the network thing in the systray and it
>says "network management settings".
>
>You see what it says now, and you re-create that after deleting it.
>
>If you are using your usual home ADSL router than just deleting the
>ethernet (probably called eth0) and recreating it accepting all
>defaults will do.
>
>Have a hunt around google and/or the Ubuntu sites for "setting up
>networking on Ubuntu" 
>
>Zebee

Thanks, will give it a go, nothing to lose!
Re: Network connects .. but no software will.
#486
Author: Polly the Parrott
Date: Sat, 10 Dec 2011 19:57
15 lines
1561 bytes
On Sat, 10 Dec 2011 12:21:57 +0000 (UTC), Zebee Johnstone
<zebeej@gmail.com> wrote:

>You see what it says now, and you re-create that after deleting it.
>
>If you are using your usual home ADSL router than just deleting the
>ethernet (probably called eth0) and recreating it accepting all
>defaults will do.

Didn't work, unfortunately.

Tried the Google bits & pieces, of course may have missed some, but a
few more to go.

Thanks for the help.
Re: Network connects .. but no software will.
#487
Author: Zebee Johnstone
Date: Sat, 10 Dec 2011 20:21
17 lines
2008 bytes
In aus.computers.linux on Sun, 11 Dec 2011 06:57:36 +1100
Polly the Parrott <flatulantdingo@deadspam.com> wrote:
> On Sat, 10 Dec 2011 12:21:57 +0000 (UTC), Zebee Johnstone
><zebeej@gmail.com> wrote:
>
>>You see what it says now, and you re-create that after deleting it.
>>
>>If you are using your usual home ADSL router than just deleting the
>>ethernet (probably called eth0) and recreating it accepting all
>>defaults will do.
>
> Didn't work, unfortunately.
>

How about the firewall and routing stuff?  any luck there?

Zebee
Re: Network connects .. but no software will.
#488
Author: Polly the Parrott
Date: Sat, 10 Dec 2011 21:40
21 lines
1947 bytes
On Sat, 10 Dec 2011 20:21:21 +0000 (UTC), Zebee Johnstone
<zebeej@gmail.com> wrote:

>In aus.computers.linux on Sun, 11 Dec 2011 06:57:36 +1100
>Polly the Parrott <flatulantdingo@deadspam.com> wrote:
>> On Sat, 10 Dec 2011 12:21:57 +0000 (UTC), Zebee Johnstone
>><zebeej@gmail.com> wrote:
>>
>>>You see what it says now, and you re-create that after deleting it.
>>>
>>>If you are using your usual home ADSL router than just deleting the
>>>ethernet (probably called eth0) and recreating it accepting all
>>>defaults will do.
>>
>> Didn't work, unfortunately.
>>
>
>How about the firewall and routing stuff?  any luck there?

Working on another track at present;  will report.
>
Re: Network connects .. but no software will.
#489
Author: Polly the Parrott
Date: Sat, 10 Dec 2011 22:13
92 lines
5188 bytes
On Sat, 10 Dec 2011 20:21:21 +0000 (UTC), Zebee Johnstone
<zebeej@gmail.com> wrote:

>How about the firewall and routing stuff?  any luck there?

Looks like a firewall issue.

Running Gufw graphical firewall set up, allow all in, none out, except
for 6881 for (cough cough) file transfers.

When I turn firewall off in Gufw, no issues.

Turn back on, same problems as before.

However Iptables reads as follows:-

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ufw-before-logging-input  all  --  anywhere             anywhere
ufw-before-input  all  --  anywhere             anywhere            
ufw-after-input  all  --  anywhere             anywhere            
ufw-after-logging-input  all  --  anywhere             anywhere
ufw-reject-input  all  --  anywhere             anywhere            
ufw-track-input  all  --  anywhere             anywhere            

Chain FORWARD (policy DROP)
target     prot opt source               destination         
ufw-before-logging-forward  all  --  anywhere             anywhere
ufw-before-forward  all  --  anywhere             anywhere            
ufw-after-forward  all  --  anywhere             anywhere            
ufw-after-logging-forward  all  --  anywhere             anywhere
ufw-reject-forward  all  --  anywhere             anywhere            

Chain OUTPUT (policy DROP)
target     prot opt source               destination         
ufw-before-logging-output  all  --  anywhere             anywhere
ufw-before-output  all  --  anywhere             anywhere            
ufw-after-output  all  --  anywhere             anywhere            
ufw-after-logging-output  all  --  anywhere             anywhere
ufw-reject-output  all  --  anywhere             anywhere            
ufw-track-output  all  --  anywhere             anywhere            

Chain ufw-after-forward (1 references)
target     prot opt source               destination         

Chain ufw-after-input (1 references)
target     prot opt source               destination         
ufw-skip-to-policy-input  udp  --  anywhere             anywhere udp
dpt:netbios-ns 
ufw-skip-to-policy-input  udp  --  anywhere             anywhere udp
dpt:netbios-dgm 
ufw-skip-to-policy-input  tcp  --  anywhere             anywhere tcp
dpt:netbios-ssn 
ufw-skip-to-policy-input  tcp  --  anywhere             anywhere tcp
dpt:microsoft-ds 
ufw-skip-to-policy-input  udp  --  anywhere             anywhere udp
dpt:bootps 
ufw-skip-to-policy-input  udp  --  anywhere             anywhere udp
dpt:bootpc 
ufw-skip-to-policy-input  all  --  anywhere             anywhere
ADDRTYPE match dst-type BROADCAST 

Chain ufw-after-logging-forward (1 references)
target     prot opt source               destination         
LOG        all  --  anywhere             anywhere            limit:
avg 3/min burst 10 LOG level warning prefix `[UFW BLOCK] ' 

Chain ufw-after-logging-input (1 references)
target     prot opt source               destination         

Chain ufw-after-logging-output (1 references)
target     prot opt source               destination         
LOG        all  --  anywhere             anywhere            limit:
avg 3/min burst 10 LOG level warning prefix `[UFW BLOCK] ' 

Chain ufw-after-output (1 references)
target     prot opt source               destination         

Chain ufw-before-forward (1 references)
target     prot opt source               destination         
ufw-user-forward  all  --  anywhere             anywhere            

Chain ufw-before-input (1 references)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            state
RELATED,ESTABLISHED 

I haven't touched the firewall set up at all, and being dumb at all of
this, politely asking how to fix, please!

And wondering what has gone wrong with Gufw?
Re: Network connects .. but no software will.
#490
Author: Zebee Johnstone
Date: Sat, 10 Dec 2011 23:26
117 lines
6481 bytes
In aus.computers.linux on Sun, 11 Dec 2011 09:13:40 +1100
Polly the Parrott <flatulantdingo@deadspam.com> wrote:
> On Sat, 10 Dec 2011 20:21:21 +0000 (UTC), Zebee Johnstone
><zebeej@gmail.com> wrote:
>
>>How about the firewall and routing stuff?  any luck there?
>
> Looks like a firewall issue.
>
> Running Gufw graphical firewall set up, allow all in, none out, except
> for 6881 for (cough cough) file transfers.
>
> When I turn firewall off in Gufw, no issues.

UNfortunately I don't use GUI firewall tools, I am a crusty old unix
admin...

I am also not particularly skilled with iptables, having not had to
mess with it for years.  (at work we have proper firewalls and at home
my ADSL whatsit does the job)

The stuff below looks reasonable from what I can tell, 

however...  the none out might be a problem.  Because well.. stuff has
to go out :)

I'd have thought you meant to put none in, all out?

You don't care what leaves the premises but you are very much
interested in what comes in.  Ideally you don't want anything coming
in you didn't ask for except those file transfers.  

Zebee

>
> Turn back on, same problems as before.
>
> However Iptables reads as follows:-
>
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination         
> ufw-before-logging-input  all  --  anywhere             anywhere
> ufw-before-input  all  --  anywhere             anywhere            
> ufw-after-input  all  --  anywhere             anywhere            
> ufw-after-logging-input  all  --  anywhere             anywhere
> ufw-reject-input  all  --  anywhere             anywhere            
> ufw-track-input  all  --  anywhere             anywhere            
>
> Chain FORWARD (policy DROP)
> target     prot opt source               destination         
> ufw-before-logging-forward  all  --  anywhere             anywhere
> ufw-before-forward  all  --  anywhere             anywhere            
> ufw-after-forward  all  --  anywhere             anywhere            
> ufw-after-logging-forward  all  --  anywhere             anywhere
> ufw-reject-forward  all  --  anywhere             anywhere            
>
> Chain OUTPUT (policy DROP)
> target     prot opt source               destination         
> ufw-before-logging-output  all  --  anywhere             anywhere
> ufw-before-output  all  --  anywhere             anywhere            
> ufw-after-output  all  --  anywhere             anywhere            
> ufw-after-logging-output  all  --  anywhere             anywhere
> ufw-reject-output  all  --  anywhere             anywhere            
> ufw-track-output  all  --  anywhere             anywhere            
>
> Chain ufw-after-forward (1 references)
> target     prot opt source               destination         
>
> Chain ufw-after-input (1 references)
> target     prot opt source               destination         
> ufw-skip-to-policy-input  udp  --  anywhere             anywhere udp
> dpt:netbios-ns 
> ufw-skip-to-policy-input  udp  --  anywhere             anywhere udp
> dpt:netbios-dgm 
> ufw-skip-to-policy-input  tcp  --  anywhere             anywhere tcp
> dpt:netbios-ssn 
> ufw-skip-to-policy-input  tcp  --  anywhere             anywhere tcp
> dpt:microsoft-ds 
> ufw-skip-to-policy-input  udp  --  anywhere             anywhere udp
> dpt:bootps 
> ufw-skip-to-policy-input  udp  --  anywhere             anywhere udp
> dpt:bootpc 
> ufw-skip-to-policy-input  all  --  anywhere             anywhere
> ADDRTYPE match dst-type BROADCAST 
>
> Chain ufw-after-logging-forward (1 references)
> target     prot opt source               destination         
> LOG        all  --  anywhere             anywhere            limit:
> avg 3/min burst 10 LOG level warning prefix `[UFW BLOCK] ' 
>
> Chain ufw-after-logging-input (1 references)
> target     prot opt source               destination         
>
> Chain ufw-after-logging-output (1 references)
> target     prot opt source               destination         
> LOG        all  --  anywhere             anywhere            limit:
> avg 3/min burst 10 LOG level warning prefix `[UFW BLOCK] ' 
>
> Chain ufw-after-output (1 references)
> target     prot opt source               destination         
>
> Chain ufw-before-forward (1 references)
> target     prot opt source               destination         
> ufw-user-forward  all  --  anywhere             anywhere            
>
> Chain ufw-before-input (1 references)
> target     prot opt source               destination         
> ACCEPT     all  --  anywhere             anywhere            
> ACCEPT     all  --  anywhere             anywhere            state
> RELATED,ESTABLISHED 
>
> I haven't touched the firewall set up at all, and being dumb at all of
> this, politely asking how to fix, please!
>
> And wondering what has gone wrong with Gufw?
>
>
Re: Network connects .. but no software will.
#491
Author: Polly the Parrott
Date: Sun, 11 Dec 2011 20:49
14 lines
1673 bytes
On Sun, 11 Dec 2011 10:26 someone claiming to be Zebee Johnstone 
(zebeej@gmail.com),  said: 


> however...  the none out might be a problem.  Because well.. stuff has
> to go out :)
> 
> I'd have thought you meant to put none in, all out?

LOL!

Correct, all fine now!

Thanks for the help!
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads