On Fri, 13 Dec 2002, Rob Walker wrote:
> I agree that this is a good idea, using private addresses and such.
> However, if the goal is to force outgoing web surfing to go somewhere
> else, what about masquerading anything going to ports 80 and 443 from
> the local machine. That way you wouldn't h
On Fri, 13 Dec 2002, Rob Walker wrote:
> I agree that this is a good idea, using private addresses and such.
> However, if the goal is to force outgoing web surfing to go somewhere
> else, what about masquerading anything going to ports 80 and 443 from
> the local machine. That way you wouldn't h
On Fri, 13 Dec 2002 21:23, Rob Walker wrote:
> However, if the goal is to force outgoing web surfing to go somewhere
> else, what about masquerading anything going to ports 80 and 443 from
> the local machine. That way you wouldn't have to change the proxy
> settings on whatever browser you were u
On Fri, 13 Dec 2002 21:23, Rob Walker wrote:
> However, if the goal is to force outgoing web surfing to go somewhere
> else, what about masquerading anything going to ports 80 and 443 from
> the local machine. That way you wouldn't have to change the proxy
> settings on whatever browser you were u
On Fri, 2002-12-13 at 02:14, Russell Coker wrote:
> On Fri, 13 Dec 2002 10:56, Walter Hofmann wrote:
> > Yet another idea: If you always use a proxy, then set http_proxy to
> > something like http://123.45.67.89:12345 and use iptables to redirect
> > all outgoing connections to the proxy instead of
On Fri, 2002-12-13 at 02:14, Russell Coker wrote:
> On Fri, 13 Dec 2002 10:56, Walter Hofmann wrote:
> > Yet another idea: If you always use a proxy, then set http_proxy to
> > something like http://123.45.67.89:12345 and use iptables to redirect
> > all outgoing connections to the proxy instead of
On Fri, 13 Dec 2002, Russell Coker wrote:
> Masquerading of packets originating at the local machine was a new feature
> added in 2.4.20, so this only works if you are tracking the latest kernels.
According to my iptables man page (which is older than 2.4.20) the DNAT
target should be valid in
On Fri, 13 Dec 2002, Russell Coker wrote:
> Masquerading of packets originating at the local machine was a new feature
> added in 2.4.20, so this only works if you are tracking the latest kernels.
According to my iptables man page (which is older than 2.4.20) the DNAT
target should be valid in
On Fri, 13 Dec 2002 10:56, Walter Hofmann wrote:
> Yet another idea: If you always use a proxy, then set http_proxy to
> something like http://123.45.67.89:12345 and use iptables to redirect
> all outgoing connections to the proxy instead of 123.45.67.89:12345.
> This allows you to switch proxies o
Yet another idea: If you always use a proxy, then set http_proxy to
something like http://123.45.67.89:12345 and use iptables to redirect
all outgoing connections to the proxy instead of 123.45.67.89:12345.
This allows you to switch proxies on the fly without restarting the
programs that use th
On Fri, 13 Dec 2002 10:56, Walter Hofmann wrote:
> Yet another idea: If you always use a proxy, then set http_proxy to
> something like http://123.45.67.89:12345 and use iptables to redirect
> all outgoing connections to the proxy instead of 123.45.67.89:12345.
> This allows you to switch proxies o
Yet another idea: If you always use a proxy, then set http_proxy to
something like http://123.45.67.89:12345 and use iptables to redirect
all outgoing connections to the proxy instead of 123.45.67.89:12345.
This allows you to switch proxies on the fly without restarting the
programs that use th
On Thu, 12 Dec 2002 16:22, Philipp Haller wrote:
> I am trying to cope with different network environments. I set up various
> schemes in /etc/pcmcia/network.opts. This works fine. For one of those
> schemes I need to set http_proxy. I tried the following (in
> /etc/pcmcia/network.opts): # Extra st
> "Philipp" == Philipp Haller <[EMAIL PROTECTED]> writes:
Philipp> I am trying to cope with different network
Philipp> environments. I set up various schemes in
Philipp> /etc/pcmcia/network.opts. This works fine. For one of
Philipp> those schemes I need to set http_proxy.
The
On Thu, 12 Dec 2002 16:22, Philipp Haller wrote:
> I am trying to cope with different network environments. I set up various
> schemes in /etc/pcmcia/network.opts. This works fine. For one of those
> schemes I need to set http_proxy. I tried the following (in
> /etc/pcmcia/network.opts): # Extra st
Walter Hofmann wrote:
> You could try the following: Change the commands above to write the
> proxy to a file in the /etc directory. Then change the bash init file
> (eg. ~/.bashrc or profile or whatever) to set the proxy variable from
> this file. This will only work for newly started shells.
Th
> "Philipp" == Philipp Haller <[EMAIL PROTECTED]> writes:
Philipp> I am trying to cope with different network
Philipp> environments. I set up various schemes in
Philipp> /etc/pcmcia/network.opts. This works fine. For one of
Philipp> those schemes I need to set http_proxy.
The
Walter Hofmann wrote:
> You could try the following: Change the commands above to write the
> proxy to a file in the /etc directory. Then change the bash init file
> (eg. ~/.bashrc or profile or whatever) to set the proxy variable from
> this file. This will only work for newly started shells.
Th
Philipp Haller schrieb am Thursday, den 12. December 2002:
> Hello list,
>
> I am trying to cope with different network environments. I set up various
> schemes in /etc/pcmcia/network.opts. This works fine. For one of those
> schemes I need to set http_proxy. I tried the following (in
> /etc/p
Philipp Haller schrieb am Thursday, den 12. December 2002:
> Hello list,
>
> I am trying to cope with different network environments. I set up various schemes in
>/etc/pcmcia/network.opts. This works fine. For one of those schemes I need to set
>http_proxy. I tried the following (in /etc/pcmcia
20 matches
Mail list logo
