dhcp across a router.
Tim Peiffer <peiffer@unet.umn.edu> Mon, 14 August 1995 20:54 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19596; 14 Aug 95 16:54 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19592; 14 Aug 95 16:53 EDT
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa18095; 14 Aug 95 16:53 EDT
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu; (5.65/1.1.8.2/29Aug94-0956AM) id AA21002; Mon, 14 Aug 1995 16:42:30 -0400
Received: from sol by charcoal (5.x/SMI-SVR4) id AA13899; Mon, 14 Aug 1995 16:41:32 -0400
Received: from mome.unet.umn.edu by sol (5.x/SMI-SVR4) id AA00587; Mon, 14 Aug 1995 16:41:25 -0400
Received: by mome.unet.umn.edu (5.65c) id AA29242; Mon, 14 Aug 1995 15:39:26 -0500
Date: Mon, 14 Aug 1995 15:39:26 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tim Peiffer <peiffer@unet.umn.edu>
Message-Id: <199508142039.AA29242@mome.unet.umn.edu>
To: host-conf@sol.eg.bucknell.edu
Cc: cisco@spot.colorado.edu
Subject: dhcp across a router.
Reply-To: peiffer@unet.umn.edu
I am attempting to provide automatic allocation of DHCP addresses
across a Cisco router using the server from the WIDE project. This
server works well with the server on the local wire, and I am trying
use the Cisco as a relay. We currently use the ip helper to forward
BOOTP requests to our production servers. I seem to be receiving BOOTP
request frames from the BOOTP client, but the server seems to ignore
the request. I would appreciate any pointers that I can get.
I had the dhcp monitor running while etherfind was running on the
server. The etherfind session saw the forwarded packet (agreement
with the sniffer), but the dhcpm did not see the packet. Presumably,
this is why the server never responded. This is odd, because both
the dhcp server, and etherfind make use of SunOS /dev/nit.
Below are representative configurations in /etc/dhcpdb.pool, as well
as a sniffer dump. The Cisco on the interface is set up with my
server as one of the IP helper addresses.
eg:
ip helper-address 128.101.4.18
Tim Peiffer peiffer@unet.umn.edu
University Networking Services
University of Minnesota +1 612 626 7884 desk
130 Lind Hall +1 612 625 0006 problems
207 Church St SE +1 612 626 1002 fax
Minneapolis MN 55455-0134, USA
bootpauto:ht1=500:dht2=850:dfll=3600:
21: :ipad=128.101.101.60:!snmk=255.255.255.0:!brda=128.101.101.255:\
:!rout=128.101.101.254:!nmsv=128.101.101.101:!dnsv=128.101.101.101:\
:!tmsv=128.101.101.101:albp=true:maxl=0xffffffff:tc=bootpauto:
SUMMARY Delta T Destination Source Summary
1293 0.0381 mome [128.101.101... BOOTP Request
BOOTP: ----- BOOTP Header -----
BOOTP:
BOOTP: Boot record type = 1 (Request)
BOOTP: Hardware address type = 1 10Mb Ethernet
BOOTP: Hardware address length = 6 bytes
BOOTP:
BOOTP: Hops = 0
BOOTP: Transaction id = E64D0A00
BOOTP: Elapsed boot time = 40 seconds
BOOTP:
BOOTP: Client self-assigned IP address = [0.0.0.0] (Unknown)
BOOTP: Client hardware address = 0020AF0E7134
BOOTP:
BOOTP: Host name = ""
BOOTP: Boot file name = ""
BOOTP:
BOOTP: Vendor Information tag = 63825363
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP: Pad byte
BOOTP:
ADDR HEX ASCII
0000 08 00 20 19 E1 02 00 00 0C 03 02 37 08 00 45 00 .. ........7..E.
0010 01 48 00 06 00 00 3B 11 13 C5 80 65 65 FE 80 65 .H....;....ee..e
0020 04 12 00 44 00 43 01 34 DD 00 01 01 06 00 E6 4D ...D.C.4.......M
0030 0A 00 00 28 00 00 00 00 00 00 00 00 00 00 00 00 ...(............
0040 00 00 80 65 65 FE 00 20 AF 0E 71 34 00 00 00 00 ...ee.. ..q4....
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0110 00 00 00 00 00 00 63 82 53 63 00 00 00 00 00 00 ......c.Sc......
0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0150 00 00 00 00 00 00 ......
- dhcp across a router. Tim Peiffer
- Re: dhcp across a router. Evan Wetstone