Thanks for the kind words, guys.
I'm thinking of a "gotcha" though. I need to add awareness of live CD or
normal operations to the function though.
This is all in the set_networking_interfaces_ports() function. Which is
called from several places, like, during boot up and from the rc.initial
screen that runs during normal operations.
I'm thinking of the "oops" potential of a production box, and an errant
key press hits #2 and for some reason or another the user doesn't notice
and doesn't exit the count down.
Boom.
I need to poke around and find the existing LiveCD "Awareness" method
and only enable the feature therein, or if interface mismatch on bootup.
I'm sure its here somewhere.
Matt Hohman wrote:
This would have saved my bacon a couple months ago... Thanks for the
great add.
Thanks,
Matt Hohman
New Heights Church
Sent from my iPhone
On Jul 5, 2009, at 3:28 PM, Tim Nelson wrote:
Tim A. wrote:
Attached a patch against 1.2.3-rc2 adding support for auto
configuring interfaces.
By enabling sshd in the default config.xml on the Live CD installer,
this eliminates many headaches for installs:
No monitor / keyboard / mouse required.
No console cable required.
Install to headless boxes that don't even have console ports!
No more crackin open your box to screw with CF cards and /etc/fstab
nightmares (for being installed to a /dev/device that no longer
exists!).
Just plug-in, turn it on and ssh to the default IP.
This is a link to an ISO built with this patch and my previously
submitted DHCP Server patch.
http://techneck.goldenpath.org/pfsense/pfSense_1.2.3-R2_RELENG_7_2_techneck_patches.iso The
new code will pause to allow interruption for manual assignment. Any
keyboard input will interrupt the procedure.
But if left unattended the code will timeout to begin the automated
process.
The code assigns interfaces in the order they were discovered, LAN,
WAN, OPT1, OPT2, etc...
If only one interface exists and is vlan capable, the code with
create vlan0 tagged VLAN1.
But this will invariably be assigned to WAN as LAN is assigned first
and obviously the parent NIC is discovered before the vlan0.
This is appropriate behavior though given the undesirable situation
of having only 1 NIC, and installation priorities.
It is appropriate because it is more likely that the typical user is
not actually prepared to connect to VLANs and his priority is to
connect to the LAN interface to install and configure his box
~Tim
+1 for you. This looks like a great and much needed feature. Thanks!
--Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Commercial support available - https://portal.pfsense.org
