We've obviously failed by not providing further information as to the
state of this fix -- and I'm not even sure this ever landed as a Lucid
SRU yet -- for that I'm very sorry. I'm also responsible for not getting
back to this bug any sooner.

Tony, could you please give me the information as to how far you got
with getting this SRU ready, and what else needs to be done to upload
that to lucid-proposed? There's at least one other fix that could be
bundled with this SRU, and it would be very good to have now despite how
close we are to Precise being released. Seems to me like it's probably a
pretty simple fix in Lucid.

I'm marking the floating task as Fix Released because I'm very certain
ICS works well in later releases. If not, we can (preferably) file new
bugs, or nominate the particular release.

** Changed in: network-manager (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/389006

Title:
  NetworkManager Internet Connection Sharing fails to route DNS

Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” source package in Lucid:
  Fix Committed

Bug description:
  Binary package hint: network-manager

  I am able to share an internet connection between two wireless NIC's. 
However, DNS routing does not work correctly.
   I have used the following procedure to verify that the problem is DNS: 
   
  Use the computer behind the NAT to navigate to http://72.14.205.104/ in 
Firefox, and verify that this works. Then, navigate to
  http://www.google.com and confirm that this does not work (Firefox says 
"Server not found"). 

  I was also able to confirm this by editing /etc/resolv.conf, setting the 
contents to be the same as the resolv.conf file on the computer sharing the 
internet connection with NetworkManager. After that, all hostnames resolved 
correctly on the computer
  behind the NAT. So, just so long as nameservers on the computer behind the 
NAT are set to the sharing computer's gateway's IP addres, everything works 
fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/389006/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to