@ryanswj:

@wallabybob:

Did you enable DHCP Server on the LAN interface? (See Services -> DHCP Server)

Nope, I don't think I have. Is that the cause of all my problems?

It will be a factor. You said @ryanswj:

I can see the Wireless AP that was created, but no IP addresses were assigned to clients.

If you don't have an active DHCP server then clients won't be assigned an IP address.

@ryanswj:

Furthermore, why does the WebUI stop responding?

Presumably because you have switched interfaces or reassigned LAN subnet IP address.

If I was trying to make your configuration work I would first make ae0 (wired interface) the LAN and ath0 (wireless) the WAN. Then through the web GUI I would enter wireless configuration details and verify a wireless client could associate (using a static IP address on the client). Then I would choose assign interfaces and swap LAN and WAN (LAN as ath0, WAN as ae0) and reboot through the console.

Wireless configuration can some times be challenge due to signal quality issues and (if your typing is as bad as mine) the challenge of correctly entering the encryption key. I have also found some encryption options don't work well with some clients so its best to sort that out BEFORE making the pfSense LAN interface a wireless interface. It has been my experience that a reboot has sometimes seemed to be necessary to persuade pfSense to correctly behave after major interface related changes such as swapping interface roles.

You didn't explain why you might want to bridge WAN and LAN interfaces. I would be inclined to get it working as a router first. (I have a wired LAN and a wireless LAN bridged together on my pfSense and I need to NAT my internet access so its not appropriate for me to bridge WAN and LAN.)

@ryanswj:

Is my configuration correct (LAN and WAN)?

I don't have enough information about your configuration to say.

Sysctrl Kernel default values to run squid,postfix,varnish for example are better on 64 bits.

@geluykens:

My modem includes a router, so no ISP problem.

Like wallabybob says, I have reconfigured the interfaces to different subnets:

[modem in DHCP(isp)–---out X.X.0.1]–---[firewall in (DHCP)–---out X.X.2.1]–---[router in X.X.2.2–---out X.X.1.1]–---> network

So I can't give the firewall WAN interface a static ip ?

I just tried and everything stiil works. My setup now is:
[modem in DHCP(isp)–---out X.X.0.1]–---[firewall in X.X.0.2–---out X.X.2.1]–---[router in X.X.2.2–---out X.X.1.1]–---> network

Thx for the support.

I added a couple links and a couple extra lines in the embedded upgrade section. Should be a little more clear now.

Thx, I discovered it reading on the forum.

When I arrived to my company the pfSense was installed previously and I don't know about the different versions for install them on low capacity devices. I proposed to link to the faq about this question on the upgrade guide.

Thank you for your answer,
Yup you got it. Linking 4 or 5 int isn't prooving so easy. Will just drop the VMware install, and run it on an old Server in just unearthed.

Thank you for your help.

FlyPig.

Hi there,

I'm using pfSense 2.0 as a transparent firewall.
As somebody had the same question some time ago I already explained it in this post.
Feel free to ask question there.

Christoph

@wallabybob:

I have contributed to this discussion because I thought that some additional data might help identify the problem

As did I yet I can see I've only added confusion!  ::)

Steve

I committed the text fixes, should help clear things up. Thanks!

There are no issues I am aware of. Certainly it went smoothly for me.
I would guess you had a package installed that didn't play nicely and removed a file it shouldn't have.
What packages were you running (or had been running)?

Steve

Save the configuration (pfSense GUI Diagnostics -> Backup/Restore) should save everything pfSense knows about. Then restore to a fresh install.

Depending on a number of factors, it might be easier/quicker to just clone your hard drive (e.g. pfSense shell command dd if=/dev/ad0 of=/dev/ad2 bs=65536 where ad0 is your current pfSense install and ad2 is the copy). On first boot of the copied drive the OS startup will likely mention a few file system fixups. I have used variations of this procedure a number of times.

Hey!

What partitions do you have on your hdd?
Or do you have a running system in the meanwhile?

Hi, as long as your MOBO are supported with 2.0.

I tried this kind of test several times on my lab and works perfectly, since both MOBO are supported with the current version.

thanks

This is now resolved. I did nothing but delete the virtual IP and re-create it for the main IP address .. and this resolved the problem. I can only thing some tables either in the firewall or the switch that lies between firewall and server had got confused with so many IP addresses having the same arp mac address.

So all happy now,
Dave

For the record my eth0 on the server looks like:-

eth0 192.168.1.229  (I think of this as the main IP address - this is the one which caused problems).
eth0:abc  192.168.1.230
eth0:xyz 192.168.1.231
….
Loads of multi-homed ip addresses on single server. All 255.255.255.0 netmask, and all 1:1 mapped to external IP's in firewall.

You should check the logs to make sure it is being caused by an unrecognised hardware version. It might be something completely different and easily fixable.

pfSense 2.1 will be based on FreeBSD 9.X and so will have far newer drivers. With the new six month release cycle this should be out around March. Even if it isn't there will probably be betas before then.

Steve

Looks like you had fun with that!  ;)

Nice detailed write up.

Steve

Won't have a chance to try this out until a little later today but I just wanted to say thanks for the response. If I can get everything setup the way I hope to, I plan to write a very detailed tutorial as this has been a very frustrating experience.

It's not a Tier 1 architecture in FreeBSD these days anyhow… From /usr/src/UPDATING

NOTE TO PEOPLE WHO THINK THAT FreeBSD 8.x IS SLOW ON IA64 OR SUN4V:         For ia64 the INVARIANTS and INVARIANT_SUPPORT kernel options         were left in the GENERIC kernel because the kernel does not         work properly without them.  For sun4v all of the normal kernel         debugging tools present in HEAD were left in place because         sun4v support still needs work to become production ready.

So even if you could get them to work, they would be even slower than usual.

See also: http://www.freebsd.org/doc/en/articles/committers-guide/archs.html

Thanks for the suggestion, i had not had time to try this until last night.  The BIOS does not let me set the SATA mode.  I did try an IDE DVD rom and still no dice.