@cmb: @tommyboy180: Remember that 2.0 is still BETA and changing frequently. it's not beta anymore and it's not changing much, it's up to package maintainers to update their packages. Now is the time. Awesome!

I never setup a bridge, My wan is connected to vr2 and is working. vr2 (OP1) is working and handing out leases. Just my vr1 (LAN) will not hand over leases. I might have to revert back to pfSense 1.2.3. If I cant figure this out tonight. Robert

that's by design.

anyone who knows the solution?

something I just thought of…. check out Diagnostics/Limiter Info... maybe that will have some info for you but not exactly what you want.... good luck.

That thread refers to FreeBSD 7 and 2.0rc1 is based on FreeBSD 8.1. You are already running a more up to date driver than that. You can see which driver you are using by viewing the sysctl: [1.2.3-RELEASE]                                                                 [root@fire.box]/root(2): sysctl dev.em.1.%desc dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 6.9.6 I am running 1.2.3 on this box as you can see. You will have the legacy driver, which is newer!  ::) Steve Edit: Finally found a good explaination. From version 7.0.0 of the driver the code was seperated into two em and lem, although you won't see that as an end user. The lem driver is for legacy adapters, which is anything pre PCI express.

It appears to be an issue with having a username with an '@' in it.  Once I removed that, everything started to work.  Thanks for your assistance and patience! Jim

I've had the same issue with most of my ALIX routers also, 6 or 7 of them.  None of my config info upgrades properly.  What I've started doing is just backing up the config and dd'ing the full embedded rc1 image to the CF, then reconfiguring manually.  It was the only sure way I knew everything was working.

Same problem, and now, on the other interface. It's not a cable/switch problem. Now the errors grow both on the old lan interface as in the new lan one :(

Happened again and I've been able to narrow the problem. I'll close this and open a new thread.

I will see how it goes with the latest snaps. Been trying to figure a way to get the ARP entries to stay in 1.2.3 when using multiple LAN interfaces.

Updated to the latest snap of today and re-ran the wizard. At the moment this seems to be working. Is it new that the wizard only creates queues for the WAN interface and not for the LAN interfaces anymore?

I understand your frustration but: a) Although 2.0 is now in the RC phase the daily snapshots are not release candidates. As the developers work to fix the bugs in RC1 there is, unfortunately, the possibility that new bugs are introduced. Personally I would stick to the rc1 release unless there is a bug that's causing you difficulty. c) I agree. I should have known there's no 64bit Nano image, my bad!  :-[ Steve

@jevo: Since I have a rule to allow all UDP traffic on port 5060 to pass to the adapter, I am confused as to why it is getting blocked. TCP and UDP packets have two ports: a source port and a destination port. Your rule description doesn't provide enough information to determine whether the blocked packets match the rule. (The logged packets have a source port of 5060 but varying destination ports. Perhaps your rule specified a destination port of 5060.) I know zip about sip so what I'm about to write is entirely speculation. Imagine some downstream of your firewall makes an outgoing access to a sip provider but then goes quite. The firewall will have created a temporary rule to allow responses through the firewall. The "session" stays quiet long enough for the temporary rule to expire. The remote end sends something (perhaps a 'keep alive') and the firewall drops it because the temporary rule that would have allowed that "something" through has expired. Depending on what has been logged, you might be able to confirm that speculation. Perhaps the firewall rules need a longer expiry time OR the "keep alive" time needs to be reduced.

Your LAN link needs to be in the UP and RUNNING states (connected to an active switch or an enabled NIC in another computer) before dhcpd can issue DHCP leases. I don't know what dhcpd does if an interface it is supposed to serve is not in the correct state. Based on the behaviour of some other utilities I wouldn't be surprised if dhcpd stopped if its interface wasn't in the correct state.

Thanks! this is exactly what i have done (tier1 with wan2 to load balance) and this time, pfbox don't hang after moded FW Rules. keep this post, for some people like me with your screenshot will Help! Thanks!

Changing timezone in Squid error messages. http://www.comfsm.fm/computing/squid/FAQ-10.html#ss10.25 Steve