<solved>unable to connect to wired connection

Questions about cabled networking
Forum rules
Before you post please read this

<solved>unable to connect to wired connection

Postby Lalitha niharika on Sat Feb 18, 2012 1:34 pm

I dual booted my Toshiba satellite c640 laptop with mint 11 and windows 7. I use proxy settings in college to connect to wireless network. My wired connection at home works properly in windows.Wireless works properly in both windows,mint in college.My problem is, at home, I am unable to use wired connection.It is not detecting connection even after changing proxy settings to no proxy or autodetect??How to solve this problem??? :( :roll:
Last edited by Lalitha niharika on Sun Mar 04, 2012 6:12 am, edited 4 times in total.
Lalitha niharika
Level 1
Level 1
 
Posts: 11
Joined: Sat Feb 18, 2012 1:25 pm

Linux Mint is funded by ads and donations.
 

Re: unable to connect to wired connection

Postby terdon on Sat Feb 18, 2012 8:47 pm

Hi, could you please connect your ethernet wire and then run the following commands (open a terminal and paste the commands there) and post their output :

Code: Select all
ifconfig

Code: Select all
dmesg| tail -50
User avatar
terdon
Level 4
Level 4
 
Posts: 270
Joined: Tue Jan 13, 2009 2:52 pm
Location: Marseille

Re: unable to connect to wired connection

Postby Lalitha niharika on Sun Feb 19, 2012 5:10 am

lalitha@lalitha-Satellite-C640 ~ $ ifconfig
eth0 Link encap:Ethernet HWaddr 00:26:6c:d2:c0:bb
inet6 addr: fe80::226:6cff:fed2:c0bb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:7653 (7.6 KB)
Interrupt:43

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:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3120 (3.1 KB) TX bytes:3120 (3.1 KB)

wlan0 Link encap:Ethernet HWaddr e0:ca:94:2f:d9:3c
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lalitha@lalitha-Satellite-C640 ~ $ dmesg| tail -50
[ 17.684437] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684439] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 17.684441] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684442] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 17.684444] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684446] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 17.684448] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684450] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 17.684452] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684453] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 17.684455] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684457] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 17.684459] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684461] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 17.684463] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684464] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
[ 17.684467] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684468] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
[ 17.684470] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 17.684472] cfg80211: Disabling freq 2484 MHz as custom regd has no rule that fits a 20 MHz wide channel
[ 17.685861] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
[ 17.691695] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[ 17.692262] Registered led device: ath9k-phy0::radio
[ 17.692291] Registered led device: ath9k-phy0::assoc
[ 17.692320] Registered led device: ath9k-phy0::tx
[ 17.692349] Registered led device: ath9k-phy0::rx
[ 17.692357] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf8760000, irq=17
[ 17.740454] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
[ 17.740461] cfg80211: World regulatory domain updated:
[ 17.740463] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 17.740467] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 17.740471] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 17.740475] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 17.740478] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 17.740481] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 18.009468] atl1c 0000:01:00.0: irq 43 for MSI/MSI-X
[ 18.009558] atl1c 0000:01:00.0: atl1c: eth0 NIC Link is Up<10 Mbps Half Duplex>
[ 18.035308] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 18.253754] Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04733/0xa40000/0xa0000
[ 18.253768] synaptics: Toshiba Satellite C640 detected, limiting rate to 40pps.
[ 18.288713] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6
[ 18.622099] ppdev: user-space parallel port driver
[ 20.116163] Bluetooth: L2CAP ver 2.15
[ 20.116168] Bluetooth: L2CAP socket layer initialized
[ 20.125275] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 20.125279] Bluetooth: BNEP filters: protocol multicast
[ 20.132718] Bluetooth: SCO (Voice Link) ver 0.6
[ 20.132723] Bluetooth: SCO socket layer initialized
[ 21.197796] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=600
[ 28.235640] eth0: no IPv6 routers present
lalitha@lalitha-Satellite-C640 ~ $
Lalitha niharika
Level 1
Level 1
 
