INTL 3:770/1 3:770/3   
   REPLYADDR bp@www.zefox.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  5441c230   
   REPLY:  6364e334   
   PID: SoupGate-Win32 v1.05   
   mm0fmf  wrote:   
   >   
   > That's AP Isolation at work.  It stops Wifi devices communicating with   
   > each. The idea is if you have lots of guest devices connecting, AP   
   > Isolation stops them talking direct to each other and is meant to limit   
   > a rogue guest device ability to do bad things to other guests.   
      
   The problem is solved, and I'm feeling quite stupid about the solution.   
      
   It turns out that setting a reserved DHCP address for the wireless client   
   MAC address un-isolates hosts on WiFi. Ssh and ping work now. Interestingly,   
   setting a static address at the client end, by itself, does not lift the   
   isolation. An old iMac with a static IP connected to the LAN via a WiFi-   
   Ethernet bridge still can't be pinged but connects outbound just fine.   
      
   On reflection it makes perfect sense.....   
      
   I've played with the idea of getting an open-wrt-compatible router in the   
   past, but dropped the idea after finding nothing suitable at the local   
   thrift store. Perhaps I should look again.   
      
   Thanks to everyone for all your help!   
      
   bob prohaska   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 129/305 153/757   
   SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426   
   SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100   
   SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426