On Fri, Sep 02, 2005 at 07:11:14PM +0200, Ghe Rivero wrote:
> I have if working now:
> 
> Suse petition:
> 
> 14:34:40.016808 IP (tos 0x0, ttl  64, id 30707, offset 0, flags [none],
> proto: UDP (17), length: 576) 0.0.0.0.bootpc > 255.255.255.255.bootps:
> BOOTP/DHCP, Request from 00:0c:6e:89:e2:fb (oui Unknown), length: 548,
> xid:0x7db0417b, secs:10, flags: [none]
>           Client Ethernet Address: 00:0c:6e:89:e2:fb (oui Unknown)
>           Vendor-rfc1048:
>             DHCP:REQUEST
>             MSZ:548
>             RQ:172.25.51.90
>             LT:4294967295
>             PR:SM+DG+NS+HN+DN+RP+TTL+BR+MD+RD+SR+YD+YS+NTP+LPR+LOG+WNS
> +WDD+WNT+WSC
>             HN:"linux^@"
>             VC:"Linux 2.6.11.4-21.7-smp i686"
>             CID:[ether]00:0c:6e:89:e2:fb
> 
> 
> Debian one:
>       16:35:07.279121 IP (tos 0x10, ttl  64, id 0, offset 0, flags [none],
> proto: UDP (17), length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps:
> BOOTP/DHCP, Request from 00:0c:6e:89:e2:fb (oui Unknown), length: 300,
> xid:0x63125d08, flags: [none]
>           Client Ethernet Address: 00:0c:6e:89:e2:fb (oui Unknown)
>           Vendor-rfc1048:
>             DHCP:REQUEST
>             RQ:172.25.51.201
>             PR:SM+BR+TZ+DG+DN+NS+HN+WNS+WSC
> 
> 
> The main difference was: 
>       CID:[ether]00:0c:6e:89:e2:fb
> 
> 
> And just putting 
>       send dhcp-client-identifier 1:YourHwAddres;     
>       
>       on /etc/dhcp3/dhcpclient.conf resolve everything.
> 
> So, Why RedHat, SuSE, Windows works properly with Cisco and not Debian?
> i don't have access to a RedHat or Suse until monday but i will took a
> look to know how they do it. Anyway, that field should not be used for
> this issues, so i will have a talk with our University Network Man to
> see how he has configured the switches.
> 
>       Thx in advanced for everything and sorry.
> 

Hi again,

So I've had a bit of a read up on the "dhcp-client-identifier" attribute,
and it appears that you can use this as an alternative to client MAC address
to identify clients. It sounds to me like this is how your DHCP server is
configured - it's not actually interested in the MAC address.

If you could mail me a dhclient.conf from a SuSE or RedHat box that works,
I'd be interested to see how you have these configured. I can't imagine that
either distribution is putting something unique and useful in an
out-of-the-box configuration file.

If it's okay with you, I'd like to close this bug, as I don't think it's a
problem with the software's functionality, it's a configuration issue.

regards

Andrew


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to