---
examples/python/goi-device-state-ip4config.py | 4 ++--
examples/python/goi-list-connections.py | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/examples/python/goi-device-state-ip4config.py
b/examples/python/goi-device-state-ip4config.py
index 48116dc..be19b99
On 09/27/2012 10:22 PM, Gene Czarcinski wrote:
also request fqdn.fqdn;
also request fqdn.hostname;
also request fqdn.domainname;
These are DHCPv4 options which DHCPv6 client doesn't know.
also request dhcp6.hostname;
also request dhcp6.domainname;
I can't find such options in
On 10/01/2012 06:33 PM, Gene Czarcinski wrote:
One of the problems I see is that, while there are a couple of viable
dchp servers out there, where the ISC server is suppose to be the
industrial strength one, dhclient seems to be the only client for the
linux/*bsd/Unix systems.
I wonder if
On 09/26/2012 06:44 PM, Subhendu Ghosh wrote:
Can those patches or options be submitted again? dhcp is going thru a
re-write along with bind 10
Submitted to dhcp-sugg...@isc.org as [ISC-Bugs #31164]
I'll post the reply here.
--
Jiri
___
On 09/24/2012 02:45 PM, Gene Czarcinski wrote:
1. Modified nm-dhcp-manager.c and nm-dhcp-dhclient.c to put the
HOSTNAME or DHCP_HOSTNAME on the dhclient -6 command line using the
-F parameter. This tells dhclient to send the name as a fqdn.fqdn
to the dhcp server.
Hi,
the -F as well as
On 09/16/2012 09:55 PM, Gene Czarcinski wrote:
BTW, from the info in the dhcp-options man-page, I believe that
NetworkManager should be doing send fqdn.fqdn instead of send
host-name for IPv4. This should be with a plain name ... not a
qualified name. See the man-page.
The story behind
On 08/02/2012 09:50 AM, Tore Anderson wrote:
* Stuart Gathman
The problem is, I don't want the auto IP, *or* the private IPs. I
just want the DHCP6 IP. But when I select DHCP only in NM, it
then assigns only the DHCP IP, but no route! The behaviour I expect
with DHCP only is to still
ping
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
The test in verify() has been probably result of my
copy-paste-fu. It's wrong and useless anyway.
Those #defines are not used anywhere.
---
libnm-util/nm-setting-connection.c |8
libnm-util/nm-setting-connection.h |7 ---
2 files changed, 15 deletions(-)
diff --git
On 03/08/2012 02:53 PM, Tore Anderson wrote:
The best solution would obviously be to just fix the default firewall in
Fedora too, but the firewall infrastructure maintainer is refusing to
make that change.
In short, he doesn't seem likely to change his mind any time soon.
He actually did :-)
On 03/07/2012 10:55 PM, Tore Anderson wrote:
3) I saw the following error message appear in the logs a few times:
warn (p17p1) firewall zone add/change failed: (32) ZONE_ALREADY_SET
It happens when you for example restart NM and it tells firewalld to add
interface to zone, but firewalld
On 03/07/2012 10:26 AM, Ludwig Nussel wrote:
Jiri Popelka wrote:
Tell firewall to allow dhcpv6-client service for the given zone prior
to starting dhcpv6 client. We don't need to wait for the response
That looks odd to me. Why doesn't the zone config already allow dhcpv6
by default
On 03/06/2012 09:03 AM, Tore Anderson wrote:
Hi Jiri,
Tell firewall to allow dhcpv6-client service for the given zone prior
to starting dhcpv6 client. We don't need to wait for the response
because dhcp client keeps sending Solicit messages until it gets the
response (i.e. until firewall opens
Tell firewall to allow dhcpv6-client service for the given zone prior
to starting dhcpv6 client. We don't need to wait for the response
because dhcp client keeps sending Solicit messages until it gets the
response (i.e. until firewall opens the port).
---
src/Makefile.am
On 02/28/2012 07:00 PM, Jiri Popelka wrote:
On 02/28/2012 06:18 AM, Dan Williams wrote:
On Mon, 2012-02-27 at 23:27 -0500, Paul Wouters wrote:
Can we please address the following bug that is almsot two years old.
This bug causes long delays for people enabling IPV6, and causes
Fedora
When we want to change the zone an interface belongs to
we can't use firewalld's addInterface() because this one
doesn't allow to add interface to zone when it already
has been part of some other/same zone.
We need to use changeZone() method instead - hopefuly
this is the final name of this
Because firewalld has no idea what interface is part of which zone
we need to inform it after it (re)starts what interface belongs to which
zone.
---
src/firewall-manager/nm-firewall-manager.c | 19 +
src/firewall-manager/nm-firewall-manager.h |3 ++
src/nm-policy.c
---
src/nm-manager.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/src/nm-manager.c b/src/nm-manager.c
index 146d491..d04a4e4 100644
--- a/src/nm-manager.c
+++ b/src/nm-manager.c
@@ -471,7 +471,9 @@ manager_device_state_changed (NMDevice *device,
On 02/28/2012 06:18 AM, Dan Williams wrote:
On Mon, 2012-02-27 at 23:27 -0500, Paul Wouters wrote:
Can we please address the following bug that is almsot two years old.
This bug causes long delays for people enabling IPV6, and causes
Fedora to not get any connectivity on IPv6 only networks,
The first patch updates FirewallD DBus service path interface.
The second one adds calling of FirewallD1.zone.removeInterface method
during device deactivation.
Jiri Popelka (2):
firewall: update FirewallD DBus service path interface
firewall: add remove_from_zone()
src/firewall-manager
---
src/firewall-manager/nm-firewall-manager.c |2 +-
src/firewall-manager/nm-firewall-manager.h |7 ---
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/firewall-manager/nm-firewall-manager.c
b/src/firewall-manager/nm-firewall-manager.c
index 00e3958..f20227e
nm_firewall_manager_remove_from_zone() is called from
nm_device_deactivate()
Also fix nm_firewall_manager_add_to_zone() to the latest
FirewallD1.zone.addInterface signature.
---
src/firewall-manager/nm-firewall-manager.c | 78 +++-
timeout some big number;
statement in /etc/dhcp/dhclient-interface.conf
could help.
From dhclient.conf man page:
The timeout statement determines the amount of time that must pass
between the time that the client begins
to try to determine its address and the time that it decides that it's
On 10/03/2011 08:24 AM, Dan Williams wrote:
So after talking with Thomas about this (and reviewing the patches) a
few weeks ago, I think we should turn the implementation around a bit.
I probably suggested that way originally but I now think instead we
should have NM tell the firewall directly
Would be great if somebody could review them. But there's
no hurry cause I'm away whole next week.
Jiri Popelka (5):
New 'zone' property of the NMSettingConnection.
plugins/ifcfg-rh: read/write zone name from/to ZONE key
nmcli: add zone field to 'con status'
Firewall manager
NMPolicy
---
src/settings/plugins/ifcfg-rh/reader.c | 12 +++-
src/settings/plugins/ifcfg-rh/writer.c |2 ++
2 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/src/settings/plugins/ifcfg-rh/reader.c
b/src/settings/plugins/ifcfg-rh/reader.c
index 910cca3..0a5f5e5 100644
---
libnm-util/nm-setting-connection
---
libnm-util/libnm-util.ver |1 +
libnm-util/nm-setting-connection.c | 52
libnm-util/nm-setting-connection.h |9 ++
3 files changed, 62 insertions(+), 0 deletions(-)
diff --git
---
src/nm-policy.c | 60 ++-
1 files changed, 59 insertions(+), 1 deletions(-)
diff --git a/src/nm-policy.c b/src/nm-policy.c
index 02292f7..693c4f6 100644
--- a/src/nm-policy.c
+++ b/src/nm-policy.c
@@ -47,6 +47,7 @@
#include
src/firewall-manager tracks whether firewall is on the bus or not.
In nm-device.c at stage5 (ip-config-commit) before we actually
apply the IP configuration to the interface, we send the
IP interface name and zone to firewall and asynchronously wait
for a D-Bus reply. Then after we get the reply
---
cli/src/connections.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/cli/src/connections.c b/cli/src/connections.c
index 7d4fffc..acb396e 100644
--- a/cli/src/connections.c
+++ b/cli/src/connections.c
@@ -68,9 +68,10 @@ static NmcOutputField
You can add
timeout value;
to /etc/dhcp/dhclient-interface.conf
See also
http://mail.gnome.org/archives/networkmanager-list/2011-September/msg00127.html
--
Jiri
On 10/04/2011 10:24 AM, Anders Gnistrup wrote:
Hi
I have searched the net and the only method to set the DHCP request timeout
overwritten each time NM runs
dhclient
so there's no way how to pass some options to NM started dhclient.
I'll be glad if you could educate me in this.
Thanks,
Jiri Popelka
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org
On 06/30/2011 11:11 PM, Dan Williams wrote:
On Tue, 2011-06-28 at 19:03 +0200, Thomas Woerner wrote:
Hello Dan,
we were talking some time ago about classification of network
connections according to their trust level in network zones.
Jiri Popelka and I want to work on network zone support
---
include/NetworkManager.h |3 +
src/nm-policy.c | 126 ++
2 files changed, 119 insertions(+), 10 deletions(-)
diff --git a/include/NetworkManager.h b/include/NetworkManager.h
index 17c3a11..dc403a4 100644
--- a/include/NetworkManager.h
---
src/main.c |2 +-
src/nm-policy.c | 389 ---
src/nm-policy.h | 21 +++-
3 files changed, 246 insertions(+), 166 deletions(-)
diff --git a/src/main.c b/src/main.c
index 328c253..109b352 100644
--- a/src/main.c
+++ b/src/main.c
@@
On 05/02/2011 03:13 PM, Thomas Bechtold wrote:
Hi,
i have a problem with NM 0.8.4 and dhcp:
Jan 1 00:08:07 meteo-40 daemon.info NetworkManager[760]: info
Activation (eth4) Stage 1 of 5 (Device Prepare) started...
Jan 1 00:08:07 meteo-40 daemon.info NetworkManager[760]: info
Activation
36 matches
Mail list logo
