It turned out that motherboard was to blame… From 4 on-board ports 2 were giving me send/receive errors... I bought new system with intel d2500cce which should last longer that this one (2 yrs)... Thanks all!

Under status->gateways and on the homescreen. Seems to be alright on the new builds though atm.

Just some additional info, as I too have been attempting to get this card working with pfsense v2.0.1 http://www.freebsd.org/cgi/query-pr.cgi?pr=165154 Appears it's a dirty matter of recompiling the kernel. I'm looking for other solutions such as replacing modules with newer software versions, if such a solution exists. Jason

1024mb of ram.. should be overkill for my home network. Never had any issues before ? :( @jimp: Looks like the crash in that one is from your wireless card. Wifi card? How can u tell? Hmm.. that could be case, I had it disabled in older versions (I forgot that I enabled it again). Hoped they would solve the crash problem with this card in the latest snapshots :(  I am using a really awesome mini firewall device : http://www.fit-pc2.com/download/fit-pc2i-owner-manual-english.pdf Too bad the wifi still doesn't work with pfsense. Any idea's on how to fix this?

Hi I would to confirm that built on Tue Aug 20 13:38:38 of PF-Sense 2.1 all function of PPPs Menu is working correct and perfect. Thank you :)

Hi ermal Sorry for the late answer You want that I try if I can get dhcp6 addresses from the secondary host right ? I can test this for you but you have to say me what exactly you want know. regards supermega

Have anybody the same problem I'm still working at this issue  :(

@cthomas: is there anything else that I can, or need to do to help get this in the development pipeline? Open a bug report or CR on http://redmine.pfsense.org, if you haven't already done so?

@autotalon: Tank Tank Tank wouldnt do anything when it was behind a firewall. <snip>third party developer documentation for the WiiU regarding networking actually suggested DMZ as the way to set it up, which seemed a little odd to me.</snip> Definitely odd. I wouldn't expect Tanks in a Demilitarized Zone.

Traced to broken Read Later Fast extension in Chrome. Error in event handler for 'undefined': superfishjs is not defined ReferenceError: superfishjs is not defined     at chrome-extension://decdfngdidijkdjgbknlnepdljfaepji/js/contentScript.js:190:19     at <error: illegal="" access="">at Event.dispatchToListener (event_bindings:356:21)     at Event.dispatch_ (event_bindings:342:27)     at Event.dispatch (event_bindings:362:17)     at Object.chromeHidden.Port.dispatchOnMessage (miscellaneous_bindings:273:22) [VM] event_bindings (2679):346</error:>

Hello, I confirm, on the very last snapshot (built on Mon Aug 19 16:16:08 EDT 2013) the DNSes got from the PPP connection are successfully used, the file /var/etc/nameserver_pppoe0 contains the DNS, and everything works great again… Thanks a lot Jim!! Michele

@jimp: No it has changed in many ways from 2.0.3, mostly IPv6 but also quite a few other enhancements in other areas unrelated to IPv6. If there are potential areas you're interested in seeing screencaps of we can try to get some together, but to randomly produce and post a bunch of 2.1 screenshots isn't really something many of us have time for at the moment. Yes, what I meant was that the GUI menu were looking about to be the same as in 2.0.3. My bad for bad interpretation.

Update 8/21/2013: I've now had a connection for 16 Days 07 Hours 52 Minutes 17 Seconds using build 2.1-RC1 (i386) built on Thu Aug 1 19:03:40 EDT 2013. This is the longest I've maintained a connection with no reboots or any other action.

@athurdent: Diagnostics -> Backup/Restore has a "Reinstall packages" button at the bottom. ORLY?  :o :-[ Thanks for tip, will try when I can mess with this. Need the uplink working right now.  :D

I'm still having this issue. Can anyone suggest a way to find out what is causing this? I have IPv6 disabled for the moment but I'm still seeing this issue: Aug 18 23:58:13 php: rc.filter_configure_sync: The command '/sbin/route change -inet6 default fe80::1' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::1: Network is unreachable'

Okay, couple things. Which ESXi -exactly-? Version and build number. Are you running the vmxnet2 as Flexible? Can you please retest with the 'legacy' interface? Preferably in pcn(4) mode over lnc(4) mode. I'm rusty so I forget how to force that behavior. (Hell, I forget if the PCIID changes were committed.) How many em(4) (aka e1000) interfaces are you running during testing? Yes, this matters. I think part of the problem is that 2.1 pulled in a bad em(4) branch - but I haven't had time to test more in depth. EDIT: Oh, can you also please check to see if you have "calcru: runtime went backwards" messages?

Issue #3152 created.