bad resolv.conf DNS when connecting G3 modem (iplus - polish/PL ISP)

Bug #296799 reported by LimCore
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

ubuntu 8.10 amd64
G3 modem Huawei E169
Polish (PL) network provider iPlus

When modem connects (using nm-applet) then the /etc/resolv.conf is set to black hole IPs:

# Generated by NetworkManager
nameserver 10.11.12.13
nameserver 10.11.12.14

The DNS that work for this provider (I took it from some web forum google) are:

nameserver 212.2.96.54
nameserver 212.2.96.55

(best verify it officially, if it has to be hardcoded... or perhaps just the auto-detection code is not working well or something?)

LimCore (limcore)
description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release the Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in network-manager (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Mathias Friman (mathias-friman) wrote :

Freshly installed Karmic RC and the problem is still there (more or less).

Huawei E220 HDSPA-modem with Swedish Telia as a provider. The connection establishes just fine, but the /etc/resolv.conf remains blank, except

"# Generated by NetworkManager"

Setting the nameservers manually in said file solves the problem. The same setup works just fine in 9.04

packages installed:
network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1

What more information do you need?

Revision history for this message
LimCore (limcore) wrote :

Yes, so the problem is on 8.10 but it is fixed in 9.04.
Perhaps someone should just backport the solution to 8.10

Changed in network-manager (Ubuntu):
status: Incomplete → Confirmed
Thomas Hood (jdthood)
Changed in network-manager (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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