i think the 712 series needs an rboot server and not bootp. debian has a package (of course!).
> 03:29:20.253733 0.0.0.0.68 > 255.255.255.255.67: xid:0xc1f968d1 ether > 8:0:9:91:ed:a0 [|bootp] > 03:29:20.259366 10.1.1.254.67 > 10.1.1.253.68: xid:0xc1f968d1 > Y:10.1.1.253 S:10.1.1.254 ether 8:0:9:91:ed:a0 sname "ironcurtai"[|bootp] > (DF) > 03:29:22.253780 0.0.0.0.68 > 255.255.255.255.67: xid:0xc1f968d1 secs:2 > ether 8:0:9:91:ed:a0 [|bootp] > 03:29:22.258825 10.1.1.254.67 > 10.1.1.253.68: xid:0xc1f968d1 secs:2 > Y:10.1.1.253 S:10.1.1.254 ether 8:0:9:91:ed:a0 sname "ironcurtai"[|bootp] > (DF) > 03:29:26.253525 0.0.0.0.68 > 255.255.255.255.67: xid:0xc1f968d1 secs:6 > ether 8:0:9:91:ed:a0 [|bootp] > 03:29:26.258648 10.1.1.254.67 > 10.1.1.253.68: xid:0xc1f968d1 secs:6 > Y:10.1.1.253 S:10.1.1.254 ether 8:0:9:91:ed:a0 sname "ironcurtai"[|bootp] > (DF) > > after this, some strange arp lookups appear in the tcpdump output, like > this: > 03:28:48.961476 arp who-has 10.1.1.253 (0:0:0:0:0:70) tell 10.1.1.254 > 03:28:49.961465 arp who-has 10.1.1.253 (0:0:0:0:0:70) tell 10.1.1.254 > > the arp address sometimes change, to 0:0:0:0:0:66, or :64. don't know what > this is, bootpd replies to the requests, but they never reach the 712. i > use the rj45 port, which worked when i bought it from a company. any > ideas? i can send the bootptab config on request (hoping the reply will > get to the recipient ;) ) GREG
