vodafone k3805-z requires "ifconfig usb0 -arp" prior to connecting to achieve connectivity

Bug #764003 reported by Pedro Francisco on 2011-04-17
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: modemmanager

Vodafone 3g pen k3805-z requires "ifconfig usb0 -arp" prior to connecting to achieve connectivity. It appears as if everything is blocked unless arp is disabled.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: modemmanager 0.4+git.20110124t203624.00b6cce-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sun Apr 17 22:48:16 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 LANGUAGE=en
 LANG=pt_PT.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: Upgraded to natty on 2011-04-07 (10 days ago)
---
AcpiTables: Error: command ['gksu', '-D', 'Apport', '--', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 3: Error copying '/home/ubuntu/.Xauthority' to '/tmp/libgksu-QrpIwZ': No such file or directory
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
Architecture: i386
AudioDevicesInUse:
 Cannot stat file /proc/3214/fd/11: Stale NFS file handle
 Cannot stat file /proc/3214/fd/12: Stale NFS file handle
 Cannot stat file /proc/3955/fd/32: Stale NFS file handle
                      USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3194 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf8600000 irq 47'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,103c30cc,00100003 HDA:10573055,10573055,00100700'
   Controls : 20
   Simple ctrls : 12
DistroRelease: Ubuntu 11.10
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110531.1)
MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
Package: linux (not installed)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper iso-scan/filename=/ISOtest/oneiric-desktop-i386.iso
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
RelatedPackageVersions:
 linux-restricted-modules-2.6.39-3-generic N/A
 linux-backports-modules-2.6.39-3-generic N/A
 linux-firmware 1.53
Tags: oneiric unity-2d
Uname: Linux 2.6.39-3-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/25/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.59
dmi.board.name: 30CC
dmi.board.vendor: Quanta
dmi.board.version: 79.2E
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.2E:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6500 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

Reassigning to 'linux', since that sounds very much like something that would need fixing at the kernel level, even though I'm not certain how this would be achieved.

FWIW, disabling arp doesn't sound like such a great idea, even though it's probably much less of an issue for connection with a phone.

affects: modemmanager (Ubuntu) → linux (Ubuntu)
thecityofgold (simon-haighmail) wrote :

Also a problem in Natty as of 18th May, and fixable by 'ifconfig usb0 -arp' before connection.

apport information

tags: added: apport-collected oneiric
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Also on Oneiric.
Will add the tag manually since I can't add Oneiric anywhere else.

Brad Figg (brad-figg) on 2011-06-25
Changed in linux (Ubuntu):
status: New → Confirmed

FYI, the driver on Windows 7 has an option which says "Enable promiscuous mode" (?on a 3G pen?) which, after enabled, results on the same behavior as if one does "ifconfig usb0 arp" on Linux.

Description of problem:
Vodafone k3805-z requires "ifconfig usb0 -arp" prior to connecting to achieve connectivity

Version-Release number of selected component (if applicable):
0.4.998 - 1.git20110706.fc15

How reproducible:
Always.

Steps to Reproduce:
1. plug usb modem and workaround whatever needed to connect (#697122)
2. try to ping/access some site

Actual results:
Nothing happens (Wireshark shows ARP requests being sent to every IP one tries to connect with)

Expected results:
Ping should be successful.

Additional info:
$ route -n [with or without NOARP]
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 usb0

Also, the driver on Windows 7 has an option which says "Enable promiscuous mode" (?on a 3G pen?) which, after enabled, results on the same behavior as if one does "ifconfig usb0 arp" on Linux.

I can confirm this bug, with this hardware.

The "ifconfig usb0 -arp" workaround works.

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel currently in the release pocket than the one you tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-11.17

Confirmed with kernel 3.0.0-9-generic of Ubuntu oneiric (development branch) [LiveCD]

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-11.18
Gary M (garym) wrote :

Confirmed with beta kernel version 3.0.0.11.18.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.19
Gary M (garym) on 2011-09-24
tags: added: kernel-net
Gary M (garym) wrote :

Confirmed with beta kernel version 3.0.0-12.19.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Gary M (garym) wrote :

Confirmed with release-candidate kernel version 3.0.0-12.20.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? 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.

tags: added: needs-upstream-testing

Huh, quite odd. Probably something we should do for all 3G devices that provide eth ports, since they are all acutally point-to-point underneath. I have just bought a K3805z off ebay that I can use to test this out when it arrives.

@Dan Williams : Hello! Just to point out you will also find bug #745454 if using Gnome-Shell ;)

Also, I don't know if all devices are affected. Looking at https://github.com/andrewbird/wader/blob/master/resources/udev/99-wader-quirks.rules you can see a relatively small list of quirks.

(that URL is the temporary Git repo of Vodafone's https://forge.betavine.net/projects/bcm (which curiously is hidden from public project list), as the result of the migration off SVN https://forge.betavine.net/forum/forum.php?forum_id=245 )

Pedro Francisco, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you plug only the Vodafone k3805-z into a USB slot, execute the following in a terminal and report the results:
lsusb

As well, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

tags: added: bot-stop-nagging
removed: kernel-request-3.0.0-11.17 kernel-request-3.0.0-11.18 kernel-request-3.0.0-12.19 kernel-request-3.0.0-12.20
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete

Thank you for your time. I'm no longer using Ubuntu, can't test it.

Pedro Francisco, this bug report is being closed due to your last comment regarding you no longer using Ubuntu. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Gary M (garym) wrote :

Christopher, this issue has been confirmed by other people, and should not be closed based on your restriction of requests to the original reporter.

Changed in linux (Ubuntu):
status: Invalid → Confirmed

Gary M, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/764003/comments/35 , those who are not the original reporter should file a new report so their bug may be addressed as soon as possible. This is well within both Ubuntu Kernel Team and Ubuntu Bug Control policy. If you have any further questions, please E-Mail me directly and we can discuss further. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Invalid

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

At least on Fedora 18, the device is now recognized as "wwan0" and no longer requires ifconfig INTERFACE_NAME -arp .

Closing bug.

Changed in linux (Fedora):
importance: Unknown → Undecided
status: Unknown → Fix Released
no longer affects: linux (Ubuntu)
affects: linux (Fedora) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Fix Released → New
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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