*** From dhcp-server -- To unsubscribe, see the end of this message. ***
> I wanted to get addresses for eth0 and eth2 over the eth2 interface.
> Sorry, I should have been more specific.
I still don't get it. You have a DHCP server on the network to which
eth2 is attached. The machine you're setting up is going to be the
router between the eth0 network and the eth2 network. How can you
expect a DHCP server to assign an address for the eth0 interface?
Why don't you just configure it on system startup? DHCP isn't meant
for configuring routers.
> It must be no-brain day for me... What I meant was can/will DHCP get
> addresses for IP aliasing, like eth0:0 and eth0:1, etc.
No, it won't. Why would you want to do that?
> By the way, have you ever heard of Samba not running on a DHCP system?
> I keep getting "Unable to bind to socket 139: Address 0.0.0.0:139
> already in use." It works fine on a non-DHCP system, but I wanted my
> DHCP and Samba to be the same system.
There is no chance that this is a DHCP-related problem. Chances are
that you're starting Samba twice - maybe once as a daemon and once out
of inetd.conf.
_MelloN_
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
------------------------------------------------------------------------------
