no cable network

Bug #270153 reported by eva
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hello,

This is an Acer laptop Aspire 1640. I normally connect to internet through wireless. This time I plugged int the Ethernet cable and I had internet. No ping to the Gateway, no ping to www.google. I don't use any firewall.
Doing

$ ifconfig

everything looked fine. I went to the Network icon, and changed "Itinerary mode" into "DHCP". But still didnt work. I changed into "Static IP" and it didn't work either. I did the following on a terminal, but still didnt work, and had an unknown error to me:

eva@eva-laptop:~$ sudo ifconfig eth0 192.168.2.2 netmask 255.255.255.0 up

eva@eva-laptop:~$ sudo route add default gw 192.168.2.1
SIOCADDRT: El fichero ya existe

eva@eva-laptop:~$ ifconfig
eth0 Link encap:Ethernet direcciónHW 00:16:36:2a:87:e0
          inet dirección:192.168.2.2 Difusión:192.168.2.255 Máscara:255.255.255.0
          dirección inet6: fe80::216:36ff:fe2a:87e0/64 Alcance:Vínculo
          ARRIBA DIFUSIÓN CORRIENDO MULTICAST MTU:1500 Métrica:1
          RX packets:299 errors:0 dropped:0 overruns:0 frame:0
          TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:1000
          RX bytes:24929 (24.3 KB) TX bytes:39970 (39.0 KB)
          Interrupción:17 Dirección base: 0x2000

eth1 Link encap:Ethernet direcciónHW 00:13:ce:c0:b5:45
          inet dirección:192.168.2.4 Difusión:192.168.2.255 Máscara:255.255.255.0
          ARRIBA DIFUSIÓN MULTICAST MTU:1500 Métrica:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupción:16 Dirección base: 0x6000 Memoria:b0101000-b0101fff

lo Link encap:Bucle local
          inet dirección:127.0.0.1 Máscara:255.0.0.0
          dirección inet6: ::1/128 Alcance:Anfitrión
          ARRIBA LOOPBACK CORRIENDO MTU:16436 Métrica:1
          RX packets:2948 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2948 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:0
          RX bytes:159100 (155.3 KB) TX bytes:159100 (155.3 KB)

eva@eva-laptop:~$ ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
From 192.168.2.4 icmp_seq=1 Destination Host Unreachable
From 192.168.2.4 icmp_seq=2 Destination Host Unreachable
From 192.168.2.4 icmp_seq=3 Destination Host Unreachable

--- 192.168.2.1 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3007ms
, pipe 3

eva@eva-laptop:~$ ping www.google.es
ping: unknown host www.google.es

eva@eva-laptop:~$ uname -r
2.6.24-19-generic

I never heard of this error message before:

SIOCADDRT: File exists

I attach the /var/log/syslog file.

Thank you.

Eva.

Revision history for this message
eva (evammg) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue. Thanks.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi eva,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 270153

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
eva (evammg) wrote :

Hello,

I have copied and pasted what you said, but it says it doesnt find the order. This is what I have done:

eva@eva-laptop:~$ apport-collect -p linux 270153
bash: apport-collect: orden no encontrada

So I looked for it in the repositories and:

eva@eva-laptop:~$ aptitude search apport-collect
eva@eva-laptop:~$ aptitude search apport
i apport - automatically generate crash reports for d
i apport-gtk - GTK+ frontend for the apport crash report
p apport-qt - Qt4 frontend for the apport crash report s
p apport-retrace - tools for reprocessing Apport crash report
i python-apport - apport crash report handling library

I have Ubuntu 8.10 and:

eva@eva-laptop:~$ uname -r
2.6.24-24-generic

Anyways, my Ubuntu works perfect now. This is not an issue any more, but if you still need me to run that command, let me know what to do about it.

Thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Eva,

I'm going to go ahead and mark this as fixed based on your previous comment. No need to run the apport-collect command. Also, just for future reference, the apport-collect command in only supported in Jaunty or newer releases. Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.