Posts: 11
Joined: Sat Feb 18, 2012 1:25 pm

Re: unable to connect to wired connection

Postby AlbertP on Sun Feb 19, 2012 8:24 am

Lalitha niharika wrote:[ 18.009468] atl1c 0000:01:00.0: irq 43 for MSI/MSI-X
[ 18.009558] atl1c 0000:01:00.0: atl1c: eth0 NIC Link is Up<10 Mbps Half Duplex>

This is about your wired internet. It says the link is up, so it should be connected.

The atl1c driver is still experimental (which surprises me given that it's already in the Linux kernel for ages). The driver will be replaced by a better one, called alx. I don't know how to solve your problem for now.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 15
Level 15
 
Posts: 5870
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: unable to connect to wired connection

Postby terdon on Sun Feb 19, 2012 9:21 am

AlbertP wrote:The atl1c driver is still experimental (which surprises me given that it's already in the Linux kernel for ages). The driver will be replaced by a better one, called alx. I don't know how to solve your problem for now.


OK, but there are still be a couple of things you could try:

1. Reload the card's module (driver), ridiculous as it may be, this has sometimes helped me:
Code: Select all
sudo rmmod atl1c
sudo modprobe atl1c


2. Restart network manager:
Code: Select all
sudo service network-manager restart


3. Make sure your dhcp client is running:
Code: Select all
sudo dhclient eth0

Then run ifconfig again and post the output here:
Code: Select all
ifconfig



3. Since your card seems to be recognized ok but is not assigned an IP, try setting a static IP address. See this page for instructions:
http://www.addictivetips.com/ubuntu-linux-tips/how-to-assign-static-ip-address-in-ubuntu-linux/

If you do not know what to enter, the Gateway is whatever your router is, often "192.168.1.1". Netmask is usually "255.255.255.0" and the DNS servers depend on your internet service provider, either do a google search for "provider_name DNS", or if you can connect using your wireless card, do so, and then right click on the network manager icon on the panel, chose connection information and copy the necessary information from there.
User avatar
terdon
Level 4
Level 4
 
Posts: 270
Joined: Tue Jan 13, 2009 2:52 pm
Location: Marseille

Re: unable to connect to wired connection

Postby Lalitha niharika on Sun Feb 19, 2012 1:02 pm

kkk..thanks..
Let me tell you one more thing, I used to connect it to wired network before setting proxy. After setting proxy, I am unable to revert back... I mean, I can connect to wireless even after connecting to wired, but not to wired after using proxy for once...last time when I got same problem with ubuntu I just rebooted with mint, immediately booting I could connect to wired.Then I configured proxy. Same problem again occurred in mint also.I don't know why proxy is everywhere.I just configured in mozilla, but even when I try to install some new software, I get a statement "proxy is refusing"...
Lalitha niharika
Level 1
Level 1
 
Posts: 11
Joined: Sat Feb 18, 2012 1:25 pm

Re: unable to connect to wired connection

Postby terdon on Sun Feb 19, 2012 1:08 pm

Have a look at http://ubuntuforums.org/showthread.php?t=1575. Check that no proxy is set in any of the options mentioned there.

Still, I don't see how it can be a proxy issue, you don't have an ip address. Unless I am mistaken, that should be assigned before the proxy comes into play.
User avatar
terdon
Level 4
Level 4
 
Posts: 270
Joined: Tue Jan 13, 2009 2:52 pm
Location: Marseille

Re: unable to connect to wired connection

Postby Lalitha niharika on Sun Feb 19, 2012 1:22 pm

lalitha@lalitha-Satellite-C640 ~ $ sudo rmmod atlic
[sudo] password for lalitha:
ERROR: Module atlic does not exist in /proc/modules
lalitha@lalitha-Satellite-C640 ~ $ sudo modprobe atlic
FATAL: Module atlic not found.
lalitha@lalitha-Satellite-C640 ~ $ sudo service network-manager restart
network-manager start/running, process 2010
lalitha@lalitha-Satellite-C640 ~ $ sudo dhclient etho
SIOCSIFADDR: No such device
etho: ERROR while getting interface flags: No such device
etho: ERROR while getting interface flags: No such device
lalitha@lalitha-Satellite-C640 ~ $ ifconfig
eth0 Link encap:Ethernet HWaddr 00:26:6c:d2:c0:bb
inet6 addr: fe80::226:6cff:fed2:c0bb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:100 errors:0 dropped:0 overruns:0 carrier:3
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:27130 (27.1 KB)
Interrupt:43

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:392 errors:0 dropped:0 overruns:0 frame:0
TX packets:392 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28848 (28.8 KB) TX bytes:28848 (28.8 KB)

wlan0 Link encap:Ethernet HWaddr e0:ca:94:2f:d9:3c
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lalitha@lalitha-Satellite-C640 ~ $
Lalitha niharika
Level 1
Level 1
 
Posts: 11
Joined: Sat Feb 18, 2012 1:25 pm

Re: unable to connect to wired connection

Postby terdon on Sun Feb 19, 2012 1:26 pm

Try copying the commands directly from my previous post. atlic shouyld be atl1c (1 not i) and etho should be eth0 (0 as in 0.5 not o as in ok)
User avatar
terdon
Level 4
Level 4
 
Posts: 270
Joined: Tue Jan 13, 2009 2:52 pm
Location: Marseille

Re: unable to connect to wired connection

Postby Lalitha niharika on Sun Feb 19, 2012 1:52 pm

ooohh..sorry, I cant copy because there is no internet connection to my laptop, I am just viewing forum from another computer...
Lalitha niharika
Level 1
Level 1
 
Posts: 11
Joined: Sat Feb 18, 2012 1:25 pm

Re: unable to connect to wired connection

Postby Lalitha niharika on Sun Feb 19, 2012 1:59 pm

lalitha@lalitha-Satellite-C640 ~ $ sudo rmmod atl1c
[sudo] password for lalitha:
lalitha@lalitha-Satellite-C640 ~ $ sudo service network-manager restart
network-manager start/running, process 1823
lalitha@lalitha-Satellite-C640 ~ $ sudo dhclient eth0
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
lalitha@lalitha-Satellite-C640 ~ $ ifconfig
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:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3120 (3.1 KB) TX bytes:3120 (3.1 KB)

lalitha@lalitha-Satellite-C640 ~ $
Lalitha niharika
Level 1
Level 1
 
Posts: 11
Joined: Sat Feb 18, 2012 1:25 pm

Re: unable to connect to wired connection

Postby terdon on Sun Feb 19, 2012 2:02 pm

You missed the second command.
This will remove the driver:
Code: Select all
sudo rmmod atl1c


And this will reload it:
Code: Select all
sudo modprobe atl1c


I am just checking to see if reloading the module (driver) helps, so you need both commands, one after the other. Then run the rest.

PS. Don't worry, I know how easy it is to miscopy something :)
User avatar
terdon
Level 4
Level 4
 
Posts: 270
Joined: Tue Jan 13, 2009 2:52 pm
Location: Marseille

Re: unable to connect to wired connection

Postby Lalitha niharika on Sun Feb 19, 2012 2:36 pm

oops!! :roll: sorry again :o

lalitha@lalitha-Satellite-C640 ~ $ sudo rmmod atl1c
[sudo] password for lalitha:
lalitha@lalitha-Satellite-C640 ~ $ sudo modprobe atl1c
lalitha@lalitha-Satellite-C640 ~ $ sudo service network-manager restart
network-manager start/running, process 1996
lalitha@lalitha-Satellite-C640 ~ $ sudo dhclient eth0
lalitha@lalitha-Satellite-C640 ~ $ ifconfig
eth0 Link encap:Ethernet HWaddr 00:26:6c:d2:c0:bb
inet6 addr: fe80::226:6cff:fed2:c0bb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:81 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:20408 (20.4 KB)
Interrupt:43

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:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3120 (3.1 KB) TX bytes:3120 (3.1 KB)
Lalitha niharika
Level 1
Level 1
 
Posts: 11
Joined: Sat Feb 18, 2012 1:25 pm

Re: unable to connect to wired connection

Postby terdon on Sun Feb 19, 2012 2:50 pm

OK, well, that did not work. Did dhclient give any errors? Did you try setting a manual ip address (see previous post)?

Also, please post the output of this command:

Code: Select all
cat /etc/network/interfaces
User avatar
terdon
Level 4
Level 4
 
Posts: 270
Joined: Tue Jan 13, 2009 2:52 pm
Location: Marseille

Re: unable to connect to wired connection

Postby AlbertP on Sun Feb 19, 2012 3:43 pm

It now says it's connected to IPv6, while the dmesg output reported: eth0: no IPv6 routers present. Why it wouldn't just connect with IPv4, I have no idea.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 15
Level 15
 
Posts: 5870
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: unable to connect to wired connection

Postby terdon on Sun Feb 19, 2012 3:55 pm

AlbertP wrote:It now says it's connected to IPv6, while the dmesg output reported: eth0: no IPv6 routers present. Why it wouldn't just connect with IPv4, I have no idea.


Where do you get that from? This line has been there from the beginning:
Code: Select all
 inet6 addr: fe80::226:6cff:fed2:c0bb/64 Scope:Link


But that doesn't mean it is connected to IPv6 does it? It looks like a MAC address. In any case it still doesn't show an IP so, as I udnerstand it, it is not connected. Am I missing something?
User avatar
terdon
Level 4
Level 4
 
Posts: 270
Joined: Tue Jan 13, 2009 2:52 pm
Location: Marseille

Re: unable to connect to wired connection

Postby AlbertP on Mon Feb 20, 2012 9:41 am

This is not a MAC address. This is an IPv6 address, and it starts with fe80 just like IPv6 should normally do. But dmesg said the router does not offer IPv6... This might be a problem with the router's configuration.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 15
Level 15
 
Posts: 5870
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: unable to connect to wired connection

Postby terdon on Mon Feb 20, 2012 12:07 pm

In that case, it shouldn't be a problem. I have similar lines for my setup and can connect with no problem:

Code: Select all
$ifconfig
eth1  Link encap:Ethernet  HWaddr 00:26:b9:e3:00:a1 
        inet addr:10.1.1.168  Bcast:10.1.255.255  Mask:255.255.0.0
        inet6 addr: fe80::226:b9ff:fee3:a1/64 Scope:Link

Code: Select all
$ dmesg | grep router
[   46.402299] eth1: no IPv6 routers present
User avatar
terdon
Level 4
Level 4
 
Posts: 270
Joined: Tue Jan 13, 2009 2:52 pm
Location: Marseille

Re: unable to connect to wired connection

Postby AlbertP on Mon Feb 20, 2012 4:02 pm

In terdon's output also the inet line is mentioned, the computer's IPv4 address, but that line is absent at Lalitha niharika. IPv4 on his/her computer is somehow not active (I really have no idea why) and IPv6 doesn't work with the router.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 15
Level 15
 
Posts: 5870
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: unable to connect to wired connection

Postby terdon on Mon Feb 20, 2012 4:10 pm

Umm.. as far as I know IPv4 is up and running on my machine. I have a perfectly valid IP address. I also checked out two different servers in my lab and got a similar output, both inet and inet6 lines and the same error message in dmesg. I have been seeing that same message (eth1: no IPv6 routers present) for a while now on various machines and it has never been a problem. In all cases IPv4 is active, or at least the machines have valid IPv4 IPs and access to the internet.

I am very much not an expert on this but it sounds like the problem is elsewhere. I still think it is dhcp-related and might be solved by a static ip address.

EDIT: Ahh, you were refering to Lalitha's machine, not mine, sorry :oops:
User avatar
terdon
Level 4
Level 4
 
Posts: 270
Joined: Tue Jan 13, 2009 2:52 pm
Location: Marseille

Linux Mint is funded by ads and donations.
 
Next

Return to Ethernet

Who is online

Users browsing this forum: No registered users and 5 guests