Tested yesterday with the 2/7 snapshot with the same results unfortunately. I only have 2 USB ports on my pfsense system; both on the same controller so neither works. Looks like for now the only work around may be to open up the case to connect an IDE or SATA drive.
no it was set to static. the WAN is actually behind a LAN connection. But the problem was resolved. after creating the other gateway and setting that as default, I noticed that after an unassociated reboot, it was gone.
That's different, that's just how dhcpd works. It doesn't have a listening IP specified, it listens on all IPs on the interface and responds using the interface IP (and can't be changed, as far as I can tell). That doesn't cause any problems.
BSDCan is in Canada. Point taken, though. ;) If you aren't already, subscribe to our announcements list (send a blank email to announce-subscribe@pfsense.com) and you'll get an email when it's scheduled.
My VOIP adapter is NATed. I guess that NAT rules are applied before the floating rules. So floating rules never "see" the LAN IP address of my adapter…
In this case, to send the VOIP traffic in the right queue, I have to choice to use the IP address of the SIP server as destination.
In 2.0 you could do this with IPsec for sure. I think it could be pulled off in 1.2.3 with IPsec but it wouldn't be pretty unless you carefully plan the subnets so they can be CIDR summarized.
