home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.sys.cisco
- Path: sparky!uunet!boulder!recnews
- From: Bob Albrightson <albright@lager.cisco.com>
- Subject: Re: BootP question [detailed, longish]
- In-Reply-To: Your message of 6 Jan 93 22:47:35 GMT
- Message-ID: <726430779.12623@news.Colorado.EDU>
- Sender: news
- Date: 7 Jan 93 8:09:08 PST
- Approved: news
- X-Note1: message-id generated by recnews
- X-Note2: mail msgid was <CMM.0.90.2.726422948.albright@lager.cisco.com>
- Lines: 24
-
- I see at least one problem with this packet: (This is the bootp reply
- from the bootp server)
-
- > ! Source IP Address: 132.241.200.10
- > ! Dest. IP Address: 132.241.16.1
- > ! ...
- > ! ...
- > ! Source Port: 67 Bootstrap Protocol Server
- > ! Destination Port: 67 Bootstrap Protocol Server
- > ! ...
- > ! ...
- > ! UDP Data Area:
- > ! PPPPPPI@PPPPPPPP 02 01 06 00 00 00 49 40 00 08 00 00 00 00 00 00
- > ! ^DPPP^DPHP^DPPPPPPP 84 f1 50 0b 84 f1 c8 0a 84 f1 10 01 02 07 01 08
- ^^ ^^ ^^ ^^
- The problem is the server is assigning a subnet 80 address to bob-pc
- (132.241.80.11, actually). This is why bob-pc is not receiving the
- reply. The router will send the packet to its subnet 80 interface.
- Look at the arp cache for 132.241.80.11 on the router. You will find
- it points to 0207:0108:6be4.
-
- Take a look at ther servers bootp config file.
-
- -bob
-