>
> Static IPs are often required by users and admins in corporate networks,
> also some home users may be statically assigned in some special
> configurations. Developers and consultants that move between development
> networks and corporate networks need the flexibility to change their
> configurations regularly and keep multiple profiles.
>
> I see no valid reason why it should not be supported, nor why network
> manager fails altogether when it is used. It is basic networking, in
> fact Static support should have been implemented before DHCP.


Static IP addresses are supported in NM 0.7, which is looking likely to be
finished in the Hardy timeframe.

We are all very aware of the reasons for supporting static IP addresses: the
upstream developers targeted NM at a very specific use case (laptop users
with wireless networks), and then added VPN support so they could connect
back to the Red Hat private network via vpnc.  As the time has gone on, the
project has got good enough to be used for some other purposes, but not
all.  The answer is "they know, but there's just not enough people working
on it to do everything at once".

-- 
Can't use static ip address with network-manager (and thus no VPN connections 
menu for static users)
https://bugs.launchpad.net/bugs/5364
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to