From: news@packardshome.net   
      
   Hello.   
      
   I've recently set up a vpn for my wireless network to get into my   
   internal network.  I used FreeBSD 4.10 running mpd as the vpn server and   
   am using regular win2k as the custoimary clients.   
      
   Now, my network is split between w2k machines and FreeBSD machines.  A   
   simple method of "talking" to my wife was to use a windows program that   
   handles the classic unix talk and ntalk protocol, it's called chitchat.   
      
   Anyways, while she is connected to the internal network directly,   
   everything works great, I can talk to her and she can talk to me.  The   
   problem arises when she vpn's into the network, talk no longer works.   
   What I've discovered is that chitchat (and others like it, I've tried   
   several) seem to think they still are on the wireless ip address and are   
   using this ip to set up the connection.  So how do I get around this?  I   
   don't have the code to chitchat, I'm hoping that there is a w2k   
   configuration I can use to start chitchat on the vpn based ip.   
      
   Thanks in advance for any help.   
      
   -   
   Mike Packard   
   news@packardshome.net   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)