Same bug on Maverick Meerkat... Knorr could you explain some more your
workaround it's not clear enough for me...
--
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 becaus
** Changed in: network-manager
Status: Invalid => Expired
** Changed in: network-manager
Importance: Unknown => Medium
--
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 not
sorry about poor english
--
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 Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
Workaround: create dummy DSL connection and fill ip settings
then gconf-editor - found dummy DSL connection (last one), copy paste to needed
VPN connection, and don't forget to change maethod from "auto" to "manual".
--
Can't use static ip address with network-manager (and thus no VPN connection
Speaking about Kubuntu and not Ubuntu, I noticed the the "Auto Eth0" and its
"Connect automatically" flag is not editable. This makes impossible to create a
custom connection (ie for static ip).
At each startup the "Auto Eth0" takes priority over all other connections.
I have filed a bug report
Workaraund from post №93 not work for VPN connections in lucid.
No way.
--
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 Kubuntu
Bugs, which
Bug still present for VPN connections in lucid.
5 years past...
Fast bugfixing...
--
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 Kubuntu
Bu
** Changed in: network-manager (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for static users)
https://bugs.launchpa
i resolved my problem.
The guilty was nm-connection-editor who didn't save the gateway configuration,
even if i wrote it.
Workaround:
- open gconf-editor
- search in /system/networking/connections the problematic connections ( 8, in
my case)
- open the voice ipv4
- in addresses, i replaced the l
i have Ubuntu 8.10 64 bit
i tried a static configuration, using NM-configuration editor, of my WPA
wireless network, but i have problem with gateway settings, even if i filled
the necessary info
nm-tool output:
- Device: wlan0
Ty
The KNetworkManager portion of this is being tracked in bug 280762, and
it has a fair amount of duplicates itself so it probably won't be marked
a dupe of this bug.
** Changed in: knetworkmanager (Ubuntu)
Status: New => Invalid
--
Can't use static ip address with network-manager (and thus
Thank you, Andrew and Howl. :)
--
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
Artist, it's a bug since NetworkManager 0.7 support static ip addresses.
The steps you describe are necessary with nm < 0.7, and, anyway is
easiest to use the now obsolete gnome network graphical manager, only
need to set "modo intenerante" (spanish) to off and the configure the
network.
--
Can'
On Mon, Dec 8, 2008 at 11:47 AM, Artist <[EMAIL PROTECTED]> wrote:
> It's not a bug.
Yes, it was. And it's fixed now. :)
--
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 notificat
Example for set a static IP:
1. edit (as root) /etc/NetworkManager/nm-system-settings.conf:
-
[ifupdown]
managed=true
-
2. edit (as root) /etc/network/interfaces
-
auto lo
iface lo inet loopback
a
It's not a bug. Read /usr/share/doc/network-manager/README.Debian,
please.
To manager your network manually,
First to edit (as root) /etc/NetworkManager/nm-system-settings.conf:
[ifupdown]
managed=true
then edit your /etc/network/interfaces and /etc/resolv.conf for your IP
and name server.
I also found that gheeke's solution workds for me, but, if this isn't a
bug, it's very bad user interface design. The order that you follow the
steps matters - and I can't see why it should.
If I add a static connection and then delete the system-created dhcp
auto-eth0 connection, the dhcp connec
In any case, it works for me. I follow gheeke's coments and now I have
my fixed IP when restarting PC. Thank you very much (three days of
configuring network remember me Windows age; a not very interesting
moment of my computer live)
--
Can't use static ip address with network-manager (and thus n
gheeke thanks for the info, but you missed something, tick the "System
Setting" option, (for me appears as "Ajustes del sistema" in Spanish).
If you remove the auto eth0 and create your own network as system
network it will ask for permission when applying it. If you try to make
a network when the
> Static IP gets reset back to DHCP after every reboot
The following workaround works for me:
Open NetworkManager, Edit Connections. Delete the default connection
(auto eth0). Add a new connection with the static ip address
information. Somewhere during this process, the NetworkManager asks for
a
Can confirm behaviour by Agostino Russo.
Static IP gets reset back to DHCP after every reboot.
--
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
Alex,
Not sure if I did anything wrong, but using intrepid daily of 26-09, the
static IP settings entered via nm-connection-editor get reset at reboot
to dhcp.
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for static users)
https://bugs.launchpad.net/bugs
fixed in NM 0.7 (intrepid). static ips as well as lots of other tweaking
is now available through NetworkManager applet.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for sta
I have the same problem. Moved from 7.10 to 8.04. /etc/interfaces is:
auto lo
iface lo inet loopback
iface dsl-provider inet ppp
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
provider dsl-provider
auto eth0
iface eth0 inet static
address 172.16.2.3
netmask 255.255.255.0
gateway
I think I can understand that.
it is an annoyance, but probably not as much as it not working atall.
I also have to use static IP's, but what i've recently done is set DHCPD
up so that it knows of the mac Address's and then issues the same IP's
all the time. my problem is my laptop with a Netgear
Craig Box wrote:
>> On mainstream bug http://bugzilla.gnome.org/show_bug.cgi?id=156952 is
>> closed as obsolete, but with Hardy I can't use the VPN stuff with
>> network manager if I use static IP.
>
> Upstream has moved to 0.7, but Ubuntu has not yet. 0.7 is more a
> development-in-progress bran
> On mainstream bug http://bugzilla.gnome.org/show_bug.cgi?id=156952 is
> closed as obsolete, but with Hardy I can't use the VPN stuff with
> network manager if I use static IP.
Upstream has moved to 0.7, but Ubuntu has not yet. 0.7 is more a
development-in-progress branch than a completely stabl
On mainstream bug http://bugzilla.gnome.org/show_bug.cgi?id=156952 is
closed as obsolete, but with Hardy I can't use the VPN stuff with
network manager if I use static IP.
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for static users)
https://bugs.launchp
Indeed many networks require static IP address, even over a WPA wireless
network... which is difficult to cobble together without creating a
special wpa_supplicant config for that network. Net exactly nice when
you guys have done such a great job making WPA simple.
** Also affects: knetworkmanag
This bug should be priority. A lot of people need to use VPN while they
are connected using an static IP for a lot of reason.
My reason: Some Internet suppliers provide one static IP by ethernet. If
people want to use a bridge to have wireless connection they need to ask
for the given IP to the br
I just want to add my comment to those above. This problem is a show-
stopper for me. It makes it impossible for me to use or to recommend
Hardy, which I otherwise think is a terrific distribution.
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for static
Unfortunately I have to agree with Blue. Isn't it really possible to do
something with that?
--
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
The ChenMing's solution is very nice for me (either on desktop that
laptop). I have changed only eth and gw's ip number:
# Add following lines to /etc/rc.local to setup a static ip address and
default route.
ifconfig eth0 192.168.0.20
route add default gw 192.168.0.10
After a simple restart it'
Well,we are a few years later and the same problem persists. You can now
configure the network manually and set a static ip for wireless - but
the setting it's not applied; Also network profiles still suck (as in
they do not work at all at remembering combinations of wired/wireless
settgins correct
Many people here are experiencing the bug where the static IP is not
assigned on startup (bug #187274), which is different to this bug as
originally submitted.
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for static users)
https://bugs.launchpad.net/bugs/
I have encountered this bug in the Hardy Beta as well. I set static IP
by choosing "Manual configuration" in the Network Manager. I have been
getting around it by opening the Network Manager, setting it to DHCP and
then resetting it to Static IP. After that it works again (until the
next reboot)
This appears to have worked. Thank you very much!
On Tue, Mar 25, 2008 at 5:49 AM, ChenMing <[EMAIL PROTECTED]> wrote:
> I meet the probem today, in the lastest.
>
> To do a workaround, I use /etc/rc.local to set my static address and
> default gateway. Maybe this way can help you.
>
> # Add foll
I meet the probem today, in the lastest.
To do a workaround, I use /etc/rc.local to set my static address and
default gateway. Maybe this way can help you.
# Add following lines to /etc/rc.local to setup a static ip address and default
route.
ifconfig eth0 192.168.168.30
route add default gw 192
I too have the problem mentioned above with the latest Hardy Heron
release.
The only way I'm currently able to connect to the internet is by using
"roaming mode." In 7.10 I was able to configure a static IP address.
Here I am able to configure a static IP address, but it does not seem to
work at a
I've the same problem of Wari Wahab in the Hardy Heron (latest version).
I've a common Alice Router with DHCP activated, but static IP address
not function (network is unreachable). Practically only "roaming mode"
it's OK with nm-applet 0.6.6.
In Windows function all, with or without DHCP, with or
On Thu, Feb 28, 2008 at 10:29 AM, Wari Wahab <[EMAIL PROTECTED]> wrote:
> Craig: I setup static IP using the nm-applet, not by editing the
> /etc/network/interfaces by hand. In 8.04, it disables networking
> entirely until I updated network-manager package. Still, apps like
> firefox, and nm-apple
Craig: I setup static IP using the nm-applet, not by editing the
/etc/network/interfaces by hand. In 8.04, it disables networking
entirely until I updated network-manager package. Still, apps like
firefox, and nm-applet reports that I have no working network.
Now if I just installed ubuntu, and lo
In regards to Craig's comment above, I am running Ubuntu 7.10 - Gutsy
Gibbon. I prefer to use a static IP. However, I have been stuck with
using DHCP for the past year or so, because when network-manager is
configured with a static IP, I cannot use it to connect to a VPN. The
'VPN Connections' o
Wari: you can assign "pseudostatic" address even via DHCP based on your
MAC address, granted you have admn priviledges on the router.
--
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
I haven't spent much time running 7.10 so I can't comment for sure on the
behaviour there, but my understanding is that if you set a static IP
address in /etc/network/interfaces, your networking will still work, but
you won't get the wireless selection and VPN abilities of NetworkManager.
Is this
Installed the latest network-manager package (0.7) and what I managed to
get static ip work, after a reboot. The system boots up with the static
IP, without the need to login, which is the behaviour I like (compared
with other distros). nm-applet however reports "No network connection"
even though
The behaviour Wari Wahab described above is definitely a regression (and
I can confirm that it works on 7.10, using nm-applet 0.6.5; and the
interface is marked as static in /etc/network/interfaces) - it really
needs to continue to work in 8.04.
--
Can't use static ip address with network-manager
It has never been possible to use a network card configured statically with
NetworkManager. If you set it static in /etc/network/interfaces then NM just
doesn't see it.
It is supported in 0.7, which is not final, and not yet in Ubuntu. Have a
look at http://ubuntuforums.org/archive/index.php/t-67
If it is not possible to set a static IP address in 8.04 - or possible
only by bringing up interfaces manually with ifconfig, then this is a
serious regression. Please fix this.
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for static users)
https://bugs.l
I'm sure network-manager is supposed to support multiple configurations.
I need static IP on my system, I'm not using WiFi.
Here's what I do:
* Click on nm-applet,
* chose Manual Configuration
* Click unlock
* Chose eth0
* Uncheck Enable Roaming Mode
* Change the configuration to use static
I'm just adding a bump here. Reading through the thread I'm at a loss as
to why it's so complicated with regards to vpnc. I have a desktop at
home and a laptop. On my laptop, I can use the Network Manager applet to
fire up the VPN connection with work (because of the current design,
this is because
This bug was nominated for Gutsy but does currently not qualify for a 7.10
stable release update (SRU) and the nomination is therefore declined.
According the the SRU policy, the fix should already be deployed and tested in
the current development version before an update to the stable releases w
While this is wishlist, as the software doesn't advertise the feature,
it is a pretty basic and essential wish.
When I go to school we have a wireless access point that is not linked
to a DHCP server, I must connect and request an IP that has been
assigned to me. I can do this fine with the tradit
I should add that the behavior for me is that the system works for a
while, then all of a sudden it can't browse the web, and linux machines
on my local net can't ssh into it. However, Macs can ssh into it, and
they can do so using the avahi name .local
--
Can't use static ip address with networ
This is a very serious BUG; I can't understand how it can be marked
"wishlist." That designation should be reserved for feature requests.
--
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 th
>
> 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
> configur
So after spending a DAY trying to figure out why none of the VPN setup
guids seem to work for me I find the answer here.
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 consultan
I would also like to make a VPN connection using NetworkManager when my
internet connection is statically defined.
It would be great if this could work in Feisty.
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for static users)
https://bugs.launchpad.net/b
network-manager with network-manager-openvpn in gutsy 7.10 still cannot find an
active device when it`s configured as static ip...
This behaviour is not accepted for normal use of nm with openvpn plugin :( :( :(
--
Can't use static ip address with network-manager (and thus no VPN connections
m
** Changed in: network-manager (Ubuntu)
Assignee: Tollef Fog Heen (tfheen) => (unassigned)
--
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
I want this functionality too !
Because i use the WPA encryption and NFS for file sharing with my other
computer ...
--
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 be
** Summary changed:
- Can't use static ip address with network-manager
+ Can't use static ip address with network-manager (and thus no VPN connections
menu for static users)
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for static users)
https://bugs.lau
We still have the problem that you can't support a VPN connection with a
static IP address, as per bug 114700.
--
Can't use static ip address with network-manager
https://bugs.launchpad.net/bugs/5364
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct sub
> Marking as fix released. Feel free to post and correct me if this is
not the case.
Static IP configuration still doesn't work as default in Ubuntu Feisty
final if network-manager is used. Problem still left the same, like I
described in this comment:
https://bugs.launchpad.net/baltix/+bug/5364/c
Marking as fix released. Feel free to post and correct me if this is not
the case.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Cool, the bug is fixed for me with network-manager-0.6.4-6ubuntu3.
Putting the interface in static IP mode will not cause NM to disconnect.
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
NM should not "disconnect" if a static IP is set. That's the bug.
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Well, that's only one of a few issues that arises from this problem.
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The issue about it acting disconnected is bug #82335 now, which has
quite a number of duplicates, and has High importance. People may wish
to move over there instead.
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
ubuntu-bugs@list
On 3/11/07, Billy Kwong <[EMAIL PROTECTED]> wrote:
> ** Changed in: network-manager (Ubuntu)
>Status: Fix Released => Rejected
As far as getting this fixed, Rejected is no better than Fix Released.
** Changed in: network-manager (Ubuntu)
Status: Rejected => Confirmed
--
Can't use
The menu item doesn't fix the problem. As I said before, the moment you
switch to a static IP configuration using network-admin (I even went to
the menu item added), and NM automatically shows that the connection is
disconnected, and liferea/gaim/epiphany goes into offline mode.
Basically, if the
Billy and co. are right. Gaim will not connect if you have your
connection configured manually, among other apps. As NM is now on by
default, this needs to be resolved. Before Feisty.
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
Yes, the "static configuration" menu item would bring up network-admin,
but Network Manager would consider the interface to be "disconnected"
when a static IP is set.
Basically if there is an entry for the corresponding eth interface in
/etc/network/interface, NetworkManager would show the disconn
On 3/9/07, Matt Zimmerman <[EMAIL PROTECTED]> wrote:
> A "Static configuration" menu item has been added to nm-applet in Feisty
> so that this is easy to find. static configuration isn't yet integrated
> with network-manager, but this gets the job done by launching the
> appropriate tool.
>
> **
A "Static configuration" menu item has been added to nm-applet in Feisty
so that this is easy to find. static configuration isn't yet integrated
with network-manager, but this gets the job done by launching the
appropriate tool.
network-manager (0.6.4-6ubuntu2) feisty; urgency=low
* Add "stati
Hi,
On Wed, Mar 07, 2007 at 08:38:12AM -, Tollef Fog Heen wrote:
> * Mantas Kriaučiūnas
> | I've just tried to configure "Static configuration" (by clicking on
> | network-managet icon in notification area and choosing "Static
> | configuration..."):
>
> The failure to activate the interface
Technically, activating the interface isn't a problem. The problem is in
switching back and forth between static and DHCP-configured networks.
The process to do so is neither intuitive nor trivial.
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bug
* Mantas Kriaučiūnas
| I've just tried to configure "Static configuration" (by clicking on
| network-managet icon in notification area and choosing "Static
| configuration..."):
The failure to activate the interface would be a network-admin bug,
not a network-manager bug.
The only real bug I see
I agree with James. Also, if I understand correctly the upstream bug
linked at the top, this actually is implemented, but Ubuntu doesn't use
it right. So I'd say it's really an Ubuntu bug.
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing
Hmm, with the fact that NM is now included by default in Feisty and the
noted issues with other Gnome Software, could this bug be moved away
from wishlist and be an actual bug?
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
ubuntu
Why importance of this bug is set to wishlist ? AFAIK it's very
important problem if users can't establish internet connection if
network-manager is installed.
Accoring to comments at http://bugzilla.gnome.org/show_bug.cgi?id=412018 this
is Ubuntu bugs:
Comment #3 from Dan Williams (NetworkMana
My mistake, wrong link.
http://bugzilla.gnome.org/show_bug.cgi?id=412018
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
There is another report upstream that is pretty much identical but more
specific to Ubuntu .
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/87941
Feisty relies on nm-applet quite a bit so hopefully this will get fixed.
--
Can't use static ip address with network-manager
https://
** Changed in: network-manager (upstream)
Status: Unknown => Rejected
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Looks like this was reported upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=156952.
However, that seems to imply (please correct me if I'm wrong) that
Ubuntu's missing something to make static configuration work with n-m.
** Bug watch added: GNOME Bug Tracker #156952
http://bugzilla.gnome
Another issue: with n-m running and the network set to a static IP, the
(increasingly common) autodetection from other programs--Banshee, Gaim,
Liferea, etc.--doesn't work. See bug # 79267 for an example. I'm sure
there are others.
--
Can't use static ip address with network-manager
https://launc
I confirm that and I cannot understand why this issue isn't taken seriously
enough.
In dapper I wasn't able to use my wireless WPA network out of the box - I
thought okay, NM was just out so edgy will make it. But again - no wireless
connection using a current encryption mode (WEP is a long tim
** Also affects: Baltix
Importance: Untriaged
Status: Unconfirmed
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
... it should support both static addresses AND network profiles for mobile
users.
Further, there should be only one way to set up network interfaces
:network-admin or network manager.
As I posted on another bug report, network admin can do some things but
miserably fails at others and vicevers
Well, I do not know whether network-manager should support your
particular setup (two network addresses is not very common). But it
should be able to support roaming between static and dynamic ip address
networks.
--
Can't use static ip address with network-manager
https://launchpad.net/bugs/5364
If you think about it, the whole point of an app like network manager is
to allow easy catering for the variety of different networks while
roaming. There's little point in having it for a stand alone
workstation that never leaves the network. As a user we are not always
able to define what a par
91 matches
Mail list logo
