dhcp3-server question

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Your ip address and netmask look to be correct, to me at least, so
Tyler is right in saying that posting your config file would help
someone here determine where the problem is, since the ip address and
netmask appear to be correct.

To answer your other question whether or not you need a second network
card, that depends on what you want to do. If you want to hook up your
second box to your debian box for the purpose of transferring files
between the 2, then a single network card is fine. If on the other
hand, you want the second box to have access to the internet via the
debian box, and you use broadband instead of dial-up to get internet
access, yes, you will need a second network card in your debian
box. Typically, eth0 is setup by most people as the outside interface,
and eth1 is setup as the inside interface, though how you set it up
doesn't matter, as long as you know what you're doing, and as long as
setting it up in reverse is more convenient for you for some reason. 

If you do need a second network card, and let's assume that the
outside interface is eth0, you don't in theory need to do anything to
tell the dhcp server about your eth0 interface. However, if your dhcp
server doesn't have any config info about eth0, it will complain about
that in your logs whenever you start it up. So, to get rid of the
complaints, you'll still need to define the eth0 subnet in your dhcp
config, but will not want to put anything in that subnet. For example,
eth0 is the outside interface on my server, and it has an ip address
of 172.16.1.10. So, in order to keep the dhcp server from complaining
about not knowing anything regarding my eth0 interface, I have this in
my config:

subnet 172.16.0.0 netmask 255.255.0.0
{
}

As you can see, the subnet is defined, but doesn't have anything in
it.

Hth somewhat, and posting your config file would help us solve your
immediate problem.

Greg


On Sun, Dec 03, 2006 at 12:50:24PM -0700, Ned Granic wrote:
> Hi all,
> 
> I've been coping with this freeking thing forever, and obviously I don't get it.
> I simply want to configure the dhcp3-server so when I connect my other computer to my Linux box with a cross-over cable, the Debian box should issue an ip address through the dhcp to that computer.
> But when I edit the dhcp3.config file, and restart the dhcp3-server, it fails to start.
> The error listed in the /var/log/syslog file is:
> line 32: subnet 192.168.1.1 netmask 255.255.255.0 - bad subnet/netmask combination.
> the 192.168.1.1 is my router.
> There is only one on-board network card on the box.
> Do I need another network card as well for the local network, and how in that case should I configure the dhcp?
> Which one, eth0, or eth1, should be the local, and which one the outer interface?
> I tried to read the manual on the dhcp3-server, but damn, there is nothing I can understand there.
> 
> Many thanks in advance!
> Ned
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager at EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFcz1M7s9z/XlyUyARAtXwAJ4rbr9PlIukLeQCDCxuM5P8uEgLEwCfbYPD
V1OLxqI+iBPVeT8BxuqDYXM=
=Q5FD
-----END PGP SIGNATURE-----