Re: using common topology through captive portal

The box in question we're talking about being behind the portal is  
actually a webserver. however due to physical location, topology  
restricts it to only be accessible via the physical network governed  
by the captive portal. What i'm trying to do is make this machine part  
of the LAN network, again, while being physically connected to the  
captive portal network.

i hope this clarifys
On Oct 24, 2009, at 6:07 PM, Lee Sharp wrote:

> Mike Nichols wrote:
>> Though i plan to try this out late tonight, i was hoping to get some
>> feedback on it beforehand. i plan to connect two offices through  
>> use of physical connections that
>> must include the captive portal. What i mean is that the only way to
>> connect the two locations is use of infrastructure that is using the
>> captive portal. so i'm thinking of just applying pass rules and  
>> setting
>> static IPs on those machines corresponding to the network outside the
>> captive portal. My question is this, when using the pass through  
>> mac, what
>> is actually happening? is it just routing the traffic around the  
>> portal?
>> Will the packets make it through the portal, through the pass rules  
>> and act
>> as usual (probably without multicast)?
>
> Passthrough MAC is not what you think.  You still need to use a web  
> browser first, but you are "pre authenticated" so you never see the  
> login.  What you want is allowed IP addresses.  And yes, you will  
> need to type in a lot.  However, the "ANY - > IP on remote network"  
> is handy, and they will still need to log in for web surfing.
>
> 			Lee
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>