[ previous ] [ next ] [ threads ]
 
 From:  "Jeremy" <Mr dot Jeremy at verizon dot net>
 To:  "'James W. McKeand'" <james at mckeand dot biz>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] DHCP on opt1
 Date:  Tue, 28 Sep 2004 22:50:30 -0400
Basically, what I can't get to work is having m0n0wall run 2 separate DHCP
servers on 2 different subnets.

-----Original Message-----
From: James W. McKeand [mailto:james at mckeand dot biz] 
Sent: Tuesday, September 28, 2004 8:45 PM
To: 'Jeremy'
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: RE: [m0n0wall] DHCP on opt1

A few of questions come to mind: (keep in mind this after a very, very long
day - may seem random)

Do you have the OPT1 bridged to another interface? (I have mine set as
"Bridge with NONE")

Do you have you OPT1 and LAN on different subnets? In other words, assuming
the default LAN IP of 192.168.1.1/24, is your OPT1 something like
192.168.2.1/24? (Note the third octets are different) Try some thing totally
different: I use 192.168.x.x on my LAN and 172.16.x.x on my LAN2 (OPT1)

Do you have "Deny unknown clients" checked with no MAC addresses in your
static mapping list?

Does the IP of the OPT1 interface match the subnet/available range in the
DHCP tab? I will try this when I am more awake...

Can your laptop connect to the AP with it disconnected from the m0n0? This
may only work if the AP supplies its own DHCP (default on my Belkin).

Sleep good, must get sleep...

_________________________________
James W. McKeand


-----Original Message-----
From: Jeremy [mailto:Mr dot Jeremy at verizon dot net] 
Sent: Tuesday, September 28, 2004 4:58 PM
To: james at mckeand dot biz; 'David Kitchens'
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: RE: [m0n0wall] DHCP on opt1

Yes, this is the same setup I'm using. Even if I connect my laptop to the
OPT1 (WLAN) interface, I cannot receive a IP address, but I can from the LAN
NIC.

-----Original Message-----
From: james at mckeand dot biz [mailto:james at mckeand dot biz]
Sent: Tuesday, September 28, 2004 8:59 AM
To: David Kitchens; 'Jeremy'
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: RE: [m0n0wall] DHCP on opt1

I believe, WEP and DHCP running on a wifi interface on m0n0 is a known
issue. But this is not the issue here.

I am not running hostap on my m0n0. I am running a separate AP (cheap
Belkin). Once entered the key in my WEP settings on the laptop I was able to
talk to the AP and get an IP from my m0n0. I believe Jeremy is using a
similar setup (correct me if I'm wrong) - he mentioned that he has a 3rd
ethernet.

_________________________________
James W. McKeand

----- Original Message -----
From: "David Kitchens" <spider at webweaver dot com>
Date: Tue, 28 Sep 2004 00:10:10 -0400
To: "'James W. McKeand'" <james at mckeand dot biz>,"'Jeremy'"
<Mr dot Jeremy at verizon dot net>
Subject: RE: [m0n0wall] DHCP on opt1

> Once again, the WEP issue appears, this IS an issue that needs to be 
> addressed. To state the problem simply once again, turning WEP on 
> negates the ability to receive an IP from DHCP. I have tried for 
> months now to put this issue on the table but its been sporadic in 
> user complaints. I think
by
> now, many users have seen this problem and if I had the ability to dig
into
> the image, I would do so gladly but I'm no BSD guru. I use a Soekris 
> 4511
at
> home and am planning on deploying several hotspots in my town soon. I
would
> like to see some work on this problem and I would be happy to do any
testing
> on my home unit if someone can tell me where to start.
> 
> Dave
> 
> > -----Original Message-----
> > From: James W. McKeand [mailto:james at mckeand dot biz]
> > Sent: Monday, September 27, 2004 9:56 AM
> > To: 'Jeremy'
> > Cc: m0n0wall at lists dot m0n0 dot ch
> > Subject: RE: [m0n0wall] DHCP on opt1
> > 
> > I initially had problems not getting an IP from my OPT1 DHCP 
> > interface from a wireless client. My problem was that I had enabled 
> > WEP (my only option on my AP) and the client was not connecting to 
> > the AP. Once that was resolved, I got an IP from my m0n0 and 
> > everything worked.
> > 
> > Are your wireless clients connecting to the AP? Try setting up the 
> > AP on the LAN side just for testing...
> > 
> > Can you connect a wired client to the OPT1 interface on the m0n0 and 
> > get an IP? It should be a separate subnet.
> > 
> > I think the only difference to your config is that I only have DHCP 
> > running my Opt1 interface, not my LAN interface.
> > 
> > _________________________________
> > James W. McKeand
> > 
> > 
> > -----Original Message-----
> > From: Jeremy [mailto:Mr dot Jeremy at verizon dot net]
> > Sent: Sunday, September 26, 2004 1:27 AM
> > To: m0n0wall at lists dot m0n0 dot ch
> > Subject: [m0n0wall] DHCP on opt1
> > 
> > I am trying to run a Monowall firewall so that users on the wireless 
> > network have to use VPN to connect. I have 3 ethernet cards 
> > installed in the computer and monowall installed. The 3rd network 
> > card is set as opt1 and has DHCP server turned on (as does the LAN 
> > one) but I cannot seem to get a DHCP lease from it. I can only get 
> > an IP from the LAN NIC. Is there some step I'm missing?
> > 
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> > 
> > 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch


---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch