|
Ugh. I don't have the time to mess around with this and completely redo
my configuration again.
-jeremy
On Mon, 2 Oct 2000, tc lewis wrote:
>
> you cannot specify a different port with direct routing.
>
> what you could do, if you wanted to stick with dr, and use a different
> port, is use horms' ipchains method for solving the arp problem, where you
> can redirect to a different port on that level on the real servers.
>
> -tcl.
>
>
> On Mon, 2 Oct 2000, Jeremy Hansen wrote:
>
> >
> > So I have two fwmark rules setupo. One for port 80 and port 443. What I
> > want to do is redirect the balance to different ports on the internal
> > machines, or real servers.
> >
> > I have regular web on port 4280 and ssl httpd on port 4243 on the real
> > servers.. My rule set looks like this:
> >
> > IP Virtual Server version 0.9.15 (size=8192)
> > Prot LocalAddress:Port Scheduler Flags
> > -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> > FWM 1 wlc
> > -> 10.110.40.1:4280 Route 1 0 0
> > FWM 2 wlc
> > -> 10.110.40.2:4243 Route 1 0 0
> >
> > ipchains:
> > 3 180 - tcp ------ 0xFF 0x00 any 0x1
> > anywhere 64.99.208.3 any -> www
> > 0 0 - tcp ------ 0xFF 0x00 any 0x2
> > anywhere 64.99.208.3 any -> https
> >
> > For some reason it's no redirecting to port 4280 on 10.110.40.1 but rather
> > just tryingf to use port 80 outside -> 80 inside. Why is this? I thought
> > for sure I used to be able to do this without any issue. I tried doing it
> > without FWMARK, just specifically specifying the port and it ignores it.
> >
> > ipvsadm -a -t vip:80 -r real:4280
> >
> > and it just ignore the 4280 and puts real:80.
> >
> > Please let me know how to work around this or what I'm doing wron g. I
> > require that this allows me to do port mapping like this.
> >
> > -jeremy
> >
> > eholes.org * jeremy@xxxxxxxxxx
> > -----------------------------------------
> > eholes have feelings too...
> >
> >
> >
> >
>
>
>
>
eholes.org * jeremy@xxxxxxxxxx
-----------------------------------------
eholes have feelings too...
|
