AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080129105833.65d22a77@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<sripal.surendiran@onstor.com>,<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04EC247A4@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 29 Jan 2008 10:58:49 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>
Cc: Maxim Kozlovsky <maxim.kozlovsky@onstor.com>
Subject: Re: Need a help on dhcp issue
Message-ID: <20080129105849.40f579a7@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04EC247A4@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E07BBFDEA@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04EC247A4@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Howdy,

I'll look into it.  It might be fixable in the kernel (by making the
hardware address type something "known" or by configuring or invoking
dh-client a certain way.

The problem is mostly that the dh-client doesn't seem to want to mind
it's own business when it comes to interfaces that we want it ignore.


On Tue, 29 Jan 2008 06:38:39 -0800 "Sripal Surendiran (HCL)"
<sripal.surendiran@onstor.com> wrote:

> Hi Andy,
>  
> I am working on Cougar FTI and facing some issue with running DHCP
> client in the Bobcat linux filer ( I don't have cougar system :-( ). 
> Following error message got displayed, when DHCP client tried to
> contact the DHCP server. 
> webui8:~# /etc/init.d/networking start
> Configuring network interfaces...Internet Systems Consortium DHCP
> Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
> bp0: unknown hardware address type 65535
>  
> Filer hangs after the above message. Even my console is not
> responding. I have to hard reboot the filer. 
> Details of my configuration file
>  
> 1. /etc/network/interfaces
>  
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> auto eth0
> iface eth0 inet dhcp
> #  address 10.25.0.8
> #  netmask 255.255.0.0
> #  gateway 10.25.0.1
> 
> 2. /etc/dhcp3/dhclient.conf
> 
> timeout 60;
> retry 60;
> reboot 10;
> select-timeout 5;
> initial-interval 2;
> 
> 
> interface "eth0" {
>         send dhcp-client-identifier 0:7:34:1:f0:0;
>         send dhcp-lease-time  -1;
>         request subnet-mask, routers,
> domain-name,domain-name-servers, host-name, ntp-servers; require
> host-name; script "/sbin/dhclient-script";
> }
> 
> alias {
>         interface "eth0";
>         fixed-address 172.18.250.250;
>         option subnet-mask 255.255.0.0;
> }
> 
> Whether I am missing something? Any help on this regards will be
> grateful.
> 
> Thanks in advance,
> Sripal.
> 
> ________________________________
> 
> From: Brian DeForest
> Sent: Fri 1/18/2008 6:58 AM
> To: Sudharsan Srinivasan-TLS,Chennai; Sripal Surendiran (HCL)
> Cc: Charissa Willard
> Subject: Cougar FTI
> 
> 
> 
> There have been some discussions about who should own the Cougar FTI
> port/development.  Since this was implemented in R98, after the
> Cougar porting was started, it wasn't really clear whether the
> offshore team or Cougar team should own this.  After some
> discussions, it was decided that the offshore team would be the right
> team to implement this given your familiarity with the R98 work.  
> 
> Currently the Cougar FTI is based on the "old" pre-R98 FTI so the
> porting/development of Cougar (R98-based) FTI is not gating any
> developers.  Also this is not a requirement for the upcoming Cougar
> beta in February.  
> 
> We'll need a schedule for the work.  Tim requested this by Monday if
> possible, however let me know if that's feasible, or an alternative
> date for a schedule.  Andy Sharp is the primary Linux technical
> contact, and feel free to consult with Charissa (or I) as needed also.
> 
> Thanks.
> Brian 
> 
