Quaker Fang writes: > --------- > 1. ARP > Client -> ARP request -> broadcast -> key1 (encrypt) > Peer -> ARP response -> unicast -> key1 (decrypt) > Since only key1 is used, and driver has correct key1, the ARP can works > well without SUNWcry package.
So what happens when the ARP entry on the peer's side needs to be refreshed? The peer will send an ARP request message, broadcasted using key2. The client (which presumably cannot use key2) will then fail to respond. > I have verified this on TP-LINK(ADSL router), and DWL-2100AP(pure WiFi AP). I see. Just the same, what you're seeing is _not_ a dependency on DHCP. It's at best a coincidence. What you're describing is an inability to receive broadcast and multicast messages. As I said before, if you can't receive those messages, neither IPv4 nor IPv6 will function properly, and failures will be both hard to predict and hard to diagnose. Such a configuration cannot be supported in any meaningful way, even if it appears to "work" for some tasks. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
