Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

DHCP issue

Hellou,

I'm a bit confused about below listed log. Can you explain it somebody?

- Why is dhcp packet send from default gw (src: 172.16.5.254:68/udp , dst: 172.16.4.1:67/udp)? I have no helper-address to host 172.16.4.1

- Why can I see src and dst port 67/udp for communication initiated from 172.16.4.1?

situation:

172.16.4.0/23 - vlan75 subnet

172.16.4.1 - dhcp server for vlan75 (linux machine)

172.16.5.254 - default gw for vlan75 (c4500, vrf2)

log from c4500:

011921: Jun 17 14:36:51.074 METDST: IP: s=172.16.5.254 (local), d=172.16.4.1 (Vlan75), len 604, sending full packet
011922: Jun 17 14:36:51.074 METDST:     UDP src=68, dst=67
011923: Jun 17 14:36:51.122 METDST: IP: s=172.16.4.1 (Vlan75), d=172.16.5.254, len 328, input feature
011924: Jun 17 14:36:51.122 METDST:     UDP src=67, dst=67, MCI Check(56), rtype 0, forus FALSE, sendself FALSE, mtu 0
011925: Jun 17 14:36:51.122 METDST: FIBipv4-packet-proc: route packet from Vlan75 src 172.16.4.1 dst 172.16.5.254
011926: Jun 17 14:36:51.122 METDST: FIBfwd-proc: vrf2:172.16.5.254/32 receive entry
011927: Jun 17 14:36:51.122 METDST: FIBipv4-packet-proc: packet routing failed
011928: Jun 17 14:36:51.122 METDST: IP: s=172.16.4.1 (Vlan75), d=172.16.5.254, len 328, rcvd 2
011929: Jun 17 14:36:51.122 METDST:     UDP src=67, dst=67
011930: Jun 17 14:36:51.122 METDST: IP: s=172.16.4.1 (Vlan75), d=172.16.5.254, len 328, stop process pak for forus packet
011931: Jun 17 14:36:51.122 METDST:     UDP src=67, dst=67
011932: Jun 17 14:36:54.142 METDST: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: tronet] [Source: 10.101.174.3] [localport: 22] at 14:36:54 METDST Thu Jun 17 2010
011933: Jun 17 14:36:56.890 METDST: IP: s=172.16.5.254 (local), d=172.16.4.1, len 604, local feature
011934: Jun 17 14:36:56.890 METDST:     UDP src=68, dst=67, Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0
011935: Jun 17 14:36:56.890 METDST: FIBipv4-packet-proc: route packet from (local) src 172.16.5.254 dst 172.16.4.1
011936: Jun 17 14:36:56.890 METDST: FIBipv4-packet-proc: packet routing succeeded
011937: Jun 17 14:36:56.890 METDST: IP: tableid=2, s=172.16.5.254 (local), d=172.16.4.1 (Vlan75), routed via FIB
011938: Jun 17 14:36:56.890 METDST: IP: s=172.16.5.254 (local), d=172.16.4.1 (Vlan75), len 604, sending
011939: Jun 17 14:36:56.890 METDST:     UDP src=68, dst=67
011940: Jun 17 14:36:56.890 METDST: IP: s=172.16.5.254 (local), d=172.16.4.1 (Vlan75), len 604, sending full packet
011941: Jun 17 14:36:56.890 METDST:     UDP src=68, dst=67
011942: Jun 17 14:36:58.950 METDST: IP: s=172.16.5.254 (local), d=172.16.4.1, len 604, local feature
011943: Jun 17 14:36:58.950 METDST:     UDP src=68, dst=67, Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0
011944: Jun 17 14:36:58.950 METDST: FIBipv4-packet-proc: route packet from (local) src 172.16.5.254 dst 172.16.4.1
011945: Jun 17 14:36:58.950 METDST: FIBipv4-packet-proc: packet routing succeeded

Everyone's tags (3)
930
Views
0
Helpful
0
Replies
CreatePlease to create content