Hi Brett, Craig, > --- Craig Caughlin <[EMAIL PROTECTED]> wrote: > > >> Hi Eric, >> The only thing I have done to get things up and >> running is: >> >> I've uncommented >> "dhcp-range=192.168.1.1,192.168.1.199,12h" in the >> /etc/dnsmasq.conf file. Do I need to do something >> different? >> >> Also, should I add another interface in >> /etc/dhcpc/config ? I see at the >> bottom it says, # Add other interfaces here *) >> ;; >> >> >> Should I add eth2? What does the syntax look like?: >> >> >> # Add other interfaces here >> *) >> eth2 ;; >> >> >> Is that right (and/or do I even need to worry about >> it?)? >> >> Thank you! :-) >> >> >> Craig >> >> >> -----Original Message----- >> From: Eric Spakman [mailto:[EMAIL PROTECTED] >> Sent: Saturday, December 23, 2006 10:35 AM >> To: Craig Caughlin >> Cc: [email protected] >> Subject: Re: [leaf-user] No DHCP address to the DMZ >> :-( >> >> >> Hi Craig, >> >> >>> Hi folks, >>> Happy Holidays. :-) >>> >>> >> Happy Holidays to you ;-) >> >> >>> I'm using the new, Bering uClibc 3.0, and my LAN >>> >> connections to/from the >>> web, etc. work great. >>> >>> Now, I'm trying to set up a wireless router in my >>> >> DMZ, and it's not getting >> >>> a dynamic IP address (I have confirmed this by >> connecting a laptop via >>> crossover cable directly to the DMZ NIC). Here's my >> scenario: >> >>> >>> 1. I'm using the new, Bering uClibc 3.0 >>> 2. ip addr show displays: >>> >>> >>> eth0: mtu 1500 qdisc pfifo_fast qlen 1000 >>> link/ether 00:02:e3:1d:e2:a5 brd ff:ff:ff:ff:ff:ff inet >>> 67.164.217.61/23 brd 255.255.255.255 scope >>> >> global eth0 >>> >>> eth1: mtu 1500 qdisc pfifo_fast qlen 1000 >>> link/ether 00:02:e3:23:c1:1f brd ff:ff:ff:ff:ff:ff inet >>> 192.168.1.254/24 brd 192.168.1.255 scope >>> >> global eth1 >>> >>> eth2: mtu 1500 qdisc pfifo_fast qlen 1000 >>> link/ether 00:02:e3:22:a0:51 brd ff:ff:ff:ff:ff:ff inet >>> 192.168.1.100/24 brd 192.168.1.255 scope >>> >> global eth2 >>> >>> 3. I uncommented the DMZ section of >>> >> /etc/network/interfaces >> > <snip> > > > Hello, > I think you are getting a static address because that > is the default behavior of the /etc/network/interfaces file. If all you did > was uncomment the default it should look like this? > > auto eth2 iface eth2 inet static address 192.168.1.100 netmask 255.255.255.0 > broadcast 192.168.1.255 > > To us dhcp on eth2 you need to have it like this > > > auto eth2 iface eth2 inet dhcp > > Have you done this already? Be sure to restart > networking, and maybe shorewall. > > HTH, > Brett >
It depends. If you want Bering-uClibc to be a dhcp _client_, this is indeed correct. But I got the impression that Craig tried to use Bering-uClibc to be a dhcp _server_ for clients on the DMZ. Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
