1) make the service that depends on networking more aware of it's
real
dependencies. That means, if named is configured to listen on some
specific interface, or some specific IP address, then the named
service
should really be waiting for that address or interface to come up,
not
just
This patch brings support for multiple domains in named configuration. All
listed
domains in the IP4 config structure are processed as follows:
- domain is added to 'search' entry in /etc/resolv.conf, as before;
- 'SetForwarders' message is sent to named for each nameserver listed in the IP4
Greetings.
I use NetworkManager 0.5.1 on a laptop (Linux, FC4) that I connect to a
wired network at home and at work.
Since a few days, connecting to the net at work does not configure the
name server, and I have to run named manually to get name resolution. At
home, everything works as expected
Matthew Saltzman wrote:
In Fedora, you start named at boot, but to get it to talk to NM, you
need to connect it to dbus. Add to /etc/sysconfig/named the line
This is OK.
Also, do not install the bind-chroot package, but do install the
caching-nameserver package.
This is OK too.
You say
On Wed, 2006-04-12 at 12:55 +0200, Filip Miletic wrote:
Matthew Saltzman wrote:
In Fedora, you start named at boot, but to get it to talk to NM, you
need to connect it to dbus. Add to /etc/sysconfig/named the line
This is OK.
Also, do not install the bind-chroot package, but do
Dan Williams wrote:
Hmm, maybe dhclient has cached the IP/MAC of the temporary DHCP server
somewhere? Try deleting everything in /var/lib/dhcp and trying
I just tried this and it does not seem to do the trick.
The eth0 interface and the routes configure fine, but if named is not up
I get
this and it does not seem to do the trick.
The eth0 interface and the routes configure fine, but if named is not up
I get an empty /etc/resolv.conf. (there's a comment along the lines of
'do not edit' from NetworkManager but I suppose that does not count).
As soon as I start named (/etc/init.d
named manually to get name resolution. At
home, everything works as expected.
I can run named by hand or enable it at startup solves the issue. But as
far as I know, NM was able to solve this before. Running 'NetworkManager
--no-daemon' did not reveal any errors.
The only message I get when
Matthew Saltzman wrote:
somewhere? Try deleting everything in /var/lib/dhcp and trying
I don't have an FC4 client, but isn't that /var/lib/dhclient? It is in
FC5.
In FC4 the directory seems to be 'dhcp' as said before. I get this from
looking at 'rpm -ql dhclient'.
Is named in fact being
On Wed, 12 Apr 2006, Neal Becker wrote:
Matthew Saltzman wrote:
In Fedora, you start named at boot, but to get it to talk to NM, you need
to connect it to dbus. Add to /etc/sysconfig/named the line
OPTIONS=-D
Also, do not install the bind-chroot package, but do install the
caching
On Wed, 2006-04-12 at 11:56 -0400, Matthew Saltzman wrote:
On Wed, 12 Apr 2006, Neal Becker wrote:
Matthew Saltzman wrote:
In Fedora, you start named at boot, but to get it to talk to NM, you need
to connect it to dbus. Add to /etc/sysconfig/named the line
OPTIONS=-D
Also, do
On Wed, 12 Apr 2006, Dan Williams wrote:
On Wed, 2006-04-12 at 11:56 -0400, Matthew Saltzman wrote:
On Wed, 12 Apr 2006, Neal Becker wrote:
Matthew Saltzman wrote:
In Fedora, you start named at boot, but to get it to talk to NM, you need
to connect it to dbus. Add to /etc/sysconfig/named
On Tue, 2005-12-13 at 16:37 -0500, Robert Love wrote:
One option is to not trigger the assertion when config==NULL but exit
silently. In other words, treat it as a known case.
I backed out the change and went ahead and checked this in. I made two
changes
(a) Return TRUE not FALSE if
On Sun, 2005-10-23 at 17:47 +0200, Tor Krill wrote:
I'm working on a port of NM to my distribution of choice, Archlinux.
Great!
Working on this i run without named and if i understand correct that is
ok? With fallback on glibc resolver.
Correct. If named does not support dbus, NM will fall
Hi all,
I'm working on a port of NM to my distribution of choice, Archlinux.
Working on this i run without named and if i understand correct that is
ok? With fallback on glibc resolver.
Doing this i have encountered two problems. When writing resolv.conf
only first nameserver gets written, once
On Thu, 2005-10-20 at 18:39 +0200, Tomislav Vujec wrote:
On Tue, 2005-10-18 at 14:41 -0400, Dan Williams wrote:
No, NM no longer spawns named directly at any point. If named is
already running (we check whether the DBUS service that named provides
is active or not) then NM will use
On Fri, 2005-10-21 at 01:58 +0200, Tomislav Vujec wrote:
On Thu, 2005-10-20 at 14:38 -0400, Peter Jones wrote:
Both of them should be started by init during boot. I think starting it
through this mechanism is just incorrect.
Can you elaborate on this? From my point of view, named can
On Tue, 2005-10-18 at 14:41 -0400, Dan Williams wrote:
No, NM no longer spawns named directly at any point. If named is
already running (we check whether the DBUS service that named provides
is active or not) then NM will use it. If the service is not running,
NM falls back to writing /etc
On Thu, 2005-10-20 at 18:39 +0200, Tomislav Vujec wrote:
On Tue, 2005-10-18 at 14:41 -0400, Dan Williams wrote:
No, NM no longer spawns named directly at any point. If named is
already running (we check whether the DBUS service that named provides
is active or not) then NM will use
On Thu, 2005-10-20 at 14:38 -0400, Peter Jones wrote:
Both of them should be started by init during boot. I think starting it
through this mechanism is just incorrect.
Can you elaborate on this? From my point of view, named can either be
controlled through dbus, or it can be a standalone DNS
On Tue, 2005-10-18 at 09:40 -0500, Brian Millett wrote:
Hello,
I'm running NetworkManager on a fedora rawhide laptop. In the not too
distant past, there was a named running under control of NetworkManager
with the /etc/resolv.conf pointing to 127.0.0.1. I see that in the 0.5
release
On Tue, 2005-10-18 at 11:44 -0500, Brian Millett wrote:
On Tue, 2005-10-18 at 12:11 -0400, Dan Williams wrote:
So, I gather that if named is started, then NetworkManager will use it,
else it reverts to creating its own?
No, NM no longer spawns named directly at any point. If named is
already
On Thu, 2005-09-29 at 17:11 +0200, [EMAIL PROTECTED] wrote:
Is there a url for the latest version of the dbus patch?
I found it with a Google search for Fedora CVS. You can get the seed
tarball, then 'cvs update -dP' in the directory it makes. You'll find
the patches in there.
I found that
Hi,
is there a url for the latest version of the dbus patch?
is it red hats plan to keep dns and dhcp in the com.redhad dbus
namespace while i.e. NetworkManager is in org.freedesktop?
to me it looks like having all in the same domain, org.freedesktop
would be a better choice.
j
Hi,
I've just committed named dbus support to NetworkManager. This does
away with launching named as a child process, and uses an existing named
process (that has been dbus-enabled). All communication is via dbus.
Pros:
1) Implementation is much cleaner, easier to follow.
2) Will fall back
25 matches
Mail list logo
