Re: [pfSense Support] WAN DHCP not working ? (org)
Thanks Kevin I think you might be on to something, because when I pluged the WAN cable from the pfSense box into the switch on the old router it got an IP right away. I didn't manage to get an IP from my ISP even after restarting the DSL modem, or changing the MAC, so I just left the old router in front of the box letting it forward everything (DMZ). I would have tested more to see if I could get an IP from my ISP if it wasn't because, after 10 hours of working great, the pfSense box died completly on me, so now I have to start all over. It's a hardware problem not a pfSense problem :/ best regards Ulrik Kevin Wolf sagde: I have cable, so this advice *might* not apply to you, but you can try it anyway. Sometimes the modem won't sync up to a different device (MAC address) unless you reboot it. So try rebooting the DSL modem first if you haven't already. If that doesn't work, try cloning the MAC address from the router to your WAN interface on the pfSense box. Ulrik S. Kofod wrote: I'm finally ready to go live with this box, replacing a really horrible router that has to be reset every now and then (daily). I unplugged the old router and inserted the WAN cable from the DSL modem into the WAN interface on the pfSense box, I then checked the interfaces status page and could se that the link was up and dhcp said up but the IP address was 0.0.0.0 and netmask was 255.0.0.0. I tried to release it at renew a few times but without result. I then tested it in the OPT1 interface with same result. The WAN and OPT1 interfases are both setup to get an IP from DHCP, nothing else changed. I added a print screen of it here if my explanation is a little confusing :) http://www.cybersite.dk/wan_dhcp.GIF Do I need to setup anything except make sure the interface is setup as DHCP like the on old router? Best regards Ulrik PS. I reinstalled the old router and it got the IP like it should. PPS. I'm using pfSense version 0.92 on a 233MHz pentium with 64MB memory and a 2GB HDD. PPPS. Apart from WAN and OPT1 I also have a LAN and WLAN interfase with static IP. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] WAN DHCP not working ?
uhhh broadcoms suck under FreeBSD also, well at least the GigE chipsets, Intels are fine though On Tue, 2005-11-15 at 09:07 +0200, Frimmel, Ivan (ISS South Africa) wrote: I echo that ! I've used 3coms through the many generations on various os's.. They even sucked hard under DOS(3c509) and even worse under Novell .. One might have thought they could get there sh*t together over time .. But alas .. not. Broadcoms and Intels are generally the best in my experience a lot of the old drivers work on current generations of cards .. -Original Message- From: Bill Marquette [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 4:45 AM To: support@pfsense.com Subject: Re: [pfSense Support] WAN DHCP not working ? On 11/14/05, Emanuel A. Gonzalez [EMAIL PROTECTED] wrote: Well, thanks Scott, you were right, the problem isn't the new release, but hardware. I have changed the nic before, but seems that the 3COM 3C905-TX has some issues, cause both nics I tried were this model, and both had the same problem. After I decided to change to an IBM Nic, the problem was solved, now I'm running on 0.93.2. Perhaps is a bug with the driver for this card, cause it was working just fine with any other previous version. Anyway, thanks again for your support and help! Somehow, the fact that this was a 3com card that had issues doesn't surprise me. :-/ 3Com cards have a very bad reputation in the bsd world - while quite popular, they seem to suck pretty bad and the many changes in the card make driver support not so good. --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Itunes Multicast Passthrough
Hello, I have an issue. I want to allow itunes communication to passthrough my gateway. I cannot figure out hoow to do this. I know itunes uses ports 3689/tcp and 5353/udp and multicast. I cannot figure out how to allow these through and still maintain multicast. I can do it if it is just go one machine but the issue is that I am on a massive network and want to share itunes with both internal and external gateway users. How can I do this? Also I want to change the TTL on these packets to be a static number such as 10 as opposed to the standard 2 that is is set to by apple. Please Help, Dwabraxus
Re: [pfSense Support] WAN DHCP not working ?
Lists wrote: uhhh broadcoms suck under FreeBSD also, well at least the GigE chipsets, I would have agreed with anything prior to 6.0, but ever since upgrading my one PowerEdge 2550 with a bge gig card to 6.0, it's been rock solid. On 5.4, it wasn't too horribly bad, but it would drop off for anywhere betweeen a few seconds to a couple minutes a day (watchdog timeout and would come back up on its own). It's been a couple weeks with 0 issues, which never happened under 5.4, so I'm hopeful the problems are solved. *knock on wood* - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] 0.92 WPA Client Issues?
I use WPA and it works great. There must be something else going on with your configuration.Just try WPA and a basic Access Point configuration. On 11/15/05, Brad Gass [EMAIL PROTECTED] wrote: Hello. I've done some digging and have yet to come up with any answers in the archives or forum, so I thought I'd just ask. I've recently installed 0.92 embedded on a WRAP board, 256MB CF card and a Atheros mPCI card (CM9). I'm trying to use this setup as a wireless client device (with WPA-PSK encryption), initially just attempting to associate with an access point right on the bench. I've gone through and set the system up for basic operations and assigned ath0 as my WAN port. Assigned the IP address, SSID, etc - everything works as expected when using no encryption, and 40 bit WEP (I didn't test 128 bit, but assume it works fine). But, no joy at all with WPA. I've tried two access points - a StarOS AP (CM9 card) and a Linksys WRV54G - and specifying the appropriate ciper for both (or auto) and no luck at all with either. I've fiddled with nearly everything I can think of, and nothing results in an association. Changing key times, ciphers, nothing. My last configuration is as follows: pfSense - fresh install of 0.92 embedded, assigned interfaces (sis0 - LAN, ath0 - WAN), assigned my wireless static IP, SSID, enabled WPA and entered the key (32 random ASCII characters). StarOS - fresh install of 2.10.0, assigned IP addresses, WPA-PSK encryption, key rotation of 3600, and the WPA key (32 random ASCII characters). SNR's are a non-issue, 35dB all around. Distance (ACK timing) isn't an issue here either, less than 10 feet on the bench. Is there something stupid I'm missing here, or is there issues with using WPA as a wireless client? More information on request, just let me know what you need. As a secondary question, is there a way to adjust the ACK timing of the radio? Assuming the WPA issues can be worked out, this setup would make a really nice wireless client access device in several places in my network, but link distances could approach 8 miles, so timing would likely need some tuning. Thanks in advance of any and all help! Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [pfSense Support] 0.92 WPA Client Issues?
I have 3 wraps with cm9 and wpa running as Accesspoints without issues. One of them was running with 0.84.6 with an uptime of 35 days without any problems before I updated it today. However, I haven't tried clientmode yet. Holger -Ursprüngliche Nachricht- Von: Scott Ullrich [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 15. November 2005 18:49 An: support@pfsense.com Betreff: Re: [pfSense Support] 0.92 WPA Client Issues? I use WPA and it works great. There must be something else going on with your configuration.Just try WPA and a basic Access Point configuration. On 11/15/05, Brad Gass [EMAIL PROTECTED] wrote: Hello. I've done some digging and have yet to come up with any answers in the archives or forum, so I thought I'd just ask. I've recently installed 0.92 embedded on a WRAP board, 256MB CF card and a Atheros mPCI card (CM9). I'm trying to use this setup as a wireless client device (with WPA-PSK encryption), initially just attempting to associate with an access point right on the bench. I've gone through and set the system up for basic operations and assigned ath0 as my WAN port. Assigned the IP address, SSID, etc - everything works as expected when using no encryption, and 40 bit WEP (I didn't test 128 bit, but assume it works fine). But, no joy at all with WPA. I've tried two access points - a StarOS AP (CM9 card) and a Linksys WRV54G - and specifying the appropriate ciper for both (or auto) and no luck at all with either. I've fiddled with nearly everything I can think of, and nothing results in an association. Changing key times, ciphers, nothing. My last configuration is as follows: pfSense - fresh install of 0.92 embedded, assigned interfaces (sis0 - LAN, ath0 - WAN), assigned my wireless static IP, SSID, enabled WPA and entered the key (32 random ASCII characters). StarOS - fresh install of 2.10.0, assigned IP addresses, WPA-PSK encryption, key rotation of 3600, and the WPA key (32 random ASCII characters). SNR's are a non-issue, 35dB all around. Distance (ACK timing) isn't an issue here either, less than 10 feet on the bench. Is there something stupid I'm missing here, or is there issues with using WPA as a wireless client? More information on request, just let me know what you need. As a secondary question, is there a way to adjust the ACK timing of the radio? Assuming the WPA issues can be worked out, this setup would make a really nice wireless client access device in several places in my network, but link distances could approach 8 miles, so timing would likely need some tuning. Thanks in advance of any and all help! Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Virus checked by G DATA AntiVirusKit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] 0.92 WPA Client Issues?
WPA testing has mostly been done with AP config, as this is what most ppl use. However it worked as a client last time I checked, but something might be broken with it now. I'll retest this ASAP. I just need to find a second client box to test with, I'll report back later. To verify you setup you can do this quite simple, just set it up as a AP and see that you can connect with another client, then just change it to client mode you it should be fine. If it's not then you can try running it manually, from console. If you don't know how to do this then just leave it for now and I'll do some testing. -lsf -Original Message- From: Brad Gass [mailto:[EMAIL PROTECTED] Sent: 15. november 2005 18:38 To: support@pfsense.com Subject: [pfSense Support] 0.92 WPA Client Issues? Hello. I've done some digging and have yet to come up with any answers in the archives or forum, so I thought I'd just ask. I've recently installed 0.92 embedded on a WRAP board, 256MB CF card and a Atheros mPCI card (CM9). I'm trying to use this setup as a wireless client device (with WPA-PSK encryption), initially just attempting to associate with an access point right on the bench. I've gone through and set the system up for basic operations and assigned ath0 as my WAN port. Assigned the IP address, SSID, etc - everything works as expected when using no encryption, and 40 bit WEP (I didn't test 128 bit, but assume it works fine). But, no joy at all with WPA. I've tried two access points - a StarOS AP (CM9 card) and a Linksys WRV54G - and specifying the appropriate ciper for both (or auto) and no luck at all with either. I've fiddled with nearly everything I can think of, and nothing results in an association. Changing key times, ciphers, nothing. My last configuration is as follows: pfSense - fresh install of 0.92 embedded, assigned interfaces (sis0 - LAN, ath0 - WAN), assigned my wireless static IP, SSID, enabled WPA and entered the key (32 random ASCII characters). StarOS - fresh install of 2.10.0, assigned IP addresses, WPA-PSK encryption, key rotation of 3600, and the WPA key (32 random ASCII characters). SNR's are a non-issue, 35dB all around. Distance (ACK timing) isn't an issue here either, less than 10 feet on the bench. Is there something stupid I'm missing here, or is there issues with using WPA as a wireless client? More information on request, just let me know what you need. As a secondary question, is there a way to adjust the ACK timing of the radio? Assuming the WPA issues can be worked out, this setup would make a really nice wireless client access device in several places in my network, but link distances could approach 8 miles, so timing would likely need some tuning. Thanks in advance of any and all help! Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] WAN DHCP not working ?
Lists wrote: yeah, do a tcp thruput test between two boxes and tell me if you get more then 800mbs, then slap intel cards in the box and do it again, been there done that granted its better then it was in 5.x but still nothing close to what it should be for the bandwidth your giving up, let me know cause we tested 6.0 2 months ago and broadcom cards were running 670mbps tops. I didn't say I performance tested it, I said it works reliably thus far. For the purposes of this box, it could be a 100 Mb NIC for all it matters, so I haven't had any need to assess network throughput. This really isn't a great test, since this isn't an isolated network environment, but it's accurate enough that I'll post the numbers. All Dell PowerEdge 2550's, dual P3 1.26 GHz. OS's tested are Windows 2000 Server SP4, with all patches and latest drivers, Windows Server 2003 SP1 with all patches and latest drivers, and FreeBSD 6.0-RELEASE. The 2550's have an onboard Broadcom BCM5700. Between a Windows 2000 and 2003 box, I can get about 450-500 Mb with iperf. Sitting at about 30-40% CPU utilization. Same if I only use one 2550 and connect it to a much bigger box, like a 2850 dual 3.6 GHz with Intel gig cards. From FreeBSD to any other box, I can get about 325-375 Mb. Granted, this FreeBSD box is about 60-70% loaded without running the test, capturing a bunch of packets off the onboard fxp card, and processing them through ntop, amongst a number of other duties. This is a busy box. The Windows boxes are relatively idle. I don't have anything better I can test right now, and I don't want to mess any further with the one production FreeBSD box. Given the numbers, and the load on the FreeBSD box that was not on the Windows boxes, I'd say that's a roughly even comparison. FreeBSD might be a little slower than Windows with the bge cards, but there certainly isn't a substantial difference. The best conclusion I could draw would not be Broadcom on FreeBSD sucks, it'd be Broadcom sucks. I expected much better on Windows, assuming it was a FreeBSD driver issue or a load related issue, but that seems to not be the case. I don't have any Intel PCI-X gig cards I could put in these boxes to compare, but I have no doubt they'd be faster and never disputed that. Intel cards are without a doubt the best choice. The only test I can come up with using all Intel gig cards is *way* different, but I get 900+ Mb through Intel PRO/1000 cards between two PowerEdge 2850's with Server 2003 SP1, dual Xeon 3.6 GHz, only 7-9% CPU utilization at that. I'd expect no different from FreeBSD. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] SNMP / Updating
Hi All, My pfsense devices won't do auto update, are there any known issues with 0.90? Also, the snmp daemon on my 0.90 devices are reporting that their interfaces are all down! I'm using carp, will this be causing it? Thanks, Adam. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Are Sangoma cards supported
Has anyone tried to use any of the Sangoma cards with pfsense? Specifically, I'm interested in trying their T1 card: http://www.sangoma.com/products/p_csu_cards.htm Drivers: ftp://ftp.sangoma.com/FreeBSD/ They might not support FreeBSD 6.x. They list 5.4 in May 2005 Release notes. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] 0.92 WPA Client Issues?
See http://cvstrac.pfsense.com/tktview?tn=684,0 Problem should be resolved now, let me know if you still have issues. -lsf -Original Message- From: Espen Johansen [mailto:[EMAIL PROTECTED] Sent: 15. november 2005 20:28 To: support@pfsense.com Subject: RE: [pfSense Support] 0.92 WPA Client Issues? WPA testing has mostly been done with AP config, as this is what most ppl use. However it worked as a client last time I checked, but something might be broken with it now. I'll retest this ASAP. I just need to find a second client box to test with, I'll report back later. To verify you setup you can do this quite simple, just set it up as a AP and see that you can connect with another client, then just change it to client mode you it should be fine. If it's not then you can try running it manually, from console. If you don't know how to do this then just leave it for now and I'll do some testing. -lsf -Original Message- From: Brad Gass [mailto:[EMAIL PROTECTED] Sent: 15. november 2005 18:38 To: support@pfsense.com Subject: [pfSense Support] 0.92 WPA Client Issues? Hello. I've done some digging and have yet to come up with any answers in the archives or forum, so I thought I'd just ask. I've recently installed 0.92 embedded on a WRAP board, 256MB CF card and a Atheros mPCI card (CM9). I'm trying to use this setup as a wireless client device (with WPA-PSK encryption), initially just attempting to associate with an access point right on the bench. I've gone through and set the system up for basic operations and assigned ath0 as my WAN port. Assigned the IP address, SSID, etc - everything works as expected when using no encryption, and 40 bit WEP (I didn't test 128 bit, but assume it works fine). But, no joy at all with WPA. I've tried two access points - a StarOS AP (CM9 card) and a Linksys WRV54G - and specifying the appropriate ciper for both (or auto) and no luck at all with either. I've fiddled with nearly everything I can think of, and nothing results in an association. Changing key times, ciphers, nothing. My last configuration is as follows: pfSense - fresh install of 0.92 embedded, assigned interfaces (sis0 - LAN, ath0 - WAN), assigned my wireless static IP, SSID, enabled WPA and entered the key (32 random ASCII characters). StarOS - fresh install of 2.10.0, assigned IP addresses, WPA-PSK encryption, key rotation of 3600, and the WPA key (32 random ASCII characters). SNR's are a non-issue, 35dB all around. Distance (ACK timing) isn't an issue here either, less than 10 feet on the bench. Is there something stupid I'm missing here, or is there issues with using WPA as a wireless client? More information on request, just let me know what you need. As a secondary question, is there a way to adjust the ACK timing of the radio? Assuming the WPA issues can be worked out, this setup would make a really nice wireless client access device in several places in my network, but link distances could approach 8 miles, so timing would likely need some tuning. Thanks in advance of any and all help! Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] Are Sangoma cards supported
I'm not sure, I have been trying to find this out myself. If you test it, please let me know. Also if anyone has tried AWM or Junghans with Freebsd6 please let me know. I'm working on implementing asterisk in pfsense, to provide a full SMB all in one system. I'm currently thinking of having a wifi phone connected to pfsense in order to have a nice PBX solution for cordless long-range handsets, as well as a PBX for softphones and normal VoIP phones. -lsf -Original Message- From: Eric W. Bates [mailto:[EMAIL PROTECTED] Sent: 15. november 2005 22:18 To: support@pfsense.com Subject: [pfSense Support] Are Sangoma cards supported Has anyone tried to use any of the Sangoma cards with pfsense? Specifically, I'm interested in trying their T1 card: http://www.sangoma.com/products/p_csu_cards.htm Drivers: ftp://ftp.sangoma.com/FreeBSD/ They might not support FreeBSD 6.x. They list 5.4 in May 2005 Release notes. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] I love my WRAP
Just wanted to report that after many miserable weeks/months of trying to get PfSense to run in any sort of stable/production situation on 3 different PC's, I finally bought a WRAP a few weeks ago and I couldn't be happier! While on any of the three PC's my PfSense box would go down anywhere between 0-8 times a night. Sometimes it would last 2 or 3 days without going down but sometimes it would go into fits where it would go down over and over ever 10 minutes, it would do this 10-12 times in a row before staying up. I was about to give up on the product when I purchased a WRAP, since putting PfSense on the WRAP with basically the same config as before, I have had nothing but sheer joy! I am going on 17 days of straight uptime without so much as a hiccup. I don't know what was up with my three different pieces of hardware and PfSense but I do know that all is well now running 0.88 on the WRAP. So, the purpose of my post is to let you folks know if you are have stability issues in a production environment and really want to get to a better place quickly, BUY A WRAP! No I do not get anything out of this, just trying to save others from going through the pain I did and go straight to the Joy of a stable PfSense solution. Hope this helps some of you. --Todd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [pfSense Support] I love my WRAP
Thanks for the info, but pfSense should run fine on other hardware than WRAPS as well AND it actually DOES run stable on other hardware as well. The WRAP is a very fine device, I agree, but if it comes to pushing larger loads you need something with more power under the hood (a WRAP does 28+ mbit/s with maxed out CPU). Can you provide info about the 3 other systems that caused all these troubles? Maybe someone might find it useful for avoiding some components or replacing some parts to get stability? Holger -Ursprüngliche Nachricht- Von: Mojo Jojo [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 16. November 2005 06:51 An: PfSense Support List Betreff: [pfSense Support] I love my WRAP Just wanted to report that after many miserable weeks/months of trying to get PfSense to run in any sort of stable/production situation on 3 different PC's, I finally bought a WRAP a few weeks ago and I couldn't be happier! While on any of the three PC's my PfSense box would go down anywhere between 0-8 times a night. Sometimes it would last 2 or 3 days without going down but sometimes it would go into fits where it would go down over and over ever 10 minutes, it would do this 10-12 times in a row before staying up. I was about to give up on the product when I purchased a WRAP, since putting PfSense on the WRAP with basically the same config as before, I have had nothing but sheer joy! I am going on 17 days of straight uptime without so much as a hiccup. I don't know what was up with my three different pieces of hardware and PfSense but I do know that all is well now running 0.88 on the WRAP. So, the purpose of my post is to let you folks know if you are have stability issues in a production environment and really want to get to a better place quickly, BUY A WRAP! No I do not get anything out of this, just trying to save others from going through the pain I did and go straight to the Joy of a stable PfSense solution. Hope this helps some of you. --Todd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Virus checked by G DATA AntiVirusKit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
