Hi David,

> One practical challenge is that AFAIK most systems only PXE boot from
> the "WAN" NIC,
Indeed, that's also been the case for all of the PXE enabled boxes that 
I've played with.

> so a bit of cable swapping will be required in order to
> boot from a machine on the internal network. Would be nice to avoid
> that. Maybe make eth0 the "LAN" NIC and eth1 the "WAN" NIC ?????
Well, that has been discussed a few times in the past (years ago, even 
before Shorewall was the firewall of choice). If I remember correctly, 
the discussion always came down to the fact that on the average setup, 
there's one external interface, but often (or usually) more than one 
internal interface (local net, DMZ and so on - I guess these kinds of 
setups are much more common than those that have multiple connections to 
the WAN). Or something like that - eth0 being the external interface is 
simply "natural" to me by now ;-)

For me, this never was a big issue, since I never used PXE to boot into 
a production router, but rather use PXE to boot into a state where I 
could install the lrps (my PXE setup never even had a firewall setup, 
since it was only used on a trusted net and only for as long as it takes 
to scp the required lrps and reboot).

Of course, that doesn't mean one could not create a PXE setup that uses 
eth0 as the internal interface and eth1 as the external interface - it 
would just need to be documented that things differ for that setup 
(otherwise, it might be rather confusing for people who are used to the 
"normal" setup).

Martin

-- 
He will win who knows when to fight and when not to fight.
        Sun Tzu, The Art of War

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to