My WAN interface on my 1841 router keeps being restarted by DHCP, my RSP told me to change the lease time to 30 minutes but that doesnt help, they're out of ideas and so am I.
Heres the errors, follwed by sh dhcp lease and sh ver.
*Jan 26 00:10:01.639: %DHCP-5-RESTART: Interface FastEthernet0/0 is being restarted by DHCP
*Jan 26 00:10:03.655: %LINK-5-CHANGED: Interface FastEthernet0/0, changed state to administratively down
*Jan 26 00:10:04.655: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
*Jan 26 00:10:06.671: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
*Jan 26 00:10:07.671: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
*Jan 26 00:10:12.891: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0/0 assigned DHCP address 180.150.11.**, mask 255.255.255.0, hostname Trinculo
Trinculo#sh dhcp lease
Temp IP addr: 180.150.11.** for peer on Interface: FastEthernet0/0
Temp sub net mask: 255.255.255.0
DHCP Lease server: 220.127.116.11, state: 5 Bound
DHCP transaction id: 20E3
Lease: 1800 secs, Renewal: 900 secs, Rebind: 1575 secs
Temp default-gateway addr: 18.104.22.168
Next timer fires after: 00:03:28
Retry count: 0 Client-ID: cisco-0019.06ab.e44c-Fa0/0
Client-ID hex dump: 636973636F2D303031392E303661622E
Cisco IOS Software, 1841 Software (C1841-ADVENTERPRISEK9-M), Version 12.4(24)T3, RELEASE SOFTWARE (fc2)
Ivan has your answer.
According to this your provider is handing out dhcp from an iOS router and then clearing the lease table. Tell your provider to upgrade the code in his device.
Sent from Cisco Technical Support iPad App
I refered this to the Net Ops team at my ISP and they replied with
Our DHCP server is not running on an IOS device.
A server running in the back end is responsible for managing DHCP lease assignments.
Trinculo#sh int fa0/0
FastEthernet0/0 is up, line protocol is up
Hardware is Gt96k FE, address is 0019.06ab.e44c (bia 0019.06ab.e44c)
Internet address is 180.150.11.**/24
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:08, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 3
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 213000 bits/sec, 34 packets/sec
5 minute output rate 36000 bits/sec, 43 packets/sec
967248 packets input, 390973897 bytes
Received 239 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
1232144 packets output, 192504697 bytes, 0 underruns
0 output errors, 0 collisions, 46 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
DHCP config as requested since I am unsure what you mean by Bootpc being permitted.
Im not sure if this is what you're after.
ip dhcp client lease 0 0 30
ip address dhcp
ip flow ingress
ip flow egress
ip nat outside
no ip virtual-reassembly
The bootps(67) is the port that your ISP uses to send out DHCP information and that router recieves on 68(bootpc) on your WAN interface.
ISP renewing your connection lease via a DHCP server which will result in a broadcast from them on ports 67/68. These bootpc/bootps broadcasts from your ISP are used to renew (keep active) your connection and assign dynamic IP's.
I hope you should try with this command; it may help you
permit udp any any eq bootpc
permit udp any any eq bootps