On Tue, Jul 14, 2009 at 6:08 PM, Tim A.<[email protected]> wrote:
> Chris Buechler wrote:
>
> On Sun, Jul 5, 2009 at 4:23 PM, Tim A.<[email protected]> wrote:
>
>
> Attached a patch against 1.2.3-rc2 adding support for auto configuring
> interfaces.
>
>
> That's definitely a nice feature, though only suitable for addition to
> 2.0, so we'll need a patch for 2.0.  The only thing from your
> description that needs to change is the auto-assignment with one
> interface, 2.0 will let you assign only WAN and treat it basically
> like LAN with a default gateway for appliance purposes, so if there is
> only one interface it needs to only assign WAN.
>
> Thanks!
>
>
> Attached a patch against 2.0 adding support for auto configuring interfaces.
> This patch is done with -rub. So, you wont see the white space but note that
> there's a significant block of the original code that should be indented
> with this.
>
> I reworked it to be less clunky and more POLS. Also, I'm learning more about
> pfsense internals and the auto interface feature automatically turns on sshd
> if it kicks in.
> So, no need to worry about the config file.
>
> I'll update the 1.2 patch later with these improvements as well.
>
> By the way. I've started using git, and its very cool. I created an account
> and added my key to rcs.pfsense.org.
> I tried to push this to the repo but it keeps saying not allowed.
> Are you guys only using that internally?
[snip]

This is great!   Please contact me off-list with your rcs username and
I will get you added to our repo so that you can push this.

[email protected]

Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Commercial support available - https://portal.pfsense.org

Reply via email to