Re: Jetty and Port 80

Hi David,

I would think that RedHat 7.2's kernel is probably fully modular. I 
simply put the following into my /etc/modules file:

ipt_MASQUERADE
ipt_REJECT
ipt_REDIRECT
ipt_TCPMSS
ip_conntrack

And then you should be able to use your redirect statements, as 
below. Unfortunately it will only work for packets originating from 
outside the server... which makes it a little difficult to test from 
the server. Use iptables, it's the newer of the two commands.

Apologies for speaking Linux on the JBoss list... if you have more 
questions David, please reply offline.

-Neal

On Sunday 07 July 2002 06:55 pm, you wrote:
> I'm obviously a newbie to JBoss/Jetty.  Excuse me if this post
> would be better posted elsewhere but I would greatly appreciate
> any thoughts on the following problem:
>
> I'm running Redhat 7.2 which has IPCHAINS enabled by default. I've
> tried the suggestions for redirecting traffic
> (http://jetty.mortbay.com/jetty/doc/User80.html) as follows:
>
> /sbin/ipchains -I input --proto TCP --dport 80 -j REDIRECT 8080
>
> or:
>
> /sbin/iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT
> --to-port 8080
>
> The IPCHAINS option doesn't work apparently because kernel is NOT
> compiled with CONFIG_IP_MASQUERADE? I don't think I want to
> recompile a kernel...sounds pretty heavy duty.
>
> The IPTABLES option didn't work either, I'm getting the following
> error when running iptables:
>
> [root@xxxx webadmin]# /sbin/iptables -L
> /lib/modules/2.4.9-34/kernel/net/ipv4/netfilter/ip_tables.o:
> init_module: Device or resource busy
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters
> /lib/modules/2.4.9-34/kernel/net/ipv4/netfilter/ip_tables.o: insmod
> /lib/modules/2.4.9-34/kernel/net/ipv4/netfilter/ip_tables.o failed
> /lib/modules/2.4.9-34/kernel/net/ipv4/netfilter/ip_tables.o: insmod
> ip_tables failed
> iptables v1.2.4: can't initialize iptables table `filter': iptables
> who? (do you need to insmod?)
> Perhaps iptables or your kernel needs to be upgraded.
>
> Does anybody have any suggestions to get these options to work or
> another method to have Jetty/JBoss listen on port 80?
>
> It seems to me this is a basic functionality that would be used
> extensively or are people out there using other methods for
> directing their standard port 80 traffic to JBoss/Jetty on port
> 8080?
>
>
> Thanks,
> David Sica
> davidwsica@xxxxxxxxxxx


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
We have stuff for geeks like you.
http://thinkgeek.com/sf