Re: Vicom Gateway (Macintosh)

Simon Hayes (
Thu, 26 Feb 1998 17:55:39 -0800


Thanks for your feedback. As far as I can see you're saying the same thing
-- that it doesn't work -- just much more technically and more accuratly.
You also seem to offer a solution in farallon netopia. Was that product
specifically written for cu-seeme? So I should look for farallon netopia
for cu-seeme? It's a software product right? Maybe not. Does anybody have
any information about when it might work, given that the problem is in the

But anyway, thanks, I'll check netopia out!

Moving forward, I guess I'm not sure what you first sentence refers to
then? NO there is NO solution, or NO it doesn't work and NO there is NO
solution, or NO, NO, NO, YES NO, it does work, or maybe NO, NO, NO, YES,
NO, and SPAM? Or perhaps, NO, NO, SPAM, NO, NO, EGG AND CHIPS, YES?

Just wondering...


At 5:26 PM -0600 2/26/98, Jeeves wrote:
>Cu-SeeMe DOES NOT work with a proxy server, or address translation/NAT.
>The problem lies in the CU-SeeMe client. The IP of client is imbedded
>within the packet. Proxy/NAT gateways replace the source IP number in the
>packet header (ONLY). There is only one solution to this. I know that
>Farallon/Netopia has actually been able to replace the embedded IP number
>with the NAT/Proxy/Gateway IP number. Of course, this was written
>specfically for CU-SeeMe..
>In addition, the Farallon/Netopia product allows one to direct certain
>ports to a specific IP number on the local LAN. For example.. All
> Ports 7640-7650 packets go to my local IP All
>Ports 23 go to my local IP, and so on.. This way, certain
>functions/ports are directed to specific hosts on the LAN.
>On a side note, I've been able to use ftp clients via my Netopia via NAT
>with no problems. Most routers should have no problems, as long as the
>session is initiated from the local LAN. If it isn't, you need some type
>of port redirection (previously explained) so the gateway knows which IP
>number should be stamped for the local LAN.
>>I'm having the same problem with a similar product: IPnetRouter.
>>Both of these products set up multi-homing on a mac, so that a small
>>network (2 macs) can both be online at the same time using the same IP
>>number/modem etc. They do this by making the PPP connection be a software
>>router and assigning dummy IP numbers to each mac, and routing packets
>>between them (I think, basically, roughly, anyway).
>>The problem also accurs for me with Fetch, or any program which needs to
>>send *to the server* the IP number of the machine it is on. It is simply
>>sending it's dummy assigned number, rather than the gateway or true number,
>>I'm pretty sure. Most reflectors are simply 'not found', while others
>>report an error: "The IP number you are using is not valid, try restarting
>>cu-seeme", which is what leads me to this conclusion. Of course, it never
>>will be valid because it is using a dummy (though not dynamic) IP number
>>from the 198 range, which is reserved for internal networks.
>>Is there any way to solve this in cu-seeme? Perhaps with resedit?
>>Otherwise I think the only way to solve it might be to wait for a version
>>which allows you to specify the ip number cu-seeme sends to the server, or
>>wait for some kind of revision or hack to these multi-homing products. I
>>imagine that these products and this situation (where home or small
>>business user wants more than one pc on line at a time) will become more
>>and more popular. This problem may also extend to other hardware solutions
>>like the "internet station" and other low-cost routers, I'm not sure.
>>Any guidance or information would be most appreciated.
>>At 2:09 PM +0100 2/26/98, Stephane Loquet wrote:
>>>Hello, i'm trying to make CuSeeMe work behind my gateway but it doesn't
>>>I'm very sad.
>>>Is there a solution?
>>>Each time i connect to a reflector all i got is "no response" but i know
>>>the ref is online ;-(
>>Simon Hayes
>>The HyperCard Resource Page
>>The HyperCard Mailing List
>>Never pick a fight with anyone who buys ink by the barrel. -Jeff Ackerman