See, this is where my confusion came in. I've got it working now that I was told that I do in fact
have to assign the interfaces. Once I assigned the lan and wan, I was able to connect via the web
interface and everything is now working fine. Until I did that, I was unable to connect to the
webgui to assign a interface to lan/wan.
How can you assign from the webgui? Don't you need to assign a lan interface before a connection to
the lan nic(webgui) could be made?
Well, I've got it working now that I was told I need to assign the interfaces. So far, I like it.
From: dave <dave at rodrig dot com>
Sent: Dec 16, 2003 9:42 PM
To: Bryan Kohlstedt <bkrosco at earthlink dot net>
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Still Can't Connect
You do have to assign a function to the NICs, unless you get lucky and
they happen to be assigned correctly. This can be done now in the
webgui, no need to type the names on the console.
Check out this screenshot to see what I'm talking about.
Are the NICs confirmed good? Have you used them elsewhere?
Bryan Kohlstedt wrote:
> I've been having problems setting up m0n0wall. I've got the .iso burned
> and I can boot off of it. It looks like it detects my cards properly
> (3com 3c905's) but I am unable to connect to the web interface or ping
> the lan interface.
> I believe it's true that we no longer have to assign a function to our
> card (lan/wan) if you're using the latest version. If I'm wrong on that,
> please correct me. I haven't had any luck in the times I've tried
> assigning a function. I always get "invalid interface name." I've tried
> using the mac address as the name but that hasn't worked.
> Anyone have any ideas?
> Bryan Kohlstedt