Re: [pfSense Support] developer build

[Tommaso Di Donato]

Hi!
I manually updated /home/pfsense/pfSense/config.default/config.xml and
my changes are still there, even after every build... I think cvs do
not overewrite this file
Try it if it works also for you...
TomOn 1/13/06, alan walters <[EMAIL PROTECTED]> wrote:
Just wondering how I can stop the cvs from updating before a build.I want to edit the defulat xml file to allow for automated installs ofour firewall configurations.Is this possibleAlan Walters
Aillweecave Company LimitedBallyvaughan Co ClarePh (00353) 65 7077 036Fax (00353) 65 7077 107Lo Call 1890 AILLWEE-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

[pfSense Support] developer build

[alan walters]

Just wondering how I can stop the cvs from updating before a build.
I want to edit the defulat xml file to allow for automated installs of
our firewall configurations.

Is this possible

Alan Walters
Aillweecave Company Limited
Ballyvaughan Co Clare
Ph (00353) 65 7077 036
Fax (00353) 65 7077 107
Lo Call 1890 AILLWEE


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

Re: [pfSense Support] Disabling interface via cron command

[Josh Stompro]

Ah, so embarrassed.  I'm so used to using # comments that i didn't even
think about that open /* tag.
Thanks much.
Josh

Scott Ullrich wrote:

  Try uncommenting /* *OR* to get the LAN interface, use this:

:)

On 1/13/06, Josh Stompro <[EMAIL PROTECTED]> wrote:
  
  
 When I run
 ---
 #!/usr/local/bin/php
 
 ---

 The output is
 # ./landown.php
 Content-type: text/html
 X-Powered-By: PHP/4.4.0

 Interface is
 Direct read of $config is xl1

 For some reason $if is not getting the value assigned to it.
 doing
 echo
convert_friendly_interface_to_real_interface_name("LAN");
 prints out the correct value.

 What am I missing?
 Josh

 Scott Ullrich wrote:
 On 1/12/06, Scott Ullrich <[EMAIL PROTECTED]> wrote:


 This PHP script may be helpful. Simply duplicate it once for up and
down and call them from cron.php. Note that I commented the command
to down the interface out so that there is no foot shooting until
you're absolutely ready.




Woops, here it is:



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




 --
--
Josh Stompro | Office 218.233.3757 EXT-139
LARL Network Coordinator | Mobile 701.371.3857


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

  


-- 
--
Josh Stompro | Office 218.233.3757 EXT-139
LARL Network Coordinator | Mobile 701.371.3857

Re: [pfSense Support] Disabling interface via cron command

[Scott Ullrich]

Try uncommenting /* *OR* to get the LAN interface, use this:

:)

On 1/13/06, Josh Stompro <[EMAIL PROTECTED]> wrote:
>  When I run
>  ---
>  #!/usr/local/bin/php
>  
>  require("functions.inc");
>  require("config.inc");
>
>  /* *OR* to get the LAN interface, use this:
>  $if =
> convert_friendly_interface_to_real_interface_name("LAN");
>
>  /* echo out the interface that we found for this assignment */
>  echo "Interface is $if \n";
>  echo "Direct read of \$config is
> ".$config['interfaces']['lan']['if']."\n";
>
>  ?>
>  ---
>
>  The output is
>  # ./landown.php
>  Content-type: text/html
>  X-Powered-By: PHP/4.4.0
>
>  Interface is
>  Direct read of $config is xl1
>
>  For some reason $if is not getting the value assigned to it.
>  doing
>  echo
> convert_friendly_interface_to_real_interface_name("LAN");
>  prints out the correct value.
>
>  What am I missing?
>  Josh
>
>  Scott Ullrich wrote:
>  On 1/12/06, Scott Ullrich <[EMAIL PROTECTED]> wrote:
>
>
>  This PHP script may be helpful. Simply duplicate it once for up and
> down and call them from cron.php. Note that I commented the command
> to down the interface out so that there is no foot shooting until
> you're absolutely ready.
>
>
>
>
> Woops, here it is:
>
> 
> require("functions.inc");
> require("config.inc");
>
> /* to get the wan interface, use this: */
> $if = get_real_wan_interface();
>
> /* *OR* to get the LAN interface, use this:
> $if =
> convert_friendly_interface_to_real_interface_name("LAN");
>
> /* echo out the interface that we found for this assignment */
> echo $if;
>
>
> /* or you could do something like this:
> exec("/sbin/ifconfig {$if} down");
> */
>
> ?>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>  --
> --
> Josh Stompro | Office 218.233.3757 EXT-139
> LARL Network Coordinator | Mobile 701.371.3857
>

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

Re: [pfSense Support] Disabling interface via cron command

[Josh Stompro]

When I run 
---
#!/usr/local/bin/php


require("functions.inc");
require("config.inc");

/* *OR* to get the LAN interface, use this:
$if = convert_friendly_interface_to_real_interface_name("LAN");

/* echo out the interface that we found for this assignment */
echo "Interface is $if \n";
echo "Direct read of \$config is
".$config['interfaces']['lan']['if']."\n";

?>
---

The output is
# ./landown.php
Content-type: text/html
X-Powered-By: PHP/4.4.0

Interface is
Direct read of $config is xl1

For some reason $if is not getting the value assigned to it.  
doing 
echo convert_friendly_interface_to_real_interface_name("LAN");
prints out the correct value.

What am I missing?
Josh

Scott Ullrich wrote:

  On 1/12/06, Scott Ullrich <[EMAIL PROTECTED]> wrote:
  
  
This PHP script may be helpful.   Simply duplicate it once for up and
down and call them from cron.php.  Note that I commented the command
to down the interface out so that there is no foot shooting until
you're absolutely ready.

  
  

Woops, here it is:



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

  


-- 
--
Josh Stompro | Office 218.233.3757 EXT-139
LARL Network Coordinator | Mobile 701.371.3857

Re: [pfSense Support] Crash Disk problems

[Scott Ullrich]

I've turned my machine off and on many times and have not experienced
this issue.

On 1/13/06, Pedro Paulo de Magalhaes Oliveira Junior
<[EMAIL PROTECTED]> wrote:
> Yes. A UPS is one solution...
>
> But it seems that usual FreeBSD is more robust in this aspect.
>
> -Mensagem original-
> De: Scott Ullrich [mailto:[EMAIL PROTECTED]
> Enviada em: sexta-feira, 13 de janeiro de 2006 15:37
> Para: support@pfsense.com
> Assunto: Re: [pfSense Support] Crash Disk problems
>
> Or a UPS
>
> On 1/13/06, Pedro Paulo de Magalhaes Oliveira Junior
> <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Hey Guys,
> >
> >
> >
> > I'm using latest version of pfsense and experienced two disk crashs with
> two
> > different machines in last days.
> >
> >
> >
> > This usually happens when simulate power failure (something that should
> > happens in a client using pfsense) and when we power on again the loading
> > process stops after the kernel load.
> >
> >
> >
> > Many times it can recover a power failure, but these times no. I don't
> know
> > if it was bad luck or something wrong.
> >
> >
> >
> > One suggestion, we could keep some parts of pfsense in a Read-Only
> partition
> > to keep safe.
> >
> >
> >
> > Regards,
> >
> >
> >
> > Pedro Paulo Jr
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.17/228 - Release Date: 12/1/2006
>
>
>
> -
> 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]

RES: [pfSense Support] Crash Disk problems

[Pedro Paulo de Magalhaes Oliveira Junior]

Yes. A UPS is one solution...

But it seems that usual FreeBSD is more robust in this aspect.

-Mensagem original-
De: Scott Ullrich [mailto:[EMAIL PROTECTED] 
Enviada em: sexta-feira, 13 de janeiro de 2006 15:37
Para: support@pfsense.com
Assunto: Re: [pfSense Support] Crash Disk problems

Or a UPS

On 1/13/06, Pedro Paulo de Magalhaes Oliveira Junior
<[EMAIL PROTECTED]> wrote:
>
>
>
> Hey Guys,
>
>
>
> I'm using latest version of pfsense and experienced two disk crashs with
two
> different machines in last days.
>
>
>
> This usually happens when simulate power failure (something that should
> happens in a client using pfsense) and when we power on again the loading
> process stops after the kernel load.
>
>
>
> Many times it can recover a power failure, but these times no. I don't
know
> if it was bad luck or something wrong.
>
>
>
> One suggestion, we could keep some parts of pfsense in a Read-Only
partition
> to keep safe.
>
>
>
> Regards,
>
>
>
> Pedro Paulo Jr
>
>

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

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.17/228 - Release Date: 12/1/2006
 


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

Re: [pfSense Support] Crash Disk problems

[Scott Ullrich]

Or a UPS

On 1/13/06, Pedro Paulo de Magalhaes Oliveira Junior
<[EMAIL PROTECTED]> wrote:
>
>
>
> Hey Guys,
>
>
>
> I'm using latest version of pfsense and experienced two disk crashs with two
> different machines in last days.
>
>
>
> This usually happens when simulate power failure (something that should
> happens in a client using pfsense) and when we power on again the loading
> process stops after the kernel load.
>
>
>
> Many times it can recover a power failure, but these times no. I don't know
> if it was bad luck or something wrong.
>
>
>
> One suggestion, we could keep some parts of pfsense in a Read-Only partition
> to keep safe.
>
>
>
> Regards,
>
>
>
> Pedro Paulo Jr
>
>

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

Re: [pfSense Support] themes

[Scott Ullrich]

Fine with me if it's okay with Erik.

Scott

On 1/13/06, Rajkumar S <[EMAIL PROTECTED]> wrote:
> Scott Ullrich wrote:
> > For 1.1 the XML approach is a great idea.
> >
> > However for 1.0 we may want to somehow fix the misc small issues so
> > that others can create themes.  Can we get a list of outstanding items
> > that need fixing in the themes section as a ticket in cvstrack?
>
> Attaching the Diff and tar.gz of Orange theme.
>
> As you can see from the diffs, it's mostly clean up of html to remove inline 
> colours and
> changing the javascripts. One immediate fix we can do is to move all 
> javascripts  to
> theme directory and call them from there instead of inline java scripts. This 
> approach is
> easy and will not cause much disruption to existing release plans.
>
> I can do this if this is "blessed".
>
> raj
>
>
> -
> 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] Disabling interface via cron command

[Scott Ullrich]

On 1/13/06, Josh Stompro <[EMAIL PROTECTED]> wrote:
>  Thank you Scott.
>
>  A few questions.  I cannot find cron.php on my pfsense box.
>  I'm running 1.0-PREBETA2-BUG-VALIDATION-EDITION2.
>  I have tried just using crontab -e to edit roots crontab, but cron doesn't
> seem to be using that.

There is no cron.php.  We simply run cron.

>  Do cron events get logged anywhere.  Should I use /etc/crontab.  I am
> guessing that /etc/crontab would get overwritten in an upgrade, so that
> might not be the best choice.

Use /etc/cron ... We do not touch cron during upgrades.

Scott

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

Re: [pfSense Support] Disabling interface via cron command

[Josh Stompro]

Thank you Scott.

A few questions.  I cannot find cron.php on my pfsense box.  
I'm running 1.0-PREBETA2-BUG-VALIDATION-EDITION2.
I have tried just using crontab -e to edit roots crontab, but cron
doesn't seem to be using that.

Do cron events get logged anywhere.  Should I use /etc/crontab.  I am
guessing that /etc/crontab would get overwritten in an upgrade, so that
might not be the best choice.

I added 
#!/usr/local/bin/php
to your script, it runs fine from the command line now, if I can just
figure out how cron is setup on pfsense I should be set.
Josh

Scott Ullrich wrote:

  On 1/12/06, Scott Ullrich <[EMAIL PROTECTED]> wrote:
  
  
This PHP script may be helpful.   Simply duplicate it once for up and
down and call them from cron.php.  Note that I commented the command
to down the interface out so that there is no foot shooting until
you're absolutely ready.

  
  

Woops, here it is:



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

  


-- 
--
Josh Stompro | Office 218.233.3757 EXT-139
LARL Network Coordinator | Mobile 701.371.3857

Re: [pfSense Support] PfSense Beta 1 - HTTP/FTP Download Problem

[Chris Buechler]

Stephen Tsai wrote:


Hi,
 
I am testing pfSense Beta 1 from the LiveCD,  and I found that it has 
problem with download file from web pages.  Here are two URL that you 
can use to test.
 
http://h18023.www1.hp.com/support/files/server/us/download/23836.html 

http://h18023.www1.hp.com/support/files/server/us/locate/20_4763.html#52 





I would assume this is due to the FTP issues in b1.  Have you tested 
beta2-bv3?  This should have that fixed.  
http://pfsense.org/~sullrich/BETA2-BUGVALIDATION3/



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

Re: [pfSense Support] how to configure vlans

[Chris Buechler]

Jure Pečar wrote:


Hi all,

I've defined some vlans on both of my carp'ed pf boxes. Now I'm a bit confused 
because they don't show up in web ui under interfaces. So how do I assign IPs 
to them?

 



after you configure them (which appears to be done properly), in the 
webgui, go to "assign interfaces" and assign them to something.  Then 
you can configure them just like you can your LAN interface. 




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

[pfSense Support] Crash Disk problems

[Pedro Paulo de Magalhaes Oliveira Junior]

Hey Guys,

 

I’m using latest version of pfsense and
experienced two disk crashs with two different machines in last days.

 

This usually happens when simulate power failure
(something that should happens in a client using pfsense) and when we power on
again the loading process stops after the kernel load.

 

Many times it can recover a power failure, but these
times no. I don’t know if it was bad luck or something wrong.

 

One suggestion, we could keep some parts of pfsense
in a Read-Only partition to keep safe.

 

Regards,

 

Pedro Paulo Jr

 

[pfSense Support] how to configure vlans

[Jure Pečar]

Hi all,

I've defined some vlans on both of my carp'ed pf boxes. Now I'm a bit confused 
because they don't show up in web ui under interfaces. So how do I assign IPs 
to them?

pfSense 1.0b1.

# ifconfig
fxp0: flags=8843 mtu 1500
options=8
inet6 fe80::2d0:b7ff:fe10:27a9%fxp0 prefixlen 64 scopeid 0x1
inet 81.24.100.2 netmask 0xff00 broadcast 81.24.100.255
ether 00:d0:b7:10:27:a9
media: Ethernet autoselect (100baseTX )
status: active
fxp1: flags=8943 mtu 1500
options=8
inet6 fe80::290:27ff:fe8c:59d5%fxp1 prefixlen 64 scopeid 0x2
inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255
ether 00:90:27:8c:59:d5
media: Ethernet autoselect (10baseT/UTP)
status: active
fxp2: flags=8843 mtu 1500
options=8
inet6 fe80::2d0:b7ff:fe84:fa9f%fxp2 prefixlen 64 scopeid 0x3
inet 10.0.1.2 netmask 0xff00 broadcast 10.0.1.255
ether 00:d0:b7:84:fa:9f
media: Ethernet autoselect (100baseTX )
status: active
fxp3: flags=8802 mtu 1500
options=8
ether 00:07:e9:94:6c:c5
media: Ethernet autoselect (none)
status: no carrier
plip0: flags=108810 mtu 1500
lo0: flags=8049 mtu 16384
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
pflog0: flags=141 mtu 33208
pfsync0: flags=41 mtu 1348
pfsync: syncdev: fxp2 maxupd: 128
vlan0: flags=8842 mtu 1500
ether 00:90:27:8c:59:d5
media: Ethernet autoselect (10baseT/UTP)
status: active
vlan: 502 parent interface: fxp1
vlan1: flags=8842 mtu 1500
ether 00:d0:b7:10:27:a9
media: Ethernet autoselect (100baseTX )
status: active
vlan: 501 parent interface: fxp0
vlan2: flags=8842 mtu 1500
ether 00:90:27:8c:59:d5
media: Ethernet autoselect (10baseT/UTP)
status: active
vlan: 503 parent interface: fxp1
carp0: flags=49 mtu 1500
inet 10.0.0.1 netmask 0xff00
carp: MASTER vhid 1 advbase 1 advskew 0


-- 

Jure Pečar
http://jure.pecar.org


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