I can connect to my WG X700 with no problems. You need to set 9600/8/N/1 with hardware flow control enabled…

spamd has been removed.  if this makes anyone angry you can blame erict35 for his loving private message he sent me.

Try latest snap.

seems to be working now with latest snapshot

I have seen that message during normal operation when the network adapter physically loses link. Sure that your cable and switch are OK? Can you swap cables, change switch ports, and see if the problem persists?

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.

eri at pfsense.org Please send your logs, config.xml, rules.debug, ifconfig, netstat -rn.

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.

I'm seeing the same thing. http://redmine.pfsense.org/issues/show/345

Works for me. /usr/local/bin/wol -i 192.168.1.255 00:1f:32:78:bc:23 Waking up 00:1f:32:78:bc:23… Works from the GUI too. I'm on a snapshot from Feb. 6, though nothing has changed related to wol in a while. Can you replicate on another system or provide any details on something specific to your setup that might be causing it?

@redvivi: It seems that DHCPd works that way too. 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.

lsf had started working on some patches for this a month or so ago, but I haven't seen him around in a while.

OK, I think I found why it doesn't work. 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.

Yes, you can do this easily with OpenVPN. 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. It's explained in lots more detail in the book.

@ermal: Can you send your config.xml to me eri at pfsense.org to see what is going wrong? will do - bit tied up at mo' ryts