RE: [pfSense Support] BigPond WAN - bpalogin not starting (Ticket 1047)

2006-08-06 Thread Günter Müller
Hi, (This port relates to problem ticket #1047. I'm unable to add remarks to ticket #1047 -- requires login?!) I'm still having trouble with the BigPond WAN interface. At boot time the /etc/rc.newwanip script is never called at all! Hence BPAlogin is not started automatically. To get the

RE: [pfSense Support] BigPond WAN - bpalogin not starting (Ticket 1047)

2006-08-06 Thread Günter Müller
More information ... I did a "find / ..." of the entire system to check what program/script call /etc/rc.newwanip and found only/usr/local/sbin/check_reload_status. The original logger message in /etc/rc.newwanip claims that it was spawned by DHClient (green line in system log output

RE: [pfSense Support] BigPond WAN - bpalogin not starting (Ticket 1047)

2006-08-06 Thread Günter Müller
I just tested by theory and commented out the "rm -f /tmp/rc.newwanip" line in /etc/rc and reboot pfSense. Success!! BPAlogin was automatically started (by check_reload_status) at boot time. See system logs: Aug 7 01:23:15 dnsmasq[659]: using nameserver 61.9.242.33#53

[pfSense Support] interface deletion breaks pf.conf rules

2006-08-06 Thread Raja Subramanian
I have an RC2 setup with load balancing going on multiple WAN interfaces (WAN, OPT1, 2). I deleted the OPT3 interfacee, but did not delete the corresponding NAT rules associated with OPT3. Upon applying changes, I realised that I had shot myself in the foot! My /tmp/rules.debug had a line

Re: [pfSense Support] interface deletion breaks pf.conf rules

2006-08-06 Thread Scott Ullrich
On 8/6/06, Raja Subramanian [EMAIL PROTECTED] wrote: I have an RC2 setup with load balancing going on multiple WAN interfaces (WAN, OPT1, 2). I deleted the OPT3 interfacee, but did not delete the corresponding NAT rules associated with OPT3. Upon applying changes, I realised that I had shot

RE: [pfSense Support] interface deletion breaks pf.conf rules

2006-08-06 Thread Jason J Ellingson
I would vote for: A removal of an interface would just disable the appropriate NAT and rules. Set the GUI to not allow reactivation of a NAT or rule that is for a non-existing interface... You need to change the interface to an existing one to re-enable it. With the possibility of dynamically

Re: [pfSense Support] interface deletion breaks pf.conf rules

2006-08-06 Thread Scott Ullrich
On 8/6/06, Jason J Ellingson [EMAIL PROTECTED] wrote: I would vote for: A removal of an interface would just disable the appropriate NAT and rules. Set the GUI to not allow reactivation of a NAT or rule that is for a non-existing interface... You need to change the interface to an existing one

[pfSense Support] Warning: stristr(): Empty delimiter. in /etc/inc/pfsense-utils.inc on line 530 after fresh install of RC2

2006-08-06 Thread Adrian Chitoni
Hi all I installed PfSense RC2 on a fresh box on Friday and everything seems to work fine incl. SQUID. But I have the following error under Firewall=NAT=Port Forward: Warning: stristr(): Empty delimiter. in /etc/inc/pfsense-utils.inc on line 530 (ext.: ). Can anyone help?