[pfSense Support] bug report - missing network device still listed as up

2008-02-14 Thread Paul M
Is this a known bug?

when you remove a network device from a working configured pfsense
1.2rc4 machine, it still boots up, and the web UI interface summary says
the device is up, but has no details (no mac, no IP, etc)

we discovered this when one of our firewall servers died, and problem
was the PCIX twin-port NIC. luckily we are able to do without that NIC,
so we booted the machine without it, using the motherboard's intel twin
giga ports for wan  lan, and intel e100 for sync. so, devices BGE0 and
BGE1 disappeared completely, but the webui still lists interface we
called DMZ as being up!

Paul



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [pfSense Support] bug report - missing network device still listed as up

2008-02-14 Thread Ermal Luçi
Can you please open a ticket for this!

On Thu, Feb 14, 2008 at 5:03 PM, Paul M [EMAIL PROTECTED] wrote:
 Is this a known bug?

  when you remove a network device from a working configured pfsense
  1.2rc4 machine, it still boots up, and the web UI interface summary says
  the device is up, but has no details (no mac, no IP, etc)

  we discovered this when one of our firewall servers died, and problem
  was the PCIX twin-port NIC. luckily we are able to do without that NIC,
  so we booted the machine without it, using the motherboard's intel twin
  giga ports for wan  lan, and intel e100 for sync. so, devices BGE0 and
  BGE1 disappeared completely, but the webui still lists interface we
  called DMZ as being up!

  Paul



  -
  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] FreeRADIUS Package

2008-02-14 Thread Scott Ullrich
On 2/11/08, Dimitri Rodis [EMAIL PROTECTED] wrote:
 The FreeRadius log seems to be located at /var/log/radius.log. According to 
 the current package, there is no logging set up in the package, so you 
 basically have to ssh into pfSense to look at the log.

  What's involved in web enabling the FreeRADIUS log? (looked in the forums, 
 didn't find much.) Does it take something more than just adding a reference 
 to the location of the log in the .xml file somewhere?

I believe the squid package makes usage of this.  Cannot recall 100%
but I do know one of our packages has this implemented that should be
a good guide.

Scott

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [pfSense Support] FreeRADIUS Package

2008-02-14 Thread Dimitri Rodis
I installed Squid (per Martin to see the syntax for some of the XML), but when 
I go to the Package Logs page, I get:

No packages with logging facilities are currently installed.

Also, would you happen to know the options you guys would want me to use with 
diff using cygwin so I can send up my changes so far? (I did the VLAN support 
already, figured I'd send that up now and then follow up with the logging 
stuff).

Thanks,
 
Dimitri Rodis
Integrita Systems LLC 
2990 S Durango Drive 
Las Vegas, NV  89117 
P: 702.896.7207 
F: 702.228.0208 
C: 702.296.4217 
[EMAIL PROTECTED]


-Original Message-
From: Scott Ullrich [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 14, 2008 10:24 AM
To: support@pfsense.com
Subject: Re: [pfSense Support] FreeRADIUS Package

On 2/11/08, Dimitri Rodis [EMAIL PROTECTED] wrote:
 The FreeRadius log seems to be located at /var/log/radius.log. According to 
 the current package, there is no logging set up in the package, so you 
 basically have to ssh into pfSense to look at the log.

  What's involved in web enabling the FreeRADIUS log? (looked in the forums, 
 didn't find much.) Does it take something more than just adding a reference 
 to the location of the log in the .xml file somewhere?

I believe the squid package makes usage of this.  Cannot recall 100%
but I do know one of our packages has this implemented that should be
a good guide.

Scott

-
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]