I tried this, and it did not work. The first command, ipvsadm -L -n
doesn't show anything. The second command tells me that -A is not a
valid option.
Does ip forwarding not currently work on Beta4? Or am I doing something
wrong? I really need to get this working as soon as possible.
Thanks,
Michael
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 05, 2001 2:11 AM
To: [EMAIL PROTECTED]
Subject: [Cooker-firewall] port forwarding
Hi there,
actually you cannot see the enrties in the ipchains because this a
separate module compiled in the kernel: ipvsadm that is.
IP explanation:
My test-firewall: 192.168.1.178 and my test-client-web-sever:
192.168.2.254
so, it goes :
[root@mypc /root] ipvsadm -L -n
IP Virtual Server version 1.0.2 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.1.178:80 wlc
-> 192.168.2.254:80 Masq 1 0 0
or
[root@mypc /root] ipvsadm -S -n
-A -t 192.168.1.178:80 -s wlc
-a -t 192.168.1.178:80 -r 192.168.2.254:80 -m -w 1
By the way, we have adde also Prelude and Snort as IDS-es ;)
cheers,
--
Florin http://www.mandrakesoft.com
"John Johnson" <[EMAIL PROTECTED]> writes:
> ok, this helps a little bit more :) Can you post your Ipchains rules
> so we can take a look?
>
> -John
>
>
>
> > Uh, yeah. I'm trying to connect to my webserver and news server
> > from my work computer at my office. I figured I wouldn't need to
> > mention that, but I guess I do.
> >
> > So to be more clear, from OUTSIDE my firewall, I cannot connect to
> > my webserver. Instead of the firewall forwarding the requests to
> > the appropriate server, the firewall's web server is what I'm
> > getting.
> >
> > Thanks,
> >
> > Michael
