Re: [pfSense Support] Wake On LAN - Now Works on 1.2.3 Embedded!
Here is my expierence with wake on lan. The bios and the operating system have to be configured to put the nic into the proper state upon shutdown sucht hat can be awaken by a wol packet. In windows u need to modify the nic in device manager and enable this feature. If the pc looses total power, ie. the power plug pulled from the source and then re-pluged in, wol may not function. Chris On Dec 12, 2009, at 1:21 AM, Tortise tort...@paradise.net.nz wrote: - Original Message - From: Chris Buechler cbuech...@gmail.com To: support@pfsense.com Sent: Tuesday, December 01, 2009 8:57 PM Subject: Re: [pfSense Support] Wake On LAN On Tue, Dec 1, 2009 at 2:53 AM, Tortise tort...@paradise.net.nz wrote: Somehow I cannot get magic packets to awaken any PC on a pfSense LAN. I don't get it. Some motherboard BIOS seem to have WOL and others don't. Even the ones I have that are said to have it cannot be awoken as best I can tell! I have tried an Intel GT1000 with WOL functionality. I can get Boot on LAN to work OK, WOL seems a mystery! It is not clear to me the state that a PC to be awoken in is, I expected that the ATX power supplies would allow the PC to awaken when the right packets are sent however I am wondering if what is needed is a PC in a suspended state - or something else? Just need a WOL-enabled NIC, and to have WOL turned on in the BIOS. If you have an onboard NIC, it should be as simple as enabling it in the BIOS. As long as the machine is plugged in, it'll wake. With add-in NICs you need a WOL cable from the NIC to the motherboard, that can complicate things. - Well I had already done all that and it still didn't work, that was using 1.2.3 RC1 embedded. (3 NIC's, one WAN, two LAN) I now wish I had set up a sniffer to see if magic packets were actually going out I just upgraded to 1.2.3 and thought I'd fire off a few magic packets for funand just as well I was sitting on my chair, the other PC's had fired into life! Only thing that had really changed was the pfSense version! (That means the motherboard BIOS was already enabled for each on board NIC on the couple of Pentium 3000 class boxes I had tried) Curious that I couldn't find any updates about this, anyway others might find it works now? Thank you for the posters on this topic, it seems it may have proved a useful thread for some... In addition to what Chris said above I understand that some NIC's do not need an additional WOL cable for WOL, e.g. Intel 1000GT which are WOL capable and have no cable connection! I hate having to get some more 512M plus CF cards but accept there are excellent reasons for this! Looking forward to checking out some more embedded stuff. I'd suggested the other half give me the pfsense book for Christmas in the hope I might learn some useful stuff about VLAN's etc, even if I don't learn anything I am pleased the other half is contributing to support pfSense! Happy Christmas all! - 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] Wake On LAN - Now Works on 1.2.3 Embedded!
Also if ur nic is a pci or pcie nic the wol cable must be connected to the motherboard header for it to work with wol. Chris On Dec 12, 2009, at 1:21 AM, Tortise tort...@paradise.net.nz wrote: - Original Message - From: Chris Buechler cbuech...@gmail.com To: support@pfsense.com Sent: Tuesday, December 01, 2009 8:57 PM Subject: Re: [pfSense Support] Wake On LAN On Tue, Dec 1, 2009 at 2:53 AM, Tortise tort...@paradise.net.nz wrote: Somehow I cannot get magic packets to awaken any PC on a pfSense LAN. I don't get it. Some motherboard BIOS seem to have WOL and others don't. Even the ones I have that are said to have it cannot be awoken as best I can tell! I have tried an Intel GT1000 with WOL functionality. I can get Boot on LAN to work OK, WOL seems a mystery! It is not clear to me the state that a PC to be awoken in is, I expected that the ATX power supplies would allow the PC to awaken when the right packets are sent however I am wondering if what is needed is a PC in a suspended state - or something else? Just need a WOL-enabled NIC, and to have WOL turned on in the BIOS. If you have an onboard NIC, it should be as simple as enabling it in the BIOS. As long as the machine is plugged in, it'll wake. With add-in NICs you need a WOL cable from the NIC to the motherboard, that can complicate things. - Well I had already done all that and it still didn't work, that was using 1.2.3 RC1 embedded. (3 NIC's, one WAN, two LAN) I now wish I had set up a sniffer to see if magic packets were actually going out I just upgraded to 1.2.3 and thought I'd fire off a few magic packets for funand just as well I was sitting on my chair, the other PC's had fired into life! Only thing that had really changed was the pfSense version! (That means the motherboard BIOS was already enabled for each on board NIC on the couple of Pentium 3000 class boxes I had tried) Curious that I couldn't find any updates about this, anyway others might find it works now? Thank you for the posters on this topic, it seems it may have proved a useful thread for some... In addition to what Chris said above I understand that some NIC's do not need an additional WOL cable for WOL, e.g. Intel 1000GT which are WOL capable and have no cable connection! I hate having to get some more 512M plus CF cards but accept there are excellent reasons for this! Looking forward to checking out some more embedded stuff. I'd suggested the other half give me the pfsense book for Christmas in the hope I might learn some useful stuff about VLAN's etc, even if I don't learn anything I am pleased the other half is contributing to support pfSense! Happy Christmas all! - 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] RC3 to RELEASE - Verify
On Fri, 11 Dec 2009 19:41:32 +0100 Seth Mos seth@xs4all.nl wrote: Chris Buechler schreef: On Fri, Dec 11, 2009 at 11:27 AM, Eugen Leitl eu...@leitl.org wrote: On Fri, Dec 11, 2009 at 09:31:38AM -0600, J.D. Bronson wrote: I just did the upgrade via the web GUI.. it went down w/o a hitch... Same thing here. One thing that was a potential problem in the past was https. Shouldn't be a problem anymore, I upgraded several HTTPS systems. Worked fine for me since forever really. And that's a really long way back. Only one I know of, and was fixed recently, was upgrading to a 2.0 snapshot. Regards, Seth I couldn't upgrade from webui from 1.2.3-RC1 to Release. Just got it when I downloaded the full update and did uploading the tgz. matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style - 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] OpenBGPD status page
On Fri, Dec 11, 2009 at 7:26 PM, Evgeny Yurchenko evg.yu...@rogers.com wrote: I know it is cosmetic but it is easy to fix, please do it. 1) Status has two OpenBGPD Routing sections, one of them should be renamed to Forwarding as it shows fib not rib. 2) OpenBGPD IP section returns error missing argument: valid commands/args: bgp it happens because not there is not bgpctl show ip command, we have to use bgpctl show ip bgp Fix for both issues: --- openbgpd_status.php.20091211.bak 2009-12-10 11:26:10.0 -0500 +++ openbgpd_status.php 2009-12-11 19:20:28.83700 -0500 @@ -140,10 +140,10 @@ defCmdT(OpenBGPD Summary,bgpctl show summary); defCmdT(OpenBGPD Interfaces,bgpctl show interfaces); defCmdT(OpenBGPD Routing,bgpctl show rib); -defCmdT(OpenBGPD Routing,bgpctl show fib); +defCmdT(OpenBGPD Forwarding,bgpctl show fib); defCmdT(OpenBGPD Network,bgpctl show network); defCmdT(OpenBGPD Nexthops,bgpctl show nexthop); -defCmdT(OpenBGPD IP,bgpctl show ip); +defCmdT(OpenBGPD IP,bgpctl show ip bgp); defCmdT(OpenBGPD Neighbors,bgpctl show neighbor); ? Thanks, all of the submissions have been committed. Scott - 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] syslog on 1.2.3
I noticed this when I 1st started using pfSense at 1.2.3-RC, so I am not sure if its a new issue or not. Using the web interface: Status...then system logs then system..and then press CLEAR LOG clears the screen but nothing is ever there when I log back in again later on. As long as you dont clear that log, it will continue to add and work fine...but Its like it ran 'newsyslog' but never kicked syslogd or something. After I press CLEAR LOG, this is what I see: Dec 12 15:42:15 syslogd: kernel boot file is /boot/kernel/kernel and then nothing more... -- J.D. Bronson Information Technology Aurora Health Care - Milwaukee WI Office: 414.978.8282 // Fax: 414.978.3988 - 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] syslog on 1.2.3
On Sat, Dec 12, 2009 at 4:44 PM, J.D. Bronson jd_bron...@sbcglobal.net wrote: I noticed this when I 1st started using pfSense at 1.2.3-RC, so I am not sure if its a new issue or not. Using the web interface: Status...then system logs then system..and then press CLEAR LOG clears the screen but nothing is ever there when I log back in again later on. As long as you dont clear that log, it will continue to add and work fine...but Its like it ran 'newsyslog' but never kicked syslogd or something. After I press CLEAR LOG, this is what I see: Dec 12 15:42:15 syslogd: kernel boot file is /boot/kernel/kernel and then nothing more... You sure there is something that should be logging there that shortly after? Depending on what you're running, there isn't much that logs to system log once the system is up and running. The syslogd message is what is logged after syslog is restarted. After clearing log, and restarting Snort which generates a bunch of logs there, mine immediately show up. - 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] syslog on 1.2.3
well my ISP DHCP lease is only 10mins, even though it never has changed in 2yrs... and as such, there is 'noise' on the system log indicating the renew every 10mins...piles of them. Once I clear the system log, I never see these again.. -- J.D. Bronson Information Technology Aurora Health Care - Milwaukee WI Office: 414.978.8282 // Fax: 414.978.3988 - 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] syslog on 1.2.3
On Sat, Dec 12, 2009 at 6:40 PM, J.D. Bronson jd_bron...@sbcglobal.net wrote: well my ISP DHCP lease is only 10mins, even though it never has changed in 2yrs... and as such, there is 'noise' on the system log indicating the renew every 10mins...piles of them. Once I clear the system log, I never see these again.. I just tried 3 different boxes and they all continue to log just fine. Including when kicking off dhclient. Try to edit and save a firewall rule and apply changes, that will log the filter reload. - 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] syslog on 1.2.3
On 12/12/09 6:09 PM, Chris Buechler wrote: I just tried 3 different boxes and they all continue to log just fine. Including when kicking off dhclient. Try to edit and save a firewall rule and apply changes, that will log the filter reload. Ok at 18:14 I edited a rule..saved it and then applied the changes. .and then see this in system log: Dec 12 18:14:27 check_reload_status: reloading filter Dec 12 17:35:12 syslogd: kernel boot file is /boot/kernel/kernel Dec 12 17:35:12 syslogd: exiting on signal 15 Dec 12 17:33:46 sshd[6834]: Accepted publickey for XX Dec 12 15:42:15 syslogd: kernel boot file is /boot/kernel/kernel but nothing more. Not even the dhclient messages. My install is straight forward and I didnt edit/hack anything. What am I missing? as long as I never clear the 'system-log' or firewall log - it logs everything it should and shows it accurately. -- J.D. Bronson Information Technology Aurora Health Care - Milwaukee WI Office: 414.978.8282 // Fax: 414.978.3988 - 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] syslog on 1.2.3
On Sat, Dec 12, 2009 at 7:19 PM, J.D. Bronson jd_bron...@sbcglobal.net wrote: On 12/12/09 6:09 PM, Chris Buechler wrote: I just tried 3 different boxes and they all continue to log just fine. Including when kicking off dhclient. Try to edit and save a firewall rule and apply changes, that will log the filter reload. Ok at 18:14 I edited a rule..saved it and then applied the changes. .and then see this in system log: Dec 12 18:14:27 check_reload_status: reloading filter Dec 12 17:35:12 syslogd: kernel boot file is /boot/kernel/kernel Dec 12 17:35:12 syslogd: exiting on signal 15 Dec 12 17:33:46 sshd[6834]: Accepted publickey for XX Dec 12 15:42:15 syslogd: kernel boot file is /boot/kernel/kernel but nothing more. Not even the dhclient messages. My install is straight forward and I didnt edit/hack anything. What am I missing? I suspect it's doing as intended, your DHCP lease may be longer than you think, or than it previously was. Logging from dhclient is no different than anything else that you are seeing logs from. Release and renew from Status-Interfaces will force it to renew. - 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] syslog on 1.2.3
On 12/12/09 6:21 PM, Chris Buechler wrote: but nothing more. Not even the dhclient messages. My install is straight forward and I didnt edit/hack anything. What am I missing? I suspect it's doing as intended, your DHCP lease may be longer than you think, or than it previously was. Logging from dhclient is no different than anything else that you are seeing logs from. Release and renew from Status-Interfaces will force it to renew. Its even shorter than I had thought: option dhcp-renewal-time 300; option dhcp-rebinding-time 525; renew 6 2009/12/12 23:47:46; rebind 6 2009/12/12 23:51:31; expire 6 2009/12/12 23:52:46; 5 mins. Never logged in system once I clear it..but still logged in /var/db as expected. I cant believe this is a bug but its annoying that it stops logging once cleared and even more annoying its not duplicated in your tests. I guess I give up... I just need to stop clearing any logs and it will then keep displaying the last 50 events and thats ok I guess. -- J.D. Bronson Information Technology Aurora Health Care - Milwaukee WI Office: 414.978.8282 // Fax: 414.978.3988 - 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] Captive Portal RADIUS authentication - Authentication error - Username and/or password invalid
The external IP of the radius server has to be added to the radius servers client list or else it will reject authentication requests. Mike From: Tancinco, Jon Sent: Wednesday, December 09, 2009 5:43 PM To: support@pfsense.com Subject: RE: [pfSense Support] Captive Portal RADIUS authentication - Authentication error - Username and/or password invalid Secret key works under m0n0wall and the same key is used in pfSense. Not sure what you mean about the IP of the NAS. Thanks for your help! Jon From: Michael Vinocur [mailto:michaelvino...@hotmail.com] Sent: Wednesday, December 09, 2009 2:28 PM To: support@pfsense.com Subject: Re: [pfSense Support] Captive Portal RADIUS authentication - Authentication error - Username and/or password invalid Could be the secret key or check is you added the IP of the NAS. Mike From: Tancinco, Jon Sent: Wednesday, December 09, 2009 11:37 AM To: support@pfsense.com Subject: [pfSense Support] Captive Portal RADIUS authentication - Authentication error - Username and/or password invalid Same error on Versions 1.2.2 and 1.2.3 Using the pfSense Captive Portal. I am getting the Authentication error - Username and/or password invalid. message when trying to authenticate. The password is correctly submitted, but get the error everytime. RADIUS server reports incorrect password. Using m0n0wall, Captive Portal and RADIUS authentication works with no problems using the same username, password and RADIUS server. Any help would be appreciated. Jon
Re: [pfSense Support] potential pfsense hardware
Just stumbled over this: MSI Industrial WindBOXII http://www.logicsupply.com/products/ms_9a25 Not cheap - but it's got everything in a nice pre-packaged box. Regards, -Jeppe - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
