Camaleón wrote:
> Bob Proulx wrote:
> > It may be unintuitive but ignoring client identifier is incorrect. That
> > is why patching to do so isn't accepted upstream. Ignoring client
> > identifier violates the protocol. See RFC 2131.
>
> Yes, I guess that's what man page also warns about, so wha
On Thu, 29 Sep 2011 13:39:06 -0600, Bob Proulx wrote:
> Camaleón wrote:
>> Niklas Jakobsson wrote:
>> > I found this post to the dhcp-users mailing list:
>> > https://lists.isc.org/pipermail/dhcp-users/2011-July/013440.html
>>
>> W-o-w... that's incredible.
>> So it is not working even in the ups
Camaleón wrote:
> Niklas Jakobsson wrote:
> > I found this post to the dhcp-users mailing list:
> > https://lists.isc.org/pipermail/dhcp-users/2011-July/013440.html
>
> W-o-w... that's incredible.
> So it is not working even in the upstream dhcpd? :-o
It may be unintuitive but ignoring client id
On Thu, 29 Sep 2011 10:32:02 +0200, Niklas Jakobsson wrote:
> I found this post to the dhcp-users mailing list:
> https://lists.isc.org/pipermail/dhcp-users/2011-July/013440.html
W-o-w... that's incredible.
So it is not working even in the upstream dhcpd? :-o
> It adds a new option ignore-clie
I found this post to the dhcp-users mailing list:
https://lists.isc.org/pipermail/dhcp-users/2011-July/013440.html
It adds a new option ignore-client-uids to dhcpd. I applied the patch
and recompiled my dhcp-server and it works exactly as intended.
So, my problem is solved...
/Nico
--
Niklas
On ons, 2011-09-28 at 16:23 +, Camaleón wrote:
> On Wed, 28 Sep 2011 10:04:22 +0200, Niklas Jakobsson wrote:
>
> (...)
>
> > I have tried setting the keyword duplicates to both allow and deny
> > without any success.
>
> I think it should be "deny duplicates;" in this case.
>
> > From what
On Wed, 28 Sep 2011 10:04:22 +0200, Niklas Jakobsson wrote:
(...)
> I have tried setting the keyword duplicates to both allow and deny
> without any success.
I think it should be "deny duplicates;" in this case.
> From what I can tell duplicates makes the
> dhcp-server ignore the UID, which is
Hello,
I have some problems when doing a network install with the kernel and
initrd in the netboot.tar.gz package in 20110106+squeeze3.
I have a local dhcp-server with an address pool configured. After I have
booted into the installer and selected configure with dhcp the lease
file on the server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You should be able to remove that from the boot order. In the system's
bios the boot order will list something like "cdrom, net, disk". Just
remove the net option.
Regards,
Tod Detre
- --
Pantek, Inc. - http://www.pantek.com/ - [EMAIL PROTECTED]
+1-
Hi all,
recently I did a fresh install of Debian Etch on my home-serverbox,
and now it only boots properly after a reboot.
The reason given is that the Managed PC Boot Agent or Pre-Boot
eXecution Environment errs with "PXE-E53 No Boot Filename received"
after which it hangs reporting there's no
Hello,
I am using Debian-Linux testing (i386).
Since two weeks my computer is connected to internet
by DSL (1&1, german provider) using a Fritz!Box configured
as router.
Configuration was done under Windows2000, and its works
very well under Debian-Linux until yesterday.
Yesterday I made a softw
On Thu, 2003-12-25 at 11:00, Alan Chandler wrote:
> I have been reconfiguring the networking on my SARGE based server so
> that it can act as an internet gateway for my home network. This
> requires that it uses dhcp (client) to get an ip address from my ISP for
> the internet interface (eth0)
I have been reconfiguring the networking on my SARGE based server so
that it can act as an internet gateway for my home network. This
requires that it uses dhcp (client) to get an ip address from my ISP for
the internet interface (eth0) and that it has a fixed ip address with a
dhcp server for
Andrew Schulman wrote:
> Stefan Bellon wrote:
[ifup does not bring up interface via dhcp]
> > The file /etc/network/interfaces contains the lines
> >
> > auto eth0
> > iface eth0 inet dhcp
> >
> > which looks ok to me.
> Yes, this seems fine (although I also have auto lo and
> iface lo inet l
> Since upgrading from dhcp3-client 3.0+3.0.1rc11-4 to 3.0+3.0.1rc11-5
> the dhclient stopped working correctly and my network interface isn't
> brought up anymore.
>
> If I do
>
> # dhclient eth0
>
> that results amongst other (usual) messages in
>
> receive_packet failed on eth0: Network is d
I'm running Debian GNU/Linux unstable on my Notebook which needs to get
its configuration via DHCP as it's connected to several networks (home,
work, ...).
Since upgrading from dhcp3-client 3.0+3.0.1rc11-4 to 3.0+3.0.1rc11-5
the dhclient stopped working correctly and my network interface isn't
bro
[Thu, Oct 04, 2001 at 10:15:18AM -0400] David Priban :
> > > > a cable modem, and the DHCP server requires that I send in my
> > > > hostname with my request. So far, I have tried (and failed at
> > > > using)
> the interface is configured via dhclient-script according info
> receiv
Are you sure that dhcpcd isn't working? I
just installed
dhcpcd, and at first I thought it wasn't working,
because
there was nothing about DHCP written to the console
during
boot. But I eventually discovered that it was
working fine...
it just doesn't print out its transmission and
recep
> > > Hi. I just installed Debian last night on my system,
> > > and everything works great except the network. I have
> > > a cable modem, and the DHCP server requires that I
> > > send in my hostname with my request. So far, I have
> > > tried (and failed at using):
I've got DHCP working on
On Wed, Oct 03, 2001 at 10:36:57PM -0500, Michael Heldebrant wrote:
> On Sat, 2001-09-29 at 19:56, Andrew Robertson wrote:
> > Hi. I just installed Debian last night on my system,
> > and everything works great except the network. I have
> > a cable modem, and the DHCP server requires that I
> >
On Sat, 2001-09-29 at 19:56, Andrew Robertson wrote:
> Hi. I just installed Debian last night on my system,
> and everything works great except the network. I have
> a cable modem, and the DHCP server requires that I
> send in my hostname with my request. So far, I have
> tried (and failed at us
Hi. I just installed Debian last night on my system,
and everything works great except the network. I have
a cable modem, and the DHCP server requires that I
send in my hostname with my request. So far, I have
tried (and failed at using):
1) using pump to explicitly define my hostname
2) using d
A heads-up for anyone experiencing network connectivity problems.
It seems that both the 'testing' and the 'unstable' debian trees are
missing the 'dhcpcd' utility. I spent the better part of 5 hours (I am
new to this ...) figuring out why I couldn't connect to my cable ISP.
Turns out that dhcp wa
23 matches
Mail list logo
