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.
Ghe Rivero
El vie, 02-09-2005 a las 21:27 +1000, Andrew Pollock escribió:
> On Thu, Sep 01, 2005 at 04:43:49PM +0200, Ghe Rivero wrote:
> > Hi again!
> > I attach the outp of tcpdump as you request me.
> >
> > For more info, my MAc address is: 00:0C:6E:89:E2:FB and it should give
> > me an 172.25.51.90 ip, instead of a 172.25.51.2xx.
> >
>
> Cool, thanks for that. Would you mind doing the same thing again with an
> older version of the dhcp3-client package that wasn't exhibiting this
> problem?
>
> To be honest, I can't see how this is a bug with dhcp3-client, as my
> understanding of the DHCP protocol is the server is responsible for pretty
> much all of the lease allocation process. If the client MAC address matches
> a configured reservation in the DHCP server, it should get that static IP
> address, rather than one from the pool. Any logs from the DHCP server would
> be interesting to see as well.
>
> regards
>
> Andrew
