Thanks for clarification on the acronym. I learned something new ... :-)) -----Original Message----- From: Bill Marquette [mailto:[EMAIL PROTECTED] Sent: Friday, 21 July 2006 12:03 To: support@pfsense.com Subject: Re: [pfSense Support] BigPond WAN - bpalogin not starting
Merge From Current :) --BIll On 7/20/06, Günter Müller <[EMAIL PROTECTED]> wrote: > Bill, > > This issue has been logged as bug ticket #1047 too ... > > I assume MFC means Main Feature Change?! I don't know too much about > PHP code but from the debug messages to syslog I could see that > $$argument was not recognised as valid syntax for variable references. > That is why I logged it as a bug instead of a feature request. Just my 2 cents ... > > Günter. > > -----Original Message----- > From: Bill Marquette [mailto:[EMAIL PROTECTED] > Sent: Friday, 21 July 2006 10:51 > To: support@pfsense.com > Subject: Re: [pfSense Support] BigPond WAN - bpalogin not starting > > Fixed, thanks for the tip! I've requested an MFC on this, so it > should show up in RELENG_1 shortly. > > --Bill > > On 7/20/06, Günter Müller <[EMAIL PROTECTED]> wrote: > > > > > > Reply to myself ... > > > > After further digging around and getting a better understanding of > > the code I now realise that interfaces.inc is not the right file to > > patch as suggested in my previous post below. > > > > This problem is related to Bug Ticket #702, which is flagged as > > fixed, but appears to be still broken or again. > > > > I have followed the instructions in Forum Topic 181 and FAQ 1089 > > http://forum.pfsense.org/index.php?topic=181.0 > > http://faq.pfsense.org/index.php?sid=10900&lang=en&action=artikel&ca > > t= > > 10&id=100&artlang=en > > > > Still no luck! I had a look at /etc/inc/interfaces.inc and can > > confirm that the code to create the bpalogin.conf file and start > > bpalogin is there in the function interfaces_wan_bigpond_configure. > > I found that this function should be called from /etc/rc.newwanip. > > After studing the syslog messages closely, I found that $interface > > is not set correctly in rc.newwanip. An examination of the code has > > revealed > the following bug: > > Lines 40-48: > > if($argument <> "") { > > $curwanip = find_interface_ip($$argument); > > $interface = > > convert_real_interface_to_friendly_interface_name($$argument); > > if($curwanip == "") > > > > $curwanip = get_current_wan_address(); > > > > } else { > > > > $curwanip = get_current_wan_address(); > > $interface = "wan"; > > } > > > > Note the $$argument on lines 41 & 42! Changing these to $argument > > has fixed the problem!! BPAlogin starts up correctly now. > > > > Regards, > > > > Günter. > > > > ________________________________ > > From: Günter Müller [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 20 July 2006 15:27 > > To: support@pfsense.com > > Subject: [pfSense Support] BigPond WAN - bpalogin not starting > > > > > > > > Hi, > > > > I'm a newbie to pfSense (using 1.0rc1) and am trying to get a > > BigPond Cable WAN connection working. If have selected BigPond for > > the WAN connection and entered the username, password, etc. > > correctly. I successfully get a Bigpond DHCP address, but bpalogin does not fire up! > > > > I have checked in /var/etc, /etc and /usr/local/etc, but have not > > found an bpalogin.conf file that should have been created by the > webConfigurator. > > > > Hence I have manually created the file in /var/etc (and > > /usr/local/etc) and started bpalogin from the shell prompt, which > > worked and I now can get out to the 'Net. > > > > A search on of the mail-archives for "BigPond" pointed me to the > > file /etc/inc/interfaces.inc. I managed to debug the file and found > > that the code for Bigpond was incomplete. I added a couple of lines > > and it is working for me now. > > > > Below is a diff of interfaces.inc and interfaces.inc.bak: > > 808,809d807 > > < $curwanip = get_current_wan_address(); > > < > > interfaces_wan_bigpond_configure($curwanip); > > > > I hope this fix can make its way into future releases of pfsense and > > be of help to other BigPond users with the same problem. > > > > Regards, > > > > Günter Müller > > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- 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]
