← Back to team overview

desktop-packages team mailing list archive

[Bug 920623] Re: Save IP in manual IPv4 settings

 

Why not use a separate connection for this instead?

You can easily achieve this by having a connection called "Manual" for
the static IP setting, and another "Automatic" or whatever for automatic
IP addressing.

This is not a bug; closing as Invalid.

** Changed in: network-manager (Ubuntu)
       Status: New => Invalid

-- 
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/920623

Title:
  Save IP in manual IPv4 settings

Status in “network-manager” package in Ubuntu:
  Invalid

Bug description:
  When I go to network connections, and select a particular connection,
  and go to edit., in the IPv4 tab, I need to often switch between
  automatic, and manual config. It would be convinient that if i choose
  manual and enter a IP, it gets saved. If I go to automatic later on,
  and switch back to manual, it should have the manual IP i had
  initially typed, as the default manual ip. This should be instead of
  requiring me to typing out the desired ipagain.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: network-manager 0.9.1.90-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Tue Jan 24 01:07:49 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 10.3.8.1 dev eth0  proto static 
   10.3.8.0/24 dev eth0  proto kernel  scope link  src 10.3.8.61  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   172.16.189.0/24 dev vmnet8  proto kernel  scope link  src 172.16.189.1 
   192.168.168.0/24 dev vmnet1  proto kernel  scope link  src 192.168.168.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://10.1.9.33:8080/
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-01-15T00:11:34.057419
  no_proxy: localhost,127.0.0.0/8

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


References