Dear John.
AFAIK, that is the only to do it. Unless your willing to switch to MSDHCP
Maybe I file a bug report on that.
(win$). Just currious, why do you need to have 2 different ips with from a
different subnet assigned to one client?.
As mentioned before, one is a private LAN and the
I am not yet sure if we are talking about the same problem, so here is
my current configuration. Unless I add an host definition WITH
fixed-address statement to the 10.2.0.0 subnet, too LaptopWLAN won't
get an IP address within this network range.
JohnStanley Writes:
Marcus, I do not think what
Dear John,
Marcus, I do not think what your trying to do is going to work. Why?
failover peer intra-net . You will need a dhcp.master configuration file
on both servers. You running two dhcp servers? Debug with only one server.
Of course, the failover is set up and working correctly. Please
single server and let that be it. On every change you make back it up
before
a change to it. Get one laptop and don't use any WiFi Security on itand
take
out the keys defined for it in in the dhcp file. You should not need a
host
declaration for the laptop if your wantting to get an assigned
JohnStanley Writes:
From the dhcp.conf.5 manual. This seems like it would skin the cat for your
needs Specify this in each Scope and you should be set. It will allow you to
have the two different addresses from two different SNs. That is as Per the
the Man Pages (lots o digging). Has to also be in
From the dhcp.conf.5 manual. This seems like it would skin the cat for your
needs Specify this in each Scope and you should be set. It will allow you to
have the two different addresses from two different SNs. That is as Per the
As I have already mentioned in my initial post, that's what I
From the dhcp.conf.5 manual. This seems like it would skin the cat for
your
needs Specify this in each Scope and you should be set. It will allow you
to
have the two different addresses from two different SNs. That is as Per
the
As I have already mentioned in my initial post, that's what I
Dear John,
Subnet A (192.168.2.x) - DHCP Server with 2 NICs - Subnet B (10.1.0.0)
Clients on Subnet A should get a static IP from the host declaration.
Clients on Subnet B should obtain dynamic IP addresses from a range.
The two subnets are not physically connected but a CLIENT should be
Marcus Wrote:
I also wonder if it's really necessary to run two instances of DHCP
with separate config files as dhcpd3 is able to detect the Subnets on
which it may deploy leases, depending on the NIC configuration.
JohnStanley Writes.
The two commands I posted for you to set it up that way can
Dear John.
The two commands I posted for you to set it up that way can be done in a
Single File Configuration. The last config file I posted for you was for two
NICS on two different Subnets.
I am not yet sure if we are talking about the same problem, so here is
my current configuration.
The two subnets are not physically connected but a Client should be
able to connect to Subnet A or to Subnet B as well.
JohnStanley Writes:
This is what is confusing. If there *NOT* Physically Connected you will
never CONNECT to them. Hope you can calculate SNs ans SNMs. You can add as
many
Hi,
On Fri, Oct 17, 2008 at 08:32, John [EMAIL PROTECTED] wrote:
# Here is Subnet number 2.
subnet 192.168.0.16 netmask 255.255.255.224 { # Subnet for 29 computers
Isn't this wrong? If the netmask is .224, it should be either
192.168.0.0-31 or 192.168.0.32-63. 192.168.0.16 does not make sense
Hi,
On Fri, Oct 17, 2008 at 12:37, John [EMAIL PROTECTED] wrote:
On subnet 192.168.0.16 with a mask of 255.255.255.224 will give enuff ips
for 29 clients. One for the broadcast addy.
I think you are mistaken here, with netmask 255.255.255.224 you can
have network 192.168.0.0 (from 0 to 31) and
John wrote:
# Here is Subnet number 2. subnet 192.168.0.16 netmask
255.255.255.224 { # Subnet for 29 computers
Isn't this wrong? If the netmask is .224, it should be either
192.168.0.0-31 or 192.168.0.32-63. 192.168.0.16 does not make sense
here.
On subnet 192.168.0.16 with a mask of
# Here is Subnet number 2.
subnet 192.168.0.16 netmask 255.255.255.224 { # Subnet for 29 computers
Isn't this wrong? If the netmask is .224, it should be either
192.168.0.0-31 or 192.168.0.32-63. 192.168.0.16 does not make sense
here.
Filipe
JohnStanley Writes:
On subnet 192.168.0.16 with a
Isn't this wrong? If the netmask is .224, it should be either
192.168.0.0-31 or 192.168.0.32-63. 192.168.0.16 does not make sense
here.
JohnStanley Writes: Follow Up to Previous Mail!!
Filipe,
To early in the day for all this math. Your right saying x.31 - x.63 for
that particular SN, with
Felipe,
JohnStanley Writes.
Whoops, you Hit Send A little to Soon. Only if you waited.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Hi,
On Fri, Oct 17, 2008 at 13:18, John [EMAIL PROTECTED] wrote:
To early in the day for all this math.
It really is! :-)
Your right saying x.31 - x.63 for
that particular SN, with x.63 being the broadcast addy and x.31 the network
addy.
Actually, x.32 to x.63, with x.32 being the network
Yeah, but you cannot really subnet that way:
JohnStanley Writes:
So let me understand that your saying that if I am Allocated and Own the IP
blocks 64.x.x.33 - 64.x.x.35 that I can not Subnet them Out in any way? I
have always done that between for inbetween LAN to WAN Back to LAN or VPN.
Filipe Brandenburger wrote:
My personal opinion, if you're using RFC1918 addresses for internal
networks, you should only use 255.255.255.0 netmasks everywhere, even
though it's a network for one machine only. Dealing with netmasks is a
PITA, and should be avoided unless there's a real reason to
My personal opinion, if you're using RFC1918 addresses for internal
networks, you should only use 255.255.255.0 netmasks everywhere, even
though it's a network for one machine only. Dealing with netmasks is a
PITA, and should be avoided unless there's a real reason to use it,
for instance with
Hi,
On Thu, Oct 16, 2008 at 15:51, Marcus Moeller [EMAIL PROTECTED] wrote:
This is definitely not what I am trying to do. I try to line out the
setup again:
Subnet A (192.168.2.x) - DHCP Server with 2 NICs - Subnet B (10.1.0.0)
Clients on Subnet A should get a static IP from the host
John wrote:
Yeah, but you cannot really subnet that way:
JohnStanley Writes:
So let me understand that your saying that if I am Allocated and Own the IP
blocks 64.x.x.33 - 64.x.x.35 that I can not Subnet them Out in any way?
Yes, because that up there contains exactly *one* IP address
See man dhcpd for the details, but I think it would be something like:
# dhcpd -cf /etc/dhcpd-subnetA.conf -lf
/var/lib/dhcpd/dhcpd-subnetA.leases -pf /var/run/dhcpd-subnetA.pid eth0
# dhcpd -cf /etc/dhcpd-subnetB.conf -lf
/var/lib/dhcpd/dhcpd-subnetB.leases -pf /var/run/dhcpd-subnetB.pid Eth1
Yes, because that up there contains exactly *one* IP address - so I'd
hardly
call that blocks.
Where I'm from we call it Blocks or Ipaddy. :-)
I have no idea what you are trying to tell me - you cannot subnet out one
IP address to your PIX firewall.
I wonder why I cant do that, seeing as have
John wrote:
I have no idea what you are trying to tell me - you cannot subnet out one
IP address to your PIX firewall.
I wonder why I cant do that, seeing as have been doing it over 10 years. One
often misguided approach to setting them up is, facing it directly into the
open internet. Your
I wonder why I cant do that, seeing as have been doing it over 10 years.
One
often misguided approach to setting them up is, facing it directly into
the
open internet. Your as good as gone when someone hits up the ftp port on
that shiny new PIX and tunnels right in.
I never heard anyone
This I am not sure can be done with dhcpd. However you can specify NIC to
fixed static addys and the nic harware address in the dhcp.conf file.
How does that work?
JohnStanley Writes:
This is what I am talking about at the end of the .conf file below. That
is what you are trying or wantting to
This I am not sure can be done with dhcpd. However you can specify NIC to
fixed static addys and the nic harware address in the dhcp.conf file.
How does that work?
JohnStanley Writes:
This is what I am talking about at the end of the .conf file below. That
is what you are trying or wantting
Hi all.
I have set up a DHCP server with multiple subnet configurations (let's
say subnet A and B). Within that I have declared pools and static
hosts addresses.
Now, if I have set up a static host entry (with fixed-address) in
Subnet B for a specific machine and try to connect to Subnet A with
On Wed, 15 Oct 2008, Marcus Moeller wrote:
Hi all.
I have set up a DHCP server with multiple subnet configurations
(let's say subnet A and B). Within that I have declared pools and
static hosts addresses.
Now, if I have set up a static host entry (with fixed-address) in
Subnet B for a
I just want the NIC to clain it's address from the range on Subnet A
and to assign a fixed address on Subnet B.
JohnStanley Writes:
In reading your post a couple more times, I think I see what you are after.
Elaborate a little more on what you want exactly.
You want the NIC to get an addy from
I just want the NIC to clain it's address from the range on Subnet A
and to assign a fixed address on Subnet B.
JohnStanley Writes:
You can assign in your dhcp.con file for your hosts to obtain an ip based
upon the host MAC Address or Host Name. Try That..
Dear Paul.
You can assign multiple host blocks for the same NIC, using a fixed-address
directive in one but not in other. dhcpd will try for the best match. If the
request arrives from subnet-B, and the fixed address is on that net, then
that's the block that gets used. Otherwise, the less
Dear John,
In reading your post a couple more times, I think I see what you are after.
Elaborate a little more on what you want exactly.
You want the NIC to get an addy from the dhcpd server from the Subnet A
address pool and then want to also obtain an addy from the Subnet B Fixed
addy pool
35 matches
Mail list logo