*** This bug is a duplicate of bug 5364 ***
https://bugs.launchpad.net/bugs/5364
This _is_ a bug, not a wouldn't-it-be-nice wished-for feature. Network
manager should have remained an optional item to install, until it had
this capability. Once it became part of the standard install, useful
*** This bug is a duplicate of bug 5364 ***
https://bugs.launchpad.net/bugs/5364
The same problem.
**Please raise the priority of this as it's a bug from users'
perspective. People with static IP's cannot connect to certain services
(VPN), while DHCPed people can. It should have nothing to
*** This bug is a duplicate of bug 5364 ***
https://bugs.launchpad.net/bugs/5364
I second that motion. Moreover, this would be a terrific workaround to
the currently unresolved bug, where when using vpn, dhclient overwrites
the changes made by NetworkManager to /etc/resolv.conf. In a static
*** This bug is a duplicate of bug 5364 ***
https://bugs.launchpad.net/bugs/5364
I would vote for this bug (and its duplicates) to be elevated from wishlist
status.
It seems pretty important to be able to make vpn connections (using the
graphical nm tool) even when using a static IP
*** This bug is a duplicate of bug 5364 ***
https://bugs.launchpad.net/bugs/5364
I agree with tilman's comment: this functionality should not depend on
whether the address is statically defined or provided via dhcp.
--
VPN menu not accessible when not using dhcp
*** This bug is a duplicate of bug 5364 ***
https://bugs.launchpad.net/bugs/5364
I have the same problem. VPN options disappear when using a static IP
address.
--
VPN menu not accessible when not using dhcp
https://bugs.launchpad.net/bugs/107070
You received this bug notification because
*** This bug is a duplicate of bug 5364 ***
https://bugs.launchpad.net/bugs/5364
** Summary changed:
- VPN menu not accessible when using dhcp
+ VPN menu not accessible when not using dhcp
** This bug has been marked a duplicate of bug 5364
Can't use static ip address with
