[ previous ] [ next ] [ threads ]
 
 From:  Rolf Sommerhalder <rolf dot sommerhalder at alumni dot ethz dot ch>
 To:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Transparent HTTP Proxy Redirection native in m0n0wall, or as Plugin Module?
 Date:  Sun, 17 Apr 2005 06:58:39 +0200
I need transparent HTTP proxy redirection support behind m0n0wall's nice 
Captive Portal, see
http://m0n0.ch/wall/list/?action=show_msg&actionargs[]=159&actionargs[]=38

So far, I got transproxy-1.5 working nicely in FreeBSD-5.3 (as guest OS 
under VMware on Linux as host OS) as proof-of-concept. Then I started 
integrating transproxy into the source tree of m0n0wall 1.2b7, which 
adds 19 kByte for the tproxy binary and maybe less another kByte to the 
.inc and .php files.

But after reading through the archives, I am currently unsure if this 
"native" integration into m0n0wall is the right approach, or if I should 
better encapsulate it into a module and use Manuel's plugin concept.

Several posters, including Manuel, expressed interest in transparent 
HTTP proxy redirection. Shall I thus continue with the "native" 
integration into m0n0wall (considering the small size of this 
extension), or better change over to the plugin module solution?

In case of "native" is the suitable option, what is the best way to 
contribute code (diffs against rootfs, etc. - I didn't find an answer 
yet in the archives/documentation)?

Thanks,
Rolf