• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Update APBS port mappings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Update APBS port mappings


  • Subject: Re: Update APBS port mappings
  • From: Mark Thomas <email@hidden>
  • Date: Thu, 02 Oct 2003 10:49:03 +0100
  • Organization: Coderus Ltd

Are we saying that the APBS NAT software doesn't allow this ???.

Thanks
Mark.

>
> I got a little confused. You've created a mapping from the public ip
> address of the NAT box and port 80 to the private IP address of a box
> behind the nat on port 80? You're trying to test it by connecting to
> the public IP address port 80 from behind the NAT? Most NATs don't
> properly implement this. If you try connecting from any address not
> behind the NAT, it will probably work. This makes it a nightmare to try
> and get communication working between two devices behind the same NAT,
> especially in the case of double NAT where one device may be behind one
> NAT and another device behind two NATS.
>
> -josh
>
> On Oct 1, 2003, at 3:47 PM, Mark Thomas wrote:
>
>> Hi,
>>
>>> The primary reason to create manual port mappings is that
>>> you have some kind of server behind your NAT box that you
>>> would like to receive unsolicited traffic for a known Apparent
>>> endpoint on the NAT box.
>>
>> That's sounds what I'm trying to do.
>>
>>>
>>> Once your server has a way to communicate with a specific client,
>>> it can create any port mappings it wants just by sending
>>> packets with the corresponding address and port information
>>> in the IP and TCP/UDP header.
>>>
>>> When you say the "server then hands off to another port",
>>> what exactly is going on? How does the client find out
>>> about this other port? All you should need to do to create
>>> a port mapping is initiate contact with the client from
>>> this other port on your server behind the NAT box.
>>>
>> I also tried this with the apache web server , as I pointed port 80
>> of the
>> APBS to my machine port 80. If used localhost address, then all worked
>> fine,
>> but if I tried using the APBS WAN API address, then the browser just
>> sits
>> there, and gets a connection error after a while. I have checked to
>> see if
>> my ISP blocks port 80, which they don't, so I guess this should have
>> worked.
>>
>> On the programmatic side I'm doing the usual listen, then accept
>> calls,
>> The server works fine, if I remove the NAT box, and make my machine
>> take the
>> WAN connection.
>>
>> Any ideas, why then this doesn't work ???.
>>
>> Thanks
>> Mark.
>> _______________________________________________
>> macnetworkprog mailing list | email@hidden
>> Help/Unsubscribe/Archives:
>> http://www.lists.apple.com/mailman/listinfo/macnetworkprog
>> Do not post admin requests to the list. They will be ignored.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Update APBS port mappings
      • From: Joshua Graessley <email@hidden>
References: 
 >Re: Update APBS port mappings (From: Joshua Graessley <email@hidden>)

  • Prev by Date: Re: SSLWrite and SSLRead mutually exclusive?
  • Next by Date: Re: Update APBS port mappings
  • Previous by thread: Re: Update APBS port mappings
  • Next by thread: Re: Update APBS port mappings
  • Index(es):
    • Date
    • Thread