Limited access to the internet via wireless or wired after an apt-get update on deb 6

onerous · 03-03-2013, 02:17 PM

Hello people,

Having a few issues and I'm a bit stuck as to what has gone wrong. Have updated the distro using apt-get update and apt-get upgrade.

Using firefox and chromium I cannot connect to google even when pinged but can connect to facebook. Can ping facebook but the pages that come up arent like the normal facebook page. Can ping facebook fine.

The card details are

Quote:

eth0 Link encap:Ethernet HWaddr 00:02:3f:d9:ce:d9
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:105 errors:0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11562 (11.2 KiB) TX bytes:12983 (12.6 KiB)
Interrupt:21 Base address:0x3000

eth1 Link encap:Ethernet HWaddr 00:25:56:0a:89:8a
inet addr:192.168.0.11 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::225:56ff:fe0a:3589/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3846 errors:0 dropped:0 overruns:0 frame:88937
TX packets:3237 errors:31 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4094511 (3.9 MiB) TX bytes:278661 (272.1 KiB)
Interrupt:22 Base address:0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:717 errors:0 dropped:0 overruns:0 frame:0
TX packets:717 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68088 (66.4 KiB) TX bytes:68088 (66.4 KiB)

The cat /etc/network/interfaces gives

Quote:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

Any ideas what has happened as it was fine.

frankbell · 03-03-2013, 08:37 PM

It's a shot in the dark, but since you can connect to some sites but not others, try clearing your browsers' caches. It takes seconds, can't hurt, and might help.

What are the contents of /etc/network/interfaces and what DNS settings are you using?

onerous · 03-12-2013, 06:31 PM

DNS settings are auto

The settings is listed already.

Tried the laptop on another network and nothing at all now. Ping gives no answer.

Any ideas?

jim_p · 03-13-2013, 04:29 AM

Some things I can notice
- you have an eth1 interface, probably made out of nowhere, unless you have a wireless card or another nic
- that eth1 interface is not configured at all in /etc/network/interfaces
so are you sure you are using the proper interface to connect to the outside world?

onerous · 03-13-2013, 01:03 PM

Hello

The computer is a laptop, has both a wireless card and wired port.

How do I populate the /etc... file and why would it change without me altering.

jim_p · 03-13-2013, 02:55 PM

Check /etc/udev/rules.d/70-persistent-net.rules to see which interface is on which card.
Was it always eth1 on your wireless?

Hungry ghost · 03-13-2013, 03:29 PM

Not sure why it changed on its own; probably the upgrade replaced the interfaces file (or any other) for some reason. Anyway, once you know which interface is linked to each card, you can check this link on Debian network configuration in order to set up your connection.

Also, being a laptop, which will probably need to connect to different APs, I would install some GUI network management tool, like network-manager, wicd, or any other of your preference, to ease the connection process each time you switch to a different AP.

onerous · 03-15-2013, 06:58 PM

Ah have been messing about and noted that plugged in to the router it does seem to be able to apt-get upgrate. But still cant access the internet via firefox or chrome. Chrome get the message Error 102 connection refused and unknown error.

Eth1 is the wireless card. The config of the wireless card is on here as I had issues.

The network manager is wicd

onerous · 03-15-2013, 08:16 PM

Could it be an Iptables issue?

onerous · 03-23-2013, 04:45 PM

Hello

Still not working and came back to this as I have an evening free,

iptables -L

Quote:

Chain INPUT (policy ACCEPT)
target prot opt source destination
pgl_in all -- anywhere anywhere state NEW mark match !0x14

Chain FORWARD (policy ACCEPT)
target prot opt source destination
pgl_fwd all -- anywhere anywhere state NEW mark match !0x14

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
pgl_out all -- anywhere anywhere state NEW mark match !0x14

Chain pgl_fwd (1 references)
target prot opt source destination
RETURN all -- link-local/16 link-local/16
RETURN all -- link-local/16 192.168.0.0/24
RETURN all -- 192.168.0.0/24 link-local/16
RETURN all -- 192.168.0.0/24 192.168.0.0/24
RETURN all -- anywhere 192.168.0.1
RETURN all -- anywhere 192.168.1.254
DROP all -- anywhere anywhere mark match 0xa
NFQUEUE all -- anywhere anywhere NFQUEUE num 92

Chain pgl_in (1 references)
target prot opt source destination
RETURN all -- link-local/16 anywhere
RETURN all -- 192.168.0.0/24 anywhere
RETURN all -- anywhere anywhere
DROP all -- anywhere anywhere mark match 0xa
NFQUEUE all -- anywhere anywhere NFQUEUE num 92

Chain pgl_out (1 references)
target prot opt source destination
RETURN all -- anywhere link-local/16
RETURN all -- anywhere 192.168.0.0/24
RETURN all -- anywhere 192.168.0.1
RETURN all -- anywhere 192.168.1.254
RETURN all -- anywhere anywhere
REJECT all -- anywhere anywhere mark match 0xa reject-with icmp-port-unreachable
NFQUEUE all -- anywhere anywhere NFQUEUE num 92

Whilst iptables -t nat -L gives

Quote:

Chain PREROUTING (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

cynwulf · 03-25-2013, 05:36 AM

Disable IPv6.

onerous · 04-14-2013, 03:05 PM

Sorry taken a while to get back to this.

Why would there suddenly be a problem when there wasn't before? Having installed debian for the same disc on another laptop, a friends old Dell D600. I have compared that laptop to mine,. On her laptop:

When I do cat etc networks, this is the output

Quote:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback

Whilst iptables l gives this

Quote:

Chain 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
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Why would my laptop ber different to the other?

onerous · 04-25-2013, 02:04 PM

Came back to this today. So initially check that I had IPv6 running by using this command netstat -tunlp |grep p6 |wc -l. Two process came up.

So did these three steps

echo net.ipv6.conf.all.disable_ipv6=1 > /etc/sysctl.d/disableipv6.conf

sed '/::/s/^/#/' /etc/hosts >/etc/dipv6-tmp;cp -a /etc/hosts /etc/hosts-backup && mv /etc/dipv6-tmp /etc/hosts

sed '/ipv6=yes/s/yes/no/' /etc/avahi/avahi-daemon.conf >/etc/avahi/dipv6-tmp;cp -a /etc/avahi/avahi-daemon.conf /etc/avahi/avahi-daemon.conf-backup && mv /etc/avahi/dipv6-tmp /etc/avahi/avahi-daemon.conf

Rebooted and ran the netstat command again and 0 came up.

Same as before.

frankbell · 04-25-2013, 07:43 PM

I don't have a solution, but a long-shot suggestion; it's more a "rule out" idea than anything else. At the least, if it works as I expect, you can rule one more possibility out of the list of suspects.

Boot to a live CD of something and test your network connections, both wired and wireless. If they work, it's almost certainly something to do with your software load/configuration. If they don't, there may be some weirdo hardware thing going on.

onerous · 04-29-2013, 05:15 PM

Gave up and reinstalled the operating system, everything is fine now.