Re: [pfSense Support] Re: NanoBSD on WRAP

2009-12-15 Thread Rainer Duffner
Ugo Bellavance schrieb: On 2009-12-14 22:17, Chris Buechler wrote: On Mon, Dec 14, 2009 at 10:53 AM, Scott Ullrichsullr...@gmail.com wrote: On Sun, Dec 13, 2009 at 7:49 PM, Ugo Bellavanceu...@lubik.ca wrote: Hi, http://doc.pfsense.org/index.php/NanoBSD_on_WRAP Has someone done the first

Re: [pfSense Support] Re: NanoBSD on WRAP

2009-12-15 Thread Jim Pingle
On 12/15/2009 6:31 AM, Rainer Duffner wrote: Ugo Bellavance schrieb: I like this answer, and there are really 2 facts that are highlighted here: - Users will always complain - The better your product and product history, the less users will read the warnings. PfSense has always had a good

Re: [pfSense Support] Re: NanoBSD on WRAP

2009-12-15 Thread Rainer Duffner
Jim Pingle schrieb: Which model ALIX do you have? alix2d1 according to the receipt. It says on the page that there are some excluded models, usually it's the ones with VGA that require a different BIOS. Did the image not boot at all? Or what did it do? IIRC, the ALIX basically said

Re: [pfSense Support] potential pfsense hardware

2009-12-15 Thread Paul Mansfield
On 14/12/09 23:47, Jeppe Øland wrote: As for the PCIe wireless card: it's a MSI brand card, using a Ralink NIC. (MS-6894, Ralink chip: RTL8187SE) I guess thats a RealTek wireless card ... probably next to useless for pfSense or? realtek != ralink yup, that's a realtek since reading some

Re: [pfSense Support] potential pfsense hardware

2009-12-15 Thread Seth Mos
Paul Mansfield schreef: On 14/12/09 23:47, Jeppe Øland wrote: As for the PCIe wireless card: it's a MSI brand card, using a Ralink NIC. (MS-6894, Ralink chip: RTL8187SE) I guess thats a RealTek wireless card ... probably next to useless for pfSense or? realtek != ralink I've previously have

Re: [pfSense Support] potential pfsense hardware

2009-12-15 Thread Paul Mansfield
On 15/12/09 14:35, Seth Mos wrote: Paul Mansfield schreef: On 14/12/09 23:47, Jeppe Øland wrote: As for the PCIe wireless card: it's a MSI brand card, using a Ralink NIC. (MS-6894, Ralink chip: RTL8187SE) I guess thats a RealTek wireless card ... probably next to useless for pfSense or?

RE: [pfSense Support] Captive Portal RADIUS authentication - Authentication error - Username and/or password invalid

2009-12-15 Thread Tancinco, Jon
Hi Mike. The authentication requests go through to the Radius server...and we get a bad password error. It's weird. All the same settings work under m0n0wall. Same IPs, same radius server. I'm not sure how different pfSense is compared to the m0n0wall app. The Captive Portal setup

Re: [pfSense Support] Captive Portal RADIUS authentication - Authentication error - Username and/or password invalid

2009-12-15 Thread Michael Vinocur
I see. Well the the only other thing I can think of is the password type i.e. m5,chap, etc must be different between the moonwall and pfsesnse boxes. Mike From: Tancinco, Jon Sent: Tuesday, December 15, 2009 11:51 AM To: support@pfsense.com Subject: RE: [pfSense Support] Captive Portal

[pfSense Support] Windows Network functionality/auto-sensing lacking.

2009-12-15 Thread li...@mgreg.com
Hi All, Got a small issue here. Basically, I replaced a DLINK router with a base pfSense setup. Now, although all of my machines can ping one another, they don't seem to be auto-sensing one another -- no machines show up in Network Neighborhood, etc. Are there any special items or special

Re: [pfSense Support] Windows Network functionality/auto-sensing lacking.

2009-12-15 Thread Seth Mos
Op 15 dec 2009, om 22:03 heeft li...@mgreg.com het volgende geschreven: Got a small issue here. Basically, I replaced a DLINK router with a base pfSense setup. Now, although all of my machines can ping one another, they don't seem to be auto-sensing one another -- no machines show up in

Re: [pfSense Support] Windows Network functionality/auto-sensing lacking.

2009-12-15 Thread Keenan Tims
Got a small issue here. Basically, I replaced a DLINK router with a base pfSense setup. Now, although all of my machines can ping one another, they don't seem to be auto-sensing one another -- no machines show up in Network Neighborhood, etc. Are there any special items or special

RE: [pfSense Support] Re: NanoBSD on WRAP

2009-12-15 Thread Simon Thomson
-Original Message- From: Jim Pingle [mailto:li...@pingle.org] Sent: Tuesday, 15 December 2009 9:07 PM To: support@pfsense.com Subject: Re: [pfSense Support] Re: NanoBSD on WRAP On 12/15/2009 6:31 AM, Rainer Duffner wrote: Ugo Bellavance schrieb: I like this answer, and there are

Re: [pfSense Support] Re: NanoBSD on WRAP

2009-12-15 Thread Duncan Hall
Simon Thomson wrote: -Original Message- From: Jim Pingle [mailto:li...@pingle.org] Sent: Tuesday, 15 December 2009 9:07 PM To: support@pfsense.com Subject: Re: [pfSense Support] Re: NanoBSD on WRAP On 12/15/2009 6:31 AM, Rainer Duffner wrote: Ugo Bellavance schrieb: I like

RE: [pfSense Support] Re: NanoBSD on WRAP

2009-12-15 Thread Simon Thomson
-Original Message- From: Duncan Hall [mailto:dun...@viator.com] Sent: Wednesday, 16 December 2009 8:47 AM To: support@pfsense.com Subject: Re: [pfSense Support] Re: NanoBSD on WRAP Simon Thomson wrote: -Original Message- From: Jim Pingle [mailto:li...@pingle.org] Sent:

[pfSense Support] WAN2 Setting Problem In Failover

2009-12-15 Thread Abel Wang
Dear All, I have set my leased line(static IP) in the WAN interface,and it is working fine. Now I need to do a failover to it,however,the back up line is ADSL, I have to use a router to do the PPPoe dial up,and connected the router(I have set it IP:192.168.1.1) to the soekris ETH2. and in

RE: [pfSense Support] WAN2 Setting Problem In Failover

2009-12-15 Thread Tim Dickson
and in the WAN2 interface,I set Type to static,IP address to 192.168.1.254/32,Gateway to 192.168.1.1. I believe you want it to be 192.168.1.254/24 Right now the gateway and static IP are in two different subnets. -tim - To