Nameserver addresses 4.2.2.1 and 4.2.2.2 end up in resolv.conf instead of ISP nameserver addresses -- Huawei E220
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: network-manager
When connecting in Karmic to my broadband connection the DNS informations isn't received around 70-80% of the times I connect, so I need to disconnect and reconnect until the info is received. (Confirmed by /etc/resolv.conf being empty except for a comment by the network manager)
I don't know if this relates to the same problem, but I also some times have a problem accessing pages after a while, like it somehow decided to block all signals. (resolv.conf still has the info and the modem shows it's connected)
I hope there's information enough to fix it, otherwise please instruct me on what to do to help debugging.
ProblemType: Bug
Architecture: amd64
CheckboxSubmission: 2483b723db6bd40
CheckboxSystem: fb5f7a2788cceff
Date: Tue Sep 22 08:43:42 2009
DistroRelease: Ubuntu 9.10
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
10.64.64.64 dev ppp0 proto kernel scope link src 95.209.250.39
169.254.0.0/16 dev ppp0 scope link metric 1000
default via 10.64.64.64 dev ppp0 proto static
Package: network-manager 0.8~a~git.
ProcEnviron:
LANGUAGE=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: network-manager
Uname: Linux 2.6.31-10-generic x86_64
WpaSupplicantLog:
Related branches
Changed in network-manager (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Confirmed |
summary: |
- network-manager: no dns recieved with mobile connectio (Huawei E220) + network-manager: no dns received with mobile connection (Huawei E220) |
summary: |
- network-manager: no dns received with mobile connection (Huawei E220) + network-manager: no dns received with mobile connectio (Huawei E220) |
summary: |
- network-manager: no dns received with mobile connectio (Huawei E220) + Nameserver addresses 4.2.2.1 and 4.2.2.2 end up in resolv.conf instead + of ISP nameserver addresses -- Huawei E220 |
I have this on Three in the UK, but AFAIK, it's an issue with the provider (teleco/ISP) not sending it. Disconnecting and Reconnecting from the menu once generally solves it, but network manager should have the sense to do this automatically.