In reply to Rasputin:

(Sorry for not immediately responding.  You deleted my name from the
To:/Cc: list and so I never saw the reply in my mailbox.  And due to my
present networking difficulties, I'm on a text console on my home gateway.
The upshot is that I can't cut and paste anything and (as always) only
read messages when and as they appear in the archives.  (^&  PLEASE never
delete my name from the To:/Cc: lists.)

Anyway, I don't know why you think my ISP would firewall-block DHCP,
especially when *they* were the ones telling me to use DHCP.  I really
doubt that that's the problem.  (Though I also have no way to investigate
it.  (^&)

I ran a tcpdump of part of a dhclient session.  (I started tcpdump, then
ran dhclient; after a couple of ~10-second delays, I killed dhclient.)
Here's the output:

 /~~~ dhclient -=> tcpdump

20:07:55.042762 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0xc456bb39 [|bootp] [tos 0x10]
20:08:03.010606 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0xc456bb39 secs:8 [|bootp] [tos 0x10]
20:08:18.010746 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0xc456bb39 secs:23 [|bootp] [tos 0x10]

 \___ dhclient -=> tcpdump

After killing the process via ^C, the interface was configured as inet
0.0.0.0.  These were the only three events caused by dhclient, it seems.

Any ideas what that might mean?


  ``I probably don't know what I'm talking about.'' --rauch@math.rice.edu