Re: issue with detecting the right interface
The autodiscovery seems to be flawed, in that if it finds a link on
the wrong NIC, it tries to get a DHCP lease and gets stuck. We can
always keep auto discovery in addition to this patch. For example, if
there is a BOOTIF parameter, use this mechanism, otherwise use the
On Sat, Sep 3, 2011 at 3:49 PM, Joseph Gunn <email@example.com> wrote:
> On Thu, 1 Sep 2011 18:56:56 -0700
> Kash <firstname.lastname@example.org> wrote:
>> Here are the changes I made to scripts/live file to support BOOTIF. It
>> doesn't have code to fall back to something else if "IPAPPEND 2" is
> Seems that this patch disables autodiscovery of an interface in favor of a
> machine specific boot parameter...
> Is this an acceptable solution?
>> On Thu, Sep 1, 2011 at 12:21 PM, Daniel Baumann
>> <email@example.com> wrote:
>> > On 09/01/2011 08:43 PM, Kash wrote:
>> >> I edited scripts/live and added code to get the MAC address from
>> >> BOOTIF option of pxelinux, which is what we are using. And then just
>> >> iterating over all the interfaces and using the one that matches the
>> >> MAC address from /proc/cmdline.
>> > nice, would you mind sending a patch?
>> >> This works great for our environment
>> >> but it might not be too portable because not everyone is using
>> >> pxelinux.
>> > that's not so much of a problem; we can always make things 'specific' to one
>> > mode of operation.
>> > --
>> > Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
>> > Email: firstname.lastname@example.org
>> > Internet: http://people.progress-technologies.net/~daniel.baumann/
>> > --
>> > To UNSUBSCRIBE, email to email@example.com
>> > with a subject of "unsubscribe". Trouble? Contact
>> > firstname.lastname@example.org
>> > Archive: 4E5FDB1E.email@example.com">http://lists.debian.org/4E5FDB1E.firstname.lastname@example.org