[ale] [OT] info on x10 browser popups

[Geoffrey]

Kevin Krumwiede wrote:
> Because pop-ups don't really get "pushed" to you.  You load a page that
> contains an instruction to request them, and the browser dutifully complies
> with that instruction.  It's the browser's outgoing request for the pop-up
> page that you want to block, hence the rule in the OUTPUT chain.
> 
> Actually you might better change the rule I suggested to REJECT instead of
> DROP.  If you set it to DROP, the browser (or at least one of its threads)
> might hang a while waiting for a response.  Likewise, if you put the rule in
> the INPUT chain, the request for the page would go out OK, but then the
> browser would wait for a response that would never come.

I still think this is an exercise in futility, as you'd have to make 
sure you covered all X10 ips, which I would think, would prove to be 
difficult.

> 
> Krum
> 
> 
> 
>>-----Original Message-----
>>From: Mike Millson [mailto:mgm at atsga.com]
>>Sent: Monday, April 01, 2002 11:30 AM
>>To: Geoffrey; Atlanta Linux Enthusiasts
>>Subject: RE: [ale] [OT] info on x10 browser popups
>>
>>
>>I'm just curious. Why did you choose to put the rule on the
>>OUTPUT chain? My
>>thought was that the INPUT chain would maybe be a better place for it
>>because it was farther upstream.
>>
>>Mike
>>
> 
> 
> ---
> This message has been sent through the ALE general discussion list.
> See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
> sent to listmaster at ale dot org.
> 
> 
> 


-- 
Until later: Geoffrey		esoteric at 3times25.net

I didn't have to buy my radio from a specific company to listen
to FM, why doesn't that apply to the Internet (anymore...)?


---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.