[pfSense Support] Re: Multi-WAN PPTP?
On Mon, Jan 5, 2009 at 11:26 PM, Morgan Reed morgan.s.r...@gmail.com wrote: I've added a firewall rule to allow 1723 in on WAN2 but there appears to be something else required as my connection attempts timeout at authentication (I've been able to connect PPTP to the WAN2 interface from inside the office with no trouble so I assume that means that the PPTP daemon listens on all interfaces) I recall PPTP also uses IP Proto 47 (GRE), do I need to add a rule to allow that traffic on WAN2? Scratch that last bit, I'm too used to M0n0wall methinks, now added a rule to allow GRE in on the WAN2 interface address, still timing out at Verifying Username and Password though. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] em0: Watchdog timeout -- resetting
Paul M wrote: linux - there used to be a problem with the e1000 driver when power saving is enabled in the e1000's eeprom. the fix worked, and I applied it by booting a linux rescue disk and ran the eeprom fix program that I got from the e1000 sourceforce website; their wiki seems to have disappeared so I can't find the script, so I've placed a copy here: http://www.zaurus.org.uk/download/scripts/fixeep-82573-dspd.sh if you have the problem on linux you get detected tx unit hang thus: http://sourceforge.net/tracker/index.php?func=detailaid=1463045group_id=42302atid=447449 p.s. I believe that in theory Intel and manufacturers using their e1000 chips were supposed to be turning this off. p.p.s. I don't think there's any equivalent of ethtool -e eth0 for freebsd, so you can't run that script directly on pfsense/freebsd. If there were, you'd get this: # ethtool -e eth5 Offset Values -- -- 0x 00 e0 81 4b 53 b7 30 0b 47 f6 02 10 ff ff ff ff 0x0010 ff ff ff ff 6b 22 91 51 f1 10 8b 10 86 80 df ac 0x0020 21 00 02 20 04 7e 00 00 00 10 d8 00 00 00 00 27 0x0030 c9 6c 50 31 22 07 0b 04 84 09 00 00 00 c0 07 06 - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: AW: [pfSense Support] em0: Watchdog timeout -- resetting
I agree with both of your statements. The portfast option isn't a solution, but it does make debugging this issue a lot less painful. Admittedly, I did not expect to run into hardware/driver issues when I was buying these NICs. :( In fact, that's exactly the reason I went with Intel HW in the first place. Thank You, Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC Atlas Networks is an Atlas Accelerator Company -Original Message- From: Paul Mansfield [mailto:it-admin-pfse...@taptu.com] Sent: Monday, January 05, 2009 3:01 AM To: support@pfsense.com Subject: Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting Fuchs, Martin wrote: And perhaps try to set the port speed in pfsense AND the switch, e.g. 1000MBit FD... Sometimes this helps, too Once you start setting port speeds to fix rates and duplex you're going down a long and slippery slope, it's best to avoid it unless there's a proven good reason! -Ursprüngliche Nachricht- Von: apiase...@midatlanticbb.com [mailto:apiase...@midatlanticbb.com] Can't help with your pfsense problem, but it might help to configure this on your switch. spanning-tree portfast Configured on your cisco switch will change the port to a forwarding state immediately. this might help hide the symptom of the interface bouncing but isn't really a cure - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: [pfSense Support] WAN IP Pool
Yep. If you are wanting to use nat, use virtual IP to set up additional Ip address and then use 1:1 nat to specify which internal IPs you would like on which external IP addresses. I am not sure, but i think you must enable advanced outbound nat as well. I hope this helps, Ryan From: Abdulrehman [mailto:arvagabo...@gmail.com] Sent: Monday, January 05, 2009 6:46 AM To: support@pfsense.com Subject: [pfSense Support] WAN IP Pool Hy i am using fiber optic as my WAN...i have to Network cards fxp0 and vr0.fxp0 is my LAN side and vr0 is my WAN side. I have 16 IP Pool from my ISP and i want to use this Pool behind my Pfsense firewall.Any help...?Thanks in advance. Regards Abdulrehman
Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting
Fuchs, Martin wrote: And perhaps try to set the port speed in pfsense AND the switch, e.g. 1000MBit FD... Sometimes this helps, too Once you start setting port speeds to fix rates and duplex you're going down a long and slippery slope, it's best to avoid it unless there's a proven good reason! -Ursprüngliche Nachricht- Von: apiase...@midatlanticbb.com [mailto:apiase...@midatlanticbb.com] Can't help with your pfsense problem, but it might help to configure this on your switch. spanning-tree portfast Configured on your cisco switch will change the port to a forwarding state immediately. this might help hide the symptom of the interface bouncing but isn't really a cure - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] new to pfSense - Soekris 4801 wireless fails to do DHCP
Wireless seems to be working, but the most important thing (IP address) isn't. I should say that I am now associated with an 11g client (both sides agree with this assessment), but I can't get DHCP to hand out a pool IP address: According to the Status - Interfaces page: OPT2 interface (ath0) Status associated DHCP up MAC address 00:xx:xx:xx:xx:xx IP address 0.0.0.0 Subnet mask 255.0.0.0 Mediaautoselect mode 11g hostap Channel 1 SSID x And pfSense claims the DHCP server is running. Yet according to Status - DHCP leases there are none: Diagnostics: DHCP leases IP address MAC address Hostname Start End Online Lease Type I am running pfSense 1.2.1 on a Soekris 4801 with a Wistron CM9 mini-PCI card: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5212 mem 0xa001-0xa001 irq 11 at device 14.0 on pci0 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:xx:xx:xx:xx:xx ath0: mac 5.9 phy 4.3 radio 3.6 I see many of these lines in the pfSense logs and in dmesg output via ssh(8): ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490 hal flags 0x150) ath0: unable to reset hardware; hal status 12 I used this URL as a guide: http://doc.pfsense.org/index.php/Access_Point2 I don't have a DHCP server on my local LAN, instead I configured the built-in pfSense DHCP server with three IP addresses to give out. It is not happening. :-( BTW, I have bridged the OPT2 (ath0) interface with the Soekris LAN interface. Any ideas or thoughts on what I am doing wrong would be most appreciated. Regards, web... -- William Bulley Email: w...@umich.edu - End forwarded message - -- Regards, web... -- William Bulley Email: w...@umich.edu - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] Multi-WAN PPTP?
Hi all, We've a multi-WAN setup on our pfSense (no redundancy or load balancing, one is dedicated to office internet traffic, the other is dedicated to inbound server traffic), just wondering if it's possible to setup pfSense so we can accept PPTP in on either WAN link (that way if the main link is down we can come in the backup and vice versa). pfSense is our PPTP server, and it authenticates against our Windows 2000 AD via RADIUS/IAS if that makes any difference. I've added a firewall rule to allow 1723 in on WAN2 but there appears to be something else required as my connection attempts timeout at authentication (I've been able to connect PPTP to the WAN2 interface from inside the office with no trouble so I assume that means that the PPTP daemon listens on all interfaces) I recall PPTP also uses IP Proto 47 (GRE), do I need to add a rule to allow that traffic on WAN2? Any suggestions? Thanks, Morgan - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
AW: AW: [pfSense Support] em0: Watchdog timeout -- resetting
That's true, but I know some cases where I used Intel cards 1000 MBit and had this problem... Therefore I said sometimes this helps... (even a pfsense-system but with a hp switch) Of course it's better to use autodetect, but it's worth a try... Regards, Martin -Ursprüngliche Nachricht- Von: Paul Mansfield [mailto:it-admin-pfse...@taptu.com] Gesendet: Montag, 5. Januar 2009 12:01 An: support@pfsense.com Betreff: Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting Fuchs, Martin wrote: And perhaps try to set the port speed in pfsense AND the switch, e.g. 1000MBit FD... Sometimes this helps, too Once you start setting port speeds to fix rates and duplex you're going down a long and slippery slope, it's best to avoid it unless there's a proven good reason! -Ursprüngliche Nachricht- Von: apiase...@midatlanticbb.com [mailto:apiase...@midatlanticbb.com] Can't help with your pfsense problem, but it might help to configure this on your switch. spanning-tree portfast Configured on your cisco switch will change the port to a forwarding state immediately. this might help hide the symptom of the interface bouncing but isn't really a cure - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] ntop Crashing after a day or two
apiase...@midatlanticbb.com wrote: Ntop is pretty cool, i just can't seem to keep it running. It crashes anywhere from a couple of hours to a day. Any tips? try darkstat instead? - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] WAN IP Pool
Hy i am using fiber optic as my WAN...i have to Network cards fxp0 and vr0.fxp0 is my LAN side and vr0 is my WAN side. I have 16 IP Pool from my ISP and i want to use this Pool behind my Pfsense firewall.Any help...?Thanks in advance. Regards Abdulrehman
Re: [pfSense Support] new to pfSense - Soekris 4801 wireless fails to do DHCP
Make sure you have the appropriate firewall rules on your OPT2 interface to allow traffic to pass. Also, you mentioned I don't have a DHCP server on my local LAN, instead I configured the built-in pfSense DHCP server with three IP addresses to give out. Does that mean you have some static DHCP assignments set but not a general DHCP range open? One more thing, when bridging a wireless interface to a wired one, make sure the wired interface has a physical ethernet link to something. I've seen it interfere with bridging many times. Tim Nelson Systems/Network Support Rockbochs Inc. (218)727-4332 x105 - William Bulley w...@umich.edu wrote: Wireless seems to be working, but the most important thing (IP address) isn't. I should say that I am now associated with an 11g client (both sides agree with this assessment), but I can't get DHCP to hand out a pool IP address: According to the Status - Interfaces page: OPT2 interface (ath0) Status associated DHCP up MAC address00:xx:xx:xx:xx:xx IP address 0.0.0.0 Subnet mask255.0.0.0 Media autoselect mode 11g hostap Channel1 SSID x And pfSense claims the DHCP server is running. Yet according to Status - DHCP leases there are none: Diagnostics: DHCP leases IP address MAC address Hostname Start End Online Lease Type I am running pfSense 1.2.1 on a Soekris 4801 with a Wistron CM9 mini-PCI card: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: Atheros 5212 mem 0xa001-0xa001 irq 11 at device 14.0 on pci0 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:xx:xx:xx:xx:xx ath0: mac 5.9 phy 4.3 radio 3.6 I see many of these lines in the pfSense logs and in dmesg output via ssh(8): ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490 hal flags 0x150) ath0: unable to reset hardware; hal status 12 I used this URL as a guide: http://doc.pfsense.org/index.php/Access_Point2 I don't have a DHCP server on my local LAN, instead I configured the built-in pfSense DHCP server with three IP addresses to give out. It is not happening. :-( BTW, I have bridged the OPT2 (ath0) interface with the Soekris LAN interface. Any ideas or thoughts on what I am doing wrong would be most appreciated. Regards, web... -- William Bulley Email: w...@umich.edu - End forwarded message - -- Regards, web... -- William Bulley Email: w...@umich.edu - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] new to pfSense - Soekris 4801 wireless fails to do DHCP
According to Tim Nelson tnel...@rockbochs.com on Mon, 01/05/09 at 15:19: Make sure you have the appropriate firewall rules on your OPT2 interface to allow traffic to pass. Following the example at the URL shown in my first message I set the OPT2 (ath0) interface to all any or * * * * * * Do I need any more rules than that? I have a similar rule on the LAN interface to let anything in to the Soekris. All this is behind my m0n0wall router/firewall. So the Soekris is nothing more than an expensive access point (albeit running FreeBSD!) Also, you mentioned I don't have a DHCP server on my local LAN, instead I configured the built-in pfSense DHCP server with three IP addresses to give out. Does that mean you have some static DHCP assignments set but not a general DHCP range open? I am using RFC1918 (net ten) non-routeable addresses behind my m0n0wall which is 10.0.0.1 So the LAN interface on the 4801 is 10.0.0.33 and the other three IP addresses in the DHCP pool are 10.0.0.11, .12, .13 So I have a small pool (range) configured in pfSense on the 4801. Is this the right thing to do? That is, will the DHCP server on the 4801 hand out these pool IP addresses to associated 11g clients? Isn't working at present... :-( One more thing, when bridging a wireless interface to a wired one, make sure the wired interface has a physical ethernet link to something. I've seen it interfere with bridging many times. I have my 4801 LAN interface wired to one of the m0n0wall ethernet jacks, and I have statically configured in pfSense the 10.0.0.33 IP address along with the (static) 10.0.0.1 gateway. I can reach the 4801 (pfSense/FreeBSD) using ssh(8) from other boxes on my local LAN. Help? Regards, web... -- William Bulley Email: w...@umich.edu - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] new to pfSense - Soekris 4801 wireless fails to do DHCP
- William Bulley w...@umich.edu wrote: According to Tim Nelson tnel...@rockbochs.com on Mon, 01/05/09 at 15:19: Make sure you have the appropriate firewall rules on your OPT2 interface to allow traffic to pass. Following the example at the URL shown in my first message I set the OPT2 (ath0) interface to all any or * * * * * * Do I need any more rules than that? You may want some tighter rules eventually but for testing, that is good. However, edit that rule and enable logging. It would be nice to see what traffic is actually being passed. I have a similar rule on the LAN interface to let anything in to the Soekris. All this is behind my m0n0wall router/firewall. So the Soekris is nothing more than an expensive access point (albeit running FreeBSD!) Also, you mentioned I don't have a DHCP server on my local LAN, instead I configured the built-in pfSense DHCP server with three IP addresses to give out. Does that mean you have some static DHCP assignments set but not a general DHCP range open? I am using RFC1918 (net ten) non-routeable addresses behind my m0n0wall which is 10.0.0.1 So the LAN interface on the 4801 is 10.0.0.33 and the other three IP addresses in the DHCP pool are 10.0.0.11, .12, .13 So I have a small pool (range) configured in pfSense on the 4801. Is this the right thing to do? That is, will the DHCP server on the 4801 hand out these pool IP addresses to associated 11g clients? Isn't working at present... :-( Just for gits and shiggles assign that DHCP range a bit larger. One more thing, when bridging a wireless interface to a wired one, make sure the wired interface has a physical ethernet link to something. I've seen it interfere with bridging many times. I have my 4801 LAN interface wired to one of the m0n0wall ethernet jacks, and I have statically configured in pfSense the 10.0.0.33 IP address along with the (static) 10.0.0.1 gateway. I can reach the 4801 (pfSense/FreeBSD) using ssh(8) from other boxes on my local LAN. Is the WAN being used on your box or is the LAN connected to your existing m0n0wall? Help? Regards, web... -- William Bulley Email: w...@umich.edu Have you tried statically assigning the IP address to your wireless device and seeing if it can access the network? That would help pinpoint if the problem is DHCP specific or network/topology based... Tim Nelson Systems/Network Support Rockbochs Inc. (218)727-4332 x105 - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] new to pfSense - Soekris 4801 wireless fails to do DHCP
On Tue, Jan 6, 2009 at 6:37 AM, William Bulley w...@umich.edu wrote: Wireless seems to be working, but the most important thing (IP address) isn't. I should say that I am now associated with an 11g client (both sides agree with this assessment), but I can't get DHCP to hand out a pool IP address: Your client isn't running vista perchance? If it is try this: http://support.microsoft.com/kb/928233 - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] new to pfSense - Soekris 4801 wireless fails to do DHCP
FACEPALM Yes. In fact I posted about this a while back on the list here. Didn't even think to consider it. Tim Nelson Systems/Network Support Rockbochs Inc. (218)727-4332 x105 - Morgan Reed morgan.s.r...@gmail.com wrote: On Tue, Jan 6, 2009 at 6:37 AM, William Bulley w...@umich.edu wrote: Wireless seems to be working, but the most important thing (IP address) isn't. I should say that I am now associated with an 11g client (both sides agree with this assessment), but I can't get DHCP to hand out a pool IP address: Your client isn't running vista perchance? If it is try this: http://support.microsoft.com/kb/928233 - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: [pfSense Support] em0: Watchdog timeout -- resetting
I ran the script in a linux environment, and received No appropriate hardware found for this fixup. I don't know if I mentioned it previously, but the model number of this card is EXPI9404PTL. Thank You, Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC Atlas Networks is an Atlas Accelerator Company -Original Message- From: Paul Mansfield [mailto:it-admin-pfse...@taptu.com] Sent: Monday, January 05, 2009 3:26 AM To: support@pfsense.com Subject: Re: [pfSense Support] em0: Watchdog timeout -- resetting Paul M wrote: linux - there used to be a problem with the e1000 driver when power saving is enabled in the e1000's eeprom. the fix worked, and I applied it by booting a linux rescue disk and ran the eeprom fix program that I got from the e1000 sourceforce website; their wiki seems to have disappeared so I can't find the script, so I've placed a copy here: http://www.zaurus.org.uk/download/scripts/fixeep-82573-dspd.sh if you have the problem on linux you get detected tx unit hang thus: http://sourceforge.net/tracker/index.php?func=detailaid=1463045group_id=42302atid=447449 p.s. I believe that in theory Intel and manufacturers using their e1000 chips were supposed to be turning this off. p.p.s. I don't think there's any equivalent of ethtool -e eth0 for freebsd, so you can't run that script directly on pfsense/freebsd. If there were, you'd get this: # ethtool -e eth5 Offset Values -- -- 0x 00 e0 81 4b 53 b7 30 0b 47 f6 02 10 ff ff ff ff 0x0010 ff ff ff ff 6b 22 91 51 f1 10 8b 10 86 80 df ac 0x0020 21 00 02 20 04 7e 00 00 00 10 d8 00 00 00 00 27 0x0030 c9 6c 50 31 22 07 0b 04 84 09 00 00 00 c0 07 06 - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting
On Mon, Jan 5, 2009 at 2:02 PM, Nathan Eisenberg nat...@atlasnetworks.us wrote: Admittedly, I did not expect to run into hardware/driver issues when I was buying these NICs. :( In fact, that's exactly the reason I went with Intel HW in the first place. Usually that's an accurate assessment. This card is newer than the driver in FreeBSD 7.0 though. And it might not be network driver related at all, might be specific to some other hardware component in relation or combination with that card. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: AW: [pfSense Support] em0: Watchdog timeout -- resetting
Any thoughts on a next step in troubleshooting? I'm running out of ideas. Setting the port speed and duplex has no effect. Thank You, Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC Atlas Networks is an Atlas Accelerator Company -Original Message- From: cbuech...@gmail.com [mailto:cbuech...@gmail.com] On Behalf Of Chris Buechler Sent: Monday, January 05, 2009 5:14 PM To: support@pfsense.com Subject: Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting On Mon, Jan 5, 2009 at 2:02 PM, Nathan Eisenberg nat...@atlasnetworks.us wrote: Admittedly, I did not expect to run into hardware/driver issues when I was buying these NICs. :( In fact, that's exactly the reason I went with Intel HW in the first place. Usually that's an accurate assessment. This card is newer than the driver in FreeBSD 7.0 though. And it might not be network driver related at all, might be specific to some other hardware component in relation or combination with that card. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting
On Mon, Jan 5, 2009 at 8:32 PM, Nathan Eisenberg nat...@atlasnetworks.us wrote: Any thoughts on a next step in troubleshooting? As I suggested earlier in this thread: http://doc.pfsense.org/index.php/Policy_on_FreeBSD_issues Most frequently these issues are driver bugs. We do not have any developers who work on drivers in FreeBSD, and cannot assist with such issues. In these cases, we suggest installing a stock FreeBSD 7.0 release on your hardware, replicating the problem, and reporting it to the appropriate FreeBSD list. This is the only way your problem will be resolved, and even at that will only be resolved in future releases. Alternatively, use different hardware. You may be able to get away with posting questions to freebsd-net using pfSense since it's close to the same as 7.0 release, with no kernel changes related to network drivers. My guess is you would be asked to try 7.1, or RELENG_7, or HEAD to see if the problems persist there. You won't be able to easily do that without running a stock FreeBSD. My guess is this is something specific to this new card that's been addressed with a newer driver, which probably isn't able to be reasonably added to a pfSense install. Hence you may be stuck for the time being. You can try 2.0, which is based on FreeBSD 7.1 and see if that makes any difference. Aside from that, I'm out of suggestions aside from going to the freebsd-net list and hoping the Intel employee who works on the em driver and posts there will offer some suggestions. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
