On 11/28/2014 06:55 AM, Bjørn Mork wrote:
Lubomir Rintel lrin...@redhat.com writes:
On Thu, 2014-11-27 at 17:15 -0500, Gene Czarcinski wrote:
On Fedora 21 with NetworkManager-0.9.10.0-13.git20140704.fc21.x86_6 and
on Fedora 20 with NetworkManager-0.9.9.0-46.git20131003.fc20.x86_64 I am
seein
On Fedora 21 with NetworkManager-0.9.10.0-13.git20140704.fc21.x86_6 and
on Fedora 20 with NetworkManager-0.9.9.0-46.git20131003.fc20.x86_64 I am
seein some strange network devices:
18: rose7: NOARP mtu 249 qdisc noop state DOWN group default
link/rose 00:00:00:00:00 brd 00:00:00:00:00
19:
On 10/19/2014 09:53 AM, Lubomir Rintel wrote:
On Sat, 2014-10-18 at 16:00 -0400, Gene Czarcinski wrote:
On 10/16/2014 07:08 AM, Lubomir Rintel wrote:
Hi,
currently it is impossible to get useful network configuration for LXC
containers on boot. (At least if they're managed via libvirt; I have
On 10/16/2014 07:08 AM, Lubomir Rintel wrote:
Hi,
currently it is impossible to get useful network configuration for LXC
containers on boot. (At least if they're managed via libvirt; I have no
idea if anything is different with native LXC tooling). They're supposed
to obtain their configuration
OK, I give up ... what is the magic dance I need to do to restore a
forgotten NIC?
I was playing with gnome's network editor and on the reset page for a
device, I hit the Forget button. Device was removed but now I would
like to restore it. How do I do that (other than to do another
When I reported that IPv6 was not working on F20 alpha:
https://bugzilla.redhat.com/show_bug.cgi?id=1013583
I was interesting in getting the fix. Since an errata was not instantly
available, I extracted the extremely simple patch from the git. Next, I
got the src.rpm ... well, although my
On 08/07/2013 04:17 PM, Dan Williams wrote:
On Wed, 2013-08-07 at 10:11 -0400, Gene Czarcinski wrote:
I recently moved into a new development and pretty much each and every
home in this development has a WIFI network. While most of these
network are secure a few of them are not but require
I recently moved into a new development and pretty much each and every
home in this development has a WIFI network. While most of these
network are secure a few of them are not but require some kind of
handshake to establish guest access. These guest access WIFI
networks are a pain because
I recently moved into a new development and pretty much each and every
home in this development has a WIFI network. While most of these
network are secure a few of them are not but require some kind of
handshake to establish guest access. These guest access WIFI
networks are a pain because
I recently moved into a new development and pretty much each and every
home in this development has a WIFI network. While most of these
network are secure a few of them are not but require some kind of
handshake to establish guest access. These guest access WIFI
networks are a pain because
On 02/15/2013 03:28 PM, Dan Williams wrote:
On Fri, 2013-02-15 at 14:32 -0500, Gene Czarcinski wrote:
Although there is a v1.0.8 tag in the NM git, there is still hope since
there has not been a Release Announcement yet.
Hmm, I don't see a 1.0.8 or a 1.0.2. The latest release was 0.9.6.4
get_duid() got a default-duid from the lease file, from
one of the system files, or from the machine-id but did
not save it back to the lease file so that dhclient
could use it.
Signed-off-by: Gene Czarcinski g...@czarc.net
---
src/dhcp-manager/nm-dhcp-dhclient.c | 24 +---
1
machine_id_parse() and uses it
in place of uuid_parse(). The machine-id uuid is not compatable
with standard uuid.
Gene Czarcinski (2):
save duid to lease file
add special machine-id parse function
src/dhcp-manager/nm-dhcp-client.c | 30 +-
src/dhcp-manager/nm-dhcp
The original used uuid_parse() but that function did not
work properly since the format of the machine-id is
not compatable with a real uuid. This patch adds a new
machine_id_parse() routine to correctly convert the
character string of hex digits to a 16 byte binary string.
Signed-off-by: Gene
On 02/13/2013 03:01 AM, Gene Czarcinski wrote:
These two patches correct the code for default-duid support.
The first patch changes the code so that a default-duid is
gotten from the lease file, from one of the system files such as
/etc/dhclient6.leases, or a generate duid-UUID based
On 02/13/2013 10:43 AM, Dan Williams wrote:
On Wed, 2013-02-13 at 03:01 -0500, Gene Czarcinski wrote:
get_duid() got a default-duid from the lease file, from
one of the system files, or from the machine-id but did
not save it back to the lease file so that dhclient
could use it.
Signed-off
On 02/13/2013 11:36 AM, Dan Williams wrote:
On Wed, 2013-02-13 at 11:16 -0500, Gene Czarcinski wrote:
On 02/13/2013 10:43 AM, Dan Williams wrote:
On Wed, 2013-02-13 at 03:01 -0500, Gene Czarcinski wrote:
get_duid() got a default-duid from the lease file, from
one of the system files, or from
On 02/12/2013 10:13 AM, Gene Czarcinski wrote:
On 02/12/2013 09:23 AM, Gene Czarcinski wrote:
On 02/11/2013 04:51 PM, Dan Williams wrote:
On Mon, 2013-02-11 at 16:42 -0500, Gene Czarcinski wrote:
On 02/11/2013 04:06 PM, Dan Williams wrote:
Fedora 17 and 18, until 0.9.7.997, left the DUID
Forget my other message because I want to start fresh.
I enable DEBUG logging which gets me more correct info as to what is
going on. The following are the relevant log message:
Feb 12 11:37:08 hawk NetworkManager[5693]:
On 02/12/2013 10:53 AM, Gene Czarcinski wrote:
On 02/12/2013 10:13 AM, Gene Czarcinski wrote:
On 02/12/2013 09:23 AM, Gene Czarcinski wrote:
On 02/11/2013 04:51 PM, Dan Williams wrote:
On Mon, 2013-02-11 at 16:42 -0500, Gene Czarcinski wrote:
On 02/11/2013 04:06 PM, Dan Williams wrote
.
While I can live with manually specifying the default-duid, I would
still prefer an option where the command-line -D LL was used.
Well, time to start testing this on real systems so I can give feedback.
Gene
- Original Message -
From: Gene Czarcinski g...@czarc.net
To: networkmanager
See my reply to dcbw on the dnsmasq-discuss mailing list.
Gene
On 02/08/2013 12:20 PM, Pavel Simerda wrote:
- Original Message -
From: Gene Czarcinski g...@czarc.net
For some time I have been having a problem attempting to have a
dnsmasq
server provide a system with a fixed IPv6
For some time I have been having a problem attempting to have a dnsmasq
server provide a system with a fixed IPv6 address. Setting an IPv4
address and identifying the system with its NIC's MAC address. But,
with DHCPv6 there is no relationship defined in the standard for DHCPv6
to use the
On 01/31/2013 04:38 PM, Dan Williams wrote:
And by virtual networks you mean bridge interfaces, as I see from the
bug. Bridging support will be turned off-by-default in the 0.9.8
release until we can become better at cooperating with existing
configurations. It will be enabled by editing the
I needed some functionality (dynamic dns update) not available in the
NetworkManager package available in Fedora 18 so I created my own
version based on git20121130. This worked nicely providing the
functionality and did not appear to have any bad side effects.
Then the NetworkManager
On 01/31/2013 10:59 AM, Gene Czarcinski wrote:
I needed some functionality (dynamic dns update) not available in the
NetworkManager package available in Fedora 18 so I created my own
version based on git20121130. This worked nicely providing the
functionality and did not appear to have any
On 11/28/2012 02:57 PM, Pavel Simerda wrote:
From: Gene Czarcinski g...@czarc.net
I have a clone of the NetworkManager git repository and, this
morning, I
ran git pull (from master) to make sure it was up to date. I also
have a couple of other branches checked out: pavlix/ipv6 and
pavlix/dhcp
I am more than a little confused.
There was an announcement on this list that 0.9.6.4 is the latest stable
version for NM and the applet and these updates are available for Fedora 17.
Fedora 18 has entered beta and includes 0.9.7.0 (git20121004) which can
be rebuilt for Fedora 17. I also
On 11/28/2012 07:47 AM, Gene Czarcinski wrote:
I am more than a little confused.
There was an announcement on this list that 0.9.6.4 is the latest
stable version for NM and the applet and these updates are available
for Fedora 17.
Fedora 18 has entered beta and includes 0.9.7.0 (git20121004
I have a clone of the NetworkManager git repository and, this morning, I
ran git pull (from master) to make sure it was up to date. I also
have a couple of other branches checked out: pavlix/ipv6 and pavlix/dhcp.
I wanted to make a distribution tarball for pavlix/ipv6 so I could build
an rpm
, it will be back to libvirt for me.
Gene
- Original Message -
From: Gene Czarcinski g...@czarc.net
To: networkmanager-list@gnome.org
Sent: Sunday, October 7, 2012 6:30:28 PM
Subject: prefix=48 static route
Should I be able to specify an IPv6 prefix=48 static route and have
it work?
I
Should I be able to specify an IPv6 prefix=48 static route and have it work?
I tried but it was with a lot of other testing and things may have
just gotten a bit screwed up.
So many things about IPv6 seem to want only prefix=64.
Gene
___
On 10/01/2012 12:47 PM, Jiri Popelka wrote:
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
On 10/01/2012 11:44 AM, Jiri Popelka wrote:
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.
That is not clear. The dhcp-options man-page could
: Gene Czarcinski g...@czarc.net
To: networkmanager-list@gnome.org
Sent: Friday, September 28, 2012 6:40:32 PM
Subject: For review: version 3 of IPv6 dynamic dns support
Here is the next round of my patch to add support for IPv6 dynamic
dns
to NetworkManager.
As before, this depends on using dhclient
On 09/27/2012 04:22 PM, Gene Czarcinski wrote:
OK, anyone have any experience sending commands, requests etc. via
dhclient?
I have my patch fixed up so that it works from a conf file rather than
-F on the commandline since that is a Red Hat ism.
I am asking for some stuff and I get little
On 09/28/2012 08:15 AM, Pavel Simerda wrote:
You*may* be right. But, unfortunately, I have been playing with DHCPv6
implementations and there wasn't one that I would actually like. Except
ISC DHCP which works for me but needs improvement.
Give dnsmasq a look. It seems that not only
Here is the next round of my patch to add support for IPv6 dynamic dns
to NetworkManager.
As before, this depends on using dhclient on the client side. As
before, IPv4 support remains the same.
While this does work if method dhcp is selected, this is purely by
chance. The real usage is
On 09/26/2012 04:51 PM, Pavel Simerda wrote:
The proper keyfile configuration is for example:
[connection]
id=Ethernet
uuid=d880f3bb-8c51-4ca4-aef7-1954e022820f
type=802-3-ethernet
[802-3-ethernet]
mac-address=52:54:00:eb:e9:fb
[ipv4]
method=auto
[ipv6]
nmmethod=auto
I believe you have a type
On 09/27/2012 04:43 AM, Jiri Popelka wrote:
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.
While it will be nice
OK, anyone have any experience sending commands, requests etc. via dhclient?
I have my patch fixed up so that it works from a conf file rather than
-F on the commandline since that is a Red Hat ism.
I am asking for some stuff and I get little back from dhcpd6 [that is
using radvd, named,
On 09/25/2012 02:49 PM, Dan Williams wrote:
On Tue, 2012-09-25 at 13:43 +0200, Jiri Popelka wrote:
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
On 09/25/2012 07:55 PM, Pavel Simerda wrote:
I'll divide my reaction into four parts and post it also to NM mailing list so
that anyone can
benefit.
1) DHCPv6 currently works according to IETF standards and has been tested with
NetworkManager
commit 70f64fbc4277c636c0a373d6e6eddf0574d53827
On 09/26/2012 02:38 PM, Dan Williams wrote:
There's some example keyfiles here:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/settings/plugins/keyfile/tests/keyfiles
manual IPv6 is for example:
On 09/26/2012 02:04 PM, Gene Czarcinski wrote:
BTW, my testing that worked was using named/dhcpd/dhcp6 on the
server. I now need to test dnsmasq to make sure that it works too. It
is possible that for a small network (which is the primary use of
dnsmasq), you might not need radvd because
On 09/23/2012 08:56 AM, Gene Czarcinski wrote:
I have been doing some work trying to improve IPv6 dhcp support in
NetworkManager. This has involved a lot of (virtual) testing. One
thing I began to notice is a lot of the following message appearing in
syslog:
[nm-system.c:1121
Note: this is for review and not submit. After I respond to any
comments, make appropriate additions and/or subtractions, and gone over
the code myself just one more time, I will submit the patch and it
should be RSN (real soon now).
Note: NO changes were made to the IPv4 dhcp support.
OK,
On 09/24/2012 12:30 PM, Dan Williams wrote:
On Mon, 2012-09-24 at 08:05 -0400, Gene Czarcinski wrote:
On 09/23/2012 08:56 AM, Gene Czarcinski wrote:
I have been doing some work trying to improve IPv6 dhcp support in
NetworkManager. This has involved a lot of (virtual) testing. One
thing I
On 09/24/2012 12:25 PM, Dan Williams wrote:
On Sat, 2012-09-22 at 15:25 -0400, Gene Czarcinski wrote:
I am in the process of developing some patches to NetworkManager which
implementingdhcp dynamic dns updating for dhcp6. The patches involve
some small updating to the code in libnm-util
On 09/24/2012 01:05 PM, Gene Czarcinski wrote:
On 09/24/2012 12:30 PM, Dan Williams wrote:
On Mon, 2012-09-24 at 08:05 -0400, Gene Czarcinski wrote:
On 09/23/2012 08:56 AM, Gene Czarcinski wrote:
I have been doing some work trying to improve IPv6 dhcp support in
NetworkManager. This has
On 09/24/2012 02:49 PM, Gene Czarcinski wrote:
On 09/24/2012 01:05 PM, Gene Czarcinski wrote:
On 09/24/2012 12:30 PM, Dan Williams wrote:
On Mon, 2012-09-24 at 08:05 -0400, Gene Czarcinski wrote:
On 09/23/2012 08:56 AM, Gene Czarcinski wrote:
I have been doing some work trying to improve
OK, I have done more testing.
1. With 0.9.7.0, the failing default route message is gone.
2. If you have radvd configured and running on the IPv6 network, the
using automatic for IPv6 works and you get a default route which works.
3. If you configure IPv6 to use dhcp, then there is no
I am running Fedora 17 but would like to update to
NetworkManager-0.9.7.0. There are src and binary rpms for F18 but it is
not practical to use the F18 binaries on F17 so I need to rebuild them
on F17 ... no problem ... for NetworkManager itself. But 0.9.7.0 splits
out the
I have been doing some work trying to improve IPv6 dhcp support in
NetworkManager. This has involved a lot of (virtual) testing. One
thing I began to notice is a lot of the following message appearing in
syslog:
[nm-system.c:1121] nm_system_replace_default_ip6_route(): (p32p1):
failed to
I am in the process of developing some patches to NetworkManager which
implementingdhcp dynamic dns updating for dhcp6. The patches involve
some small updating to the code in libnm-util. There is a reference
manual for libnm-util. What is the process/procedure for doing the
updates to that?
On 09/18/2012 04:17 PM, Dan Williams wrote:
On Tue, 2012-09-18 at 14:59 -0400, Gene Czarcinski wrote:
On 09/18/2012 02:22 PM, Dan Williams wrote:
On Tue, 2012-09-18 at 13:08 -0500, Dan Williams wrote:
On Tue, 2012-09-18 at 13:19 -0400, Gene Czarcinski wrote:
On 09/17/2012 02:36 PM, Gene
On 09/17/2012 02:36 PM, Gene Czarcinski wrote:
On 09/17/2012 02:24 PM, Gene Czarcinski wrote:
On 09/17/2012 12:05 PM, Jiri Popelka wrote:
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
On 09/18/2012 02:22 PM, Dan Williams wrote:
On Tue, 2012-09-18 at 13:08 -0500, Dan Williams wrote:
On Tue, 2012-09-18 at 13:19 -0400, Gene Czarcinski wrote:
On 09/17/2012 02:36 PM, Gene Czarcinski wrote:
On 09/17/2012 02:24 PM, Gene Czarcinski wrote:
On 09/17/2012 12:05 PM, Jiri Popelka
On 09/17/2012 12:05 PM, Jiri Popelka wrote:
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
On 09/17/2012 02:24 PM, Gene Czarcinski wrote:
On 09/17/2012 12:05 PM, Jiri Popelka wrote:
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
On 09/15/2012 10:13 AM, Gene Czarcinski wrote:
I am trying to set up an IPv6 virtual network using dnsmasq to support
the dhcp and dns. Recently (the last couple of releases) dnsmasq has
supported dhcp with updating dns.
I have gotten it so that the IPv6 addresses are assigned correctly
I am trying to set up an IPv6 virtual network using dnsmasq to support
the dhcp and dns. Recently (the last couple of releases) dnsmasq has
supported dhcp with updating dns.
I have gotten it so that the IPv6 addresses are assigned correctly but I
have been driving myself nuts trying to
Just curious but ... I noticed that the dnsmasq for caching that
NetworkManager starts has the command parameter --keep-in-foreground
specified.
Why?
According to the dnsmasq doc: --keep-in-foreground or -k does:
Do not go into the background at startup but otherwise run as
normal. This is
I am doing some testing of NM using dnsmasq for a caching nameserver:
From another message:
3. Will use of dnsmasq be optional and configurable?
It already is, you can enable or disable it via dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf; and since recently, you can
tweak the
OK, I have been doing some testing with NM's new use of dnsmasq. But, I
am running Fedora 17 and I needed the --conf-dir= capability Just
getting the 0.9.7.0 package from rawhide and rebuilding had far too many
other packages required to do that. However, it was pretty easy to look
at the
On 09/01/2012 03:24 PM, Gene Czarcinski wrote:
OK, I have been doing some testing with NM's new use of dnsmasq. But,
I am running Fedora 17 and I needed the --conf-dir= capability Just
getting the 0.9.7.0 package from rawhide and rebuilding had far too
many other packages required to do
I am doing some testing of NM using dnsmasq for a caching nameserver:
From another message:
3. Will use of dnsmasq be optional and configurable?
It already is, you can enable or disable it via dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf; and since recently, you can
tweak the
On 08/27/2012 12:19 PM, Mathieu Trudel-Lapierre wrote:
On Sat, Aug 25, 2012 at 5:05 PM, Gene Czarcinski g...@czarc.net wrote:
[...]
1. Is it already in use? I am running current Fedora 17 and a ps ax
shows no extra dnsmasq ... just all the ones for my virtual networks.
It's not in use
I was having some problems with libvirt's usage of dnsmasq (the command
line parameters libvirtd was using). Too many queries were being
forwarded. I have submitted a patch to libvirt for their part of the
problem but dnsmasq is still leaking some queries that I believe should
not be
DEFROUTE=yes|no support has been added to initscripts and is in rawhide (and I
assume will be in F12) ...
https://bugzilla.redhat.com/show_bug.cgi?id=528822
When will the DEFROUTE support be added to NetworkManager?
https://bugzilla.redhat.com/show_bug.cgi?id=528281
The patch is in the BZ
I notice that if I stop the NetworkManager service:
/etc/init.d/NetworkManager stop
that the interfaces started by NetworkManager are not always stopped.
Note: this is a F12 qemu-kvm guest with multiple (two) NICs defined.
Bug or feature??
Gene
I am not adverse to doing some coding to get functionality I want. The BZ
report https://bugzilla.redhat.com/show_bug.cgi?id=510253 asks for an
enhancement to NetworkManager to support specifying a DHCP hostname using the
NetworkManager system-settings editor. Unfortunately for me, the editor
On Monday 02 November 2009 16:18:57 Dan Williams wrote:
On Mon, 2009-11-02 at 17:08 -0400, Gene Czarcinski wrote:
I am not adverse to doing some coding to get functionality I want. The
BZ report https://bugzilla.redhat.com/show_bug.cgi?id=510253 asks for an
enhancement to NetworkManager
On Monday 02 November 2009 16:21:17 Dan Williams wrote:
On Mon, 2009-11-02 at 16:54 -0400, Gene Czarcinski wrote:
I notice that if I stop the NetworkManager service:
/etc/init.d/NetworkManager stop
that the interfaces started by NetworkManager are not always stopped.
Note
On Sunday 18 October 2009 11:59:59 Gene Czarcinski wrote:
Unfortunately, in order to set these variables for the hostname, you
currently need to use you favorite text editor such as vi. In the case
of a system connection (a connection available to all users), you can use
system-config
On Tuesday 13 October 2009 17:05:56 Dan Williams wrote:
On Sun, 2009-10-11 at 22:44 +0200, Robert Vogelgesang wrote:
On Sun, Oct 11, 2009 at 03:12:05PM -0400, Gene Czarcinski wrote:
See the attached patch in another email. My choice of parameter/option
is NM_NEVER_DEFAULT= for devices
On Monday 12 October 2009 12:13:20 Gene Czarcinski wrote:
On Sunday 11 October 2009 20:30:58 Gene Czarcinski wrote:
2. Since this seems to work fine on F12, I thought I would give a shot at
F11. The patch applies with no changes on the latest NetworkManager
updatre (git20090708).
3
On Sunday 11 October 2009 20:30:58 Gene Czarcinski wrote:
2. Since this seems to work fine on F12, I thought I would give a shot at
F11. The patch applies with no changes on the latest NetworkManager
updatre (git20090708).
3. On F11 (as compared to F12), the update does nothing
On Saturday 10 October 2009 17:56:36 Gene Czarcinski wrote:
On Saturday 10 October 2009 17:32:42 Gene Czarcinski wrote:
OK, this is a followup to a lot of my previous email about NM handling
the default route when a system has multiple NICs.
I have closed out my BZ report for Fedora 11
On Sunday 11 October 2009 14:44:25 Robert Vogelgesang wrote:
Hello,
On Sat, Oct 10, 2009 at 05:56:36PM -0400, Gene Czarcinski wrote:
On Saturday 10 October 2009 17:32:42 Gene Czarcinski wrote:
OK, this is a followup to a lot of my previous email about NM handling
the default route when
On Sunday 11 October 2009 16:44:56 Robert Vogelgesang wrote:
On Sun, Oct 11, 2009 at 03:12:05PM -0400, Gene Czarcinski wrote:
See the attached patch in another email. My choice of parameter/option
is NM_NEVER_DEFAULT= for devices/NICs/connections that should never be
the default route
On Sunday 11 October 2009 14:44:06 Gene Czarcinski wrote:
On Saturday 10 October 2009 17:56:36 Gene Czarcinski wrote:
On Saturday 10 October 2009 17:32:42 Gene Czarcinski wrote:
OK, this is a followup to a lot of my previous email about NM handling
the default route when a system has
OK, this is a followup to a lot of my previous email about NM handling the
default route when a system has multiple NICs.
I have closed out my BZ report for Fedora 11 as WONTFIX --
https://bugzilla.redhat.com/show_bug.cgi?id=523875 -- and have opened a new
report against rawhide --
On Saturday 10 October 2009 17:32:42 Gene Czarcinski wrote:
OK, this is a followup to a lot of my previous email about NM handling the
default route when a system has multiple NICs.
I have closed out my BZ report for Fedora 11 as WONTFIX --
https://bugzilla.redhat.com/show_bug.cgi?id=523875
On Thursday 08 October 2009 12:48:57 Gene Czarcinski wrote:
1. On a qemu-kvm F12 guest, I tried manually setting GATEWAYDEV=eth1 and
this works! Not only is the default route correct but the connection
only box is now checked. At the very least, this gives me a work-around
until things
On Wednesday 07 October 2009 12:52:58 Dan Williams wrote:
On Tue, 2009-10-06 at 11:19 -0400, Gene Czarcinski wrote:
On Tuesday 06 October 2009 10:45:50 Gene Czarcinski wrote:
On Tuesday 06 October 2009 10:03:45 Gene Czarcinski wrote:
On Monday 05 October 2009 17:43:42 Dan Williams wrote
On Monday 05 October 2009 15:01:59 Dan Williams wrote:
On Mon, 2009-10-05 at 14:37 -0400, Gene Czarcinski wrote:
On Sunday 04 October 2009 01:56:25 Martyn J. Pearce wrote:
Apogolies if re-asked, I have searched the mailing-list archive to no
avail.
I am running a new ubuntu install
On Monday 05 October 2009 17:43:42 Dan Williams wrote:
On Mon, 2009-10-05 at 16:52 -0400, Gene Czarcinski wrote:
On Monday 05 October 2009 16:33:21 Gene Czarcinski wrote:
I have not worked with koji before but I can give 134947 a try too.
Downloaded and installed:
Download
On Tuesday 06 October 2009 10:03:45 Gene Czarcinski wrote:
On Monday 05 October 2009 17:43:42 Dan Williams wrote:
On Mon, 2009-10-05 at 16:52 -0400, Gene Czarcinski wrote:
On Monday 05 October 2009 16:33:21 Gene Czarcinski wrote:
I have not worked with koji before but I can give 134947
On Tuesday 06 October 2009 10:45:50 Gene Czarcinski wrote:
On Tuesday 06 October 2009 10:03:45 Gene Czarcinski wrote:
On Monday 05 October 2009 17:43:42 Dan Williams wrote:
On Mon, 2009-10-05 at 16:52 -0400, Gene Czarcinski wrote:
On Monday 05 October 2009 16:33:21 Gene Czarcinski wrote
On Sunday 04 October 2009 01:56:25 Martyn J. Pearce wrote:
Apogolies if re-asked, I have searched the mailing-list archive to no
avail.
I am running a new ubuntu install on a netbook (Eeepc surf), with wired
wireless networking available, both domestic manually-configured networks
(no
On Monday 05 October 2009 15:33:38 Dan Williams wrote:
On Mon, 2009-10-05 at 15:03 -0400, Gene Czarcinski wrote:
On Monday 05 October 2009 13:21:46 Dan Williams wrote:
That checkbox ensures that that connection (and thus any device that
has been activated using that connection
On Thursday 24 September 2009 11:24:42 Jeff Carr wrote:
3. System boots up in single user mode ... disable autostart of network
and NetworkManager. Looking at /proc/sys/net/ipv4/conf/, I now have
eth1 instead of eth0 although there is only one NIC and it is the
same type, etc. [BTW, what
On Wednesday 23 September 2009 01:36:56 Dan Williams wrote:
On Fri, 2009-09-11 at 11:42 -0400, Gene Czarcinski wrote:
On Thursday 10 September 2009 16:59:29 Dan Williams wrote:
As far as setting only use this connection for resources on its
network, I did have this work at one time
On Thursday 10 September 2009 16:59:29 Dan Williams wrote:
As far as setting only use this connection for resources on its
network, I did have this work at one time but now seems to be
consistently failing to set ... I can edit the device connection, check
the box, and then save/apply this
On Thursday 10 September 2009 16:59:29 Dan Williams wrote:
As far as setting only use this connection for resources on its
network, I did have this work at one time but now seems to be
consistently failing to set ... I can edit the device connection, check
the box, and then save/apply this
On Thursday 10 September 2009 16:59:29 Dan Williams wrote:
As far as setting only use this connection for resources on its
network, I did have this work at one time but now seems to be
consistently failing to set ... I can edit the device connection, check
the box, and then save/apply this
On Wednesday 26 August 2009 13:03:36 Dan Williams wrote:
On Wed, 2009-08-26 at 11:59 -0500, Dan Williams wrote:
On Mon, 2009-08-24 at 13:08 -0400, Gene Czarcinski wrote:
I like a lot about how NetworkManager works. I especially like the way
it handles wireless connects.
However
I have tried to simplify things but may still be unclear ... sorry. If you
would prefer, I can put all of this info in a bugzilla report or continue here
on this mailing list.
On Wednesday 26 August 2009 12:59:44 Dan Williams wrote:
On Mon, 2009-08-24 at 13:08 -0400, Gene Czarcinski wrote
/2009 02:12 PM, Gene Czarcinski wrote:
I have a problem with default route handling by NetworkManager. I have
searched this mailing list as well as bugzilla and, while there are
claims that the problem is fixed, I still have problems on Fedora 11
with current maintenance as of today
1 - 100 of 112 matches
Mail list logo
