Paypal IPN

[Mad Dawg]

Originally Posted by w0ss

The issue is you have is an internal machine(client pc) trying to access an internal server(Hotspot gateway) via the external IP..

Thats partially correct I actually have coova in the APs set for using using the internal wan ip as it is but as soon as you change the
WAN IP Address or FQDN: in rush that seems to override the underlying pf internal WAN ip even though it is still the same
also tried setting the WAN and LAN ips in Rushs PF version both to be internal ips (the WAN one stayed as the 1:1 Nated one)
basically using it as a bridge and that didnt work either

Originally Posted by w0ss

Most NAT implementations will not allow this so not sure there is a real solution. Research NAT hairpinning and you will find a common problem. Most solve it via some type of split DNS. have the address resolve to the internal IP for the internal network and the external IP for the external network.

The other part of my question is really the million dollar one if I go to the trouble of physically moving it behing my core router
and using both nics will it kill the rest of my network

I assume that if I put rush behind my main PF gateway and
use both nics in a wan and lan router type setup it would work fine
but I do not want to have it block all my network at this point just catch the few hotspots I am testing
If I were to move it behind my Gateway router would it only authenticate the hotspot aps that have the coova firmware on them
or will it try to block everything
for now I want the rest of my network traffic to pass through unrestricted

Thanks for hanging in there with me w0ss
I appreciate your assistance