Looks like an IP conflict from router to mono box...
I agree it looks odd with that class A or B mask listed instead of Class
C (setting in mono causing that?).
Try manually setting the mono WAN address to 192.168.1.X where "X" is
outside the DHCP range, maybe "150" or something.
Jeroen Mulder wrote:
> Yes this is what I already did (unchecked "Block Private Networks")
> I also followed the advic e of the other users.
> The LAN side works fine I think. I set it to IP 192.168.0.1 (while my home LAN is on 192.168.1.x)
The dhcp server gives IP addresses 192.168.0.2 -192.168.0.9
> When I want to enter the GUI I connect to hotspot (since it is at the LAN side) and go to
webaddress 192.168.0.1. All fine here.
> The WAN side:
> 1) I unchecked "Block Private Networks" on WAN interface.
> 2) removed firewall rules and made sure there are * in it.
> 3) no NAT stuff
> When I look at the status interfaces tab I see:
> Status up DHCP up MAC address 00:08:74:c9:0b:19 IP address 0.0.0.0 Subnet mask 255.0.0.0
Media 100baseTX <full-duplex> In/out packets 191/40 (22 KB/14 KB) In/out errors 0/0 Collisions 0
> ????? Subnet mask 255.0.0.0 ??? and no IP address.
> Why not 255.255.255.0 since the WAN is connected to LAN port of router and it give IP addresses in
> When I look in the log:
> Aug 5 19:51:36 dhclient: DHCPREQUEST on em0 to 255.255.255.255 port 67 Aug 5 19:51:36 dhclient:
DHCPOFFER from 192.168.1.100 Aug 5 19:51:36 dhclient: DHCPDISCOVER on em0 to 255.255.255.255 port 67
interval 6 Aug 5 19:51:36 dhclient: no expiry time on offered lease. Aug 5 19:51:36 dhclient:
DHCPACK from 192.168.1.100 Aug 5 19:51:35 dhclient: DHCPREQUEST on em0 to 255.255.255.255 port 67
Aug 5 19:51:35 dhclient: DHCPOFFER from 192.168.1.100 Aug 5 19:51:35 dhclient: DHCPDISCOVER on em0
to 255.255.255.255 port 67 interval 3 Aug 5 19:51:35 dhclient: no expiry time on offered lease. Aug
5 19:51:35 dhclient: DHCPACK from 192.168.1.100 Aug 5 19:51:34 dhclient: DHCPREQUEST on em0 to
255.255.255.255 port 67 Aug 5 19:51:34 dhclient: DHCPOFFER from 192.168.1.100 Aug 5 19:51:34
dhclient: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 5 Aug 5 19:51:34 dhclient: no
expiry time on offered lease.
> I sure looks like my router 192.168.1.100 (this is an other subnet isn't it ?) is offering a DHCP
> But is m0n0wall not taking it ??
> Any suggestions ?
>> Date: Tue, 5 Aug 2008 04:53:35 -0600> From: apt dot get at gmail dot com> Subject: Re: [m0n0wall] setting up
hotspot> CC: jaj dot mulder at hotmail dot com; m0n0wall at lists dot m0n0 dot ch> > On Mon, Aug 4, 2008 at 3:29 PM,
Melvin <melvin at sleepydragon dot net> wrote:> > Jeroen Mulder wrote:> >>> >> Hi,> >> I have been
struggling with this for over a week now.> >> Also i must say I am no network expert.> >> Starting
from this article I tried to setup a captive portal.> >>
http://www.ciscopress.com/articles/article.asp?p=704315> >> I did as described but I couldn't get it
to work.> >> In this article I also don't understand how one could get an ipaddress> >> from the WAN
side but anyway.> >> This is what I tried (and want to achieve)> >> internet----modem (sip spoof)
---- WAN snb6500 router LAN 192.168.1.100> >> ------WAN m0n0wall LAN-----AP> >> I have read the
mailing list before and I have seen suggestions of> >> connecting m0n0wall directly to the modem.>
>> I don't want this. I don't want to change existing infra structure. I only> >> want to add
monowall and an AP> >> I tried all kind of stuff> >> Swapping WAN and LAN, different subnets for LAN
connected to AP. Nothing> >> seems to work> >> When I look at the interface part of monowall I see
no IP address assigned> >> on one side . I thought my snb6500 router would distribute an IP to the>
>> monowall but it doesn't ?? (yes dhcp is on in router) I do get an address> >> from mono when
connecting to the AP (called hotspot)> >> What am I missing. Is it that hard to set up a hotspot ??>
>> Or am I really doing stupid things here ?> >> regards,> >> J Mulder> >> Ps running version 1.233
livecd> >> _________________________________________________________________> >>> >> > Just a guess,
but since you're using Private IPs on both sides of m0n0, you> > need to make sure you enable them
in the interface. Also, make sure you> > aren't using the same subnet for the WAN and LAN sides of
m0n0.> > Or in other words, go to m0n0wall's "Interfaces>WAN" page and uncheck> the box that says
"Block Private Networks" and click the save button.> > db
> Express yourself instantly with MSN Messenger! Download today it's FREE!