|
Assuming your switch supports passing 802.1q frames, it should work -
Presumably you can ping back and forth?
You still need to setup IPVS not to match paclets going over your 10.
network - FWM can do that too, or you can do NAT instead of DR and use a
ip ru entry to route it back over the private network. Also need to set
rp_filter to 0 on your private interfaces for most of this to work.
On 10/23/11 5:34 PM, Tomasz Chmielewski wrote:
> Although, something like "vconfig add eth0 105" should get me a
> private VLAN interconnect between them, or?
>
> So:
>
>
> TCP 109.200.13.253:80 lc
> -> 10.0.0.1:80 Route 20 0 2
> -> 10.0.0.2:80 Local 20 0 2
>
>
> And indeed it works correctly, but not always.
> For the host which does not have the VIP assigned, it works every
> second connection - any ideas why?
>
> $ curl 209.15.13.253/testpage.txt
> successful
> dbs2
>
> $ curl 209.15.13.253/testpage.txt
> successful
> dbs1
>
> $ curl 209.15.13.253/testpage.txt
> successful
> dbs2
>
> $ curl 209.15.13.253/testpage.txt
> curl: (7) couldn't connect to host
>
> $ curl 209.15.13.253/testpage.txt
> successful
> dbs2
>
> $ curl 209.15.13.253/testpage.txt
> successful
> dbs1
>
> $ curl 209.15.13.253/testpage.txt
> successful
> dbs2
>
> $ curl 209.15.13.253/testpage.txt
> curl: (7) couldn't connect to host
>
>
> When it doesn't work, tcpdump on eth0 and eth0.105 shows only incoming
> client packets; no replies from the real server.
>
>
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
