What does your real server see? Only include packets related to your LVS traffic, and make sure you display it as IPs and numeric ports (tcpdump -nn).
David On Mar 20, 2012, at 9:11 AM, Reet Vyas wrote: > win 1002, options [nop,nop,TS val 622858179 ecr 19927684], length 480 > 17:58:53.331753 IP ABTS-KK-static-133.233.166. >> >> 122.airtelbroadband.in.55541 > server13000.teamviewer.com.https: Flags >> [P.], seq 1346:1390, ack 283, win 1002, options [nop,nop,TS val 622858189 >> ecr 50106], length 44 >> 17:58:53.359331 IP server12811.teamviewer.com.https > >> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423: Flags [P.], seq >> 820:868, ack 240, win 256, options [nop,nop,TS val 1649727 ecr 622858022], >> length 48 >> 17:58:53.359433 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423 >>> server12811.teamviewer.com.https: Flags [.], ack 868, win 245, options >> [nop,nop,TS val 622858217 ecr 1649727], length 0 >> 17:58:53.378801 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.55541 >>> server13000.teamviewer.com.https: Flags [P.], seq 1390:1434, ack 283, win >> 1002, options [nop,nop,TS val 622858236 ecr 50106], length 44 >> 17:58:53.388839 IP server13000.teamviewer.com.https > >> ABTS-KK-static-133.233.166.122.airtelbroadband.in.55541: Flags [.], ack >> 1390, win 260, options [nop,nop,TS val 50115 ecr 622858142], length 0 >> 17:58:53.390759 IP 14.140.226.234.STATIC-Pune-vsnl.net.in.47901 > >> ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh: Flags [.], ack >> 46880, win 501, options [nop,nop,TS val 19927754 ecr 622858135], length 0 >> 17:58:53.390788 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh > >> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [.], seq 48128:49576, >> ack 49, win 1002, options [nop,nop,TS val 622858248 ecr 19927754], length >> 1448 >> 17:58:53.390794 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh > >> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [P.], seq 49576:49600, >> ack 49, win 1002, options [nop,nop,TS val 622858248 ecr 19927754], length 24 >> 17:58:53.396228 IP server12811.teamviewer.com.https > >> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423: Flags [.], ack >> 344, win 256, options [nop,nop,TS val 1649731 ecr 622858088], length 0 >> 17:58:53.417494 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423 >>> server12811.teamviewer.com.https: Flags [P.], seq 344:399, ack 868, win >> 245, options [nop,nop,TS val 622858275 ecr 1649731], length 55 >> 17:58:53.425619 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.55541 >>> server13000.teamviewer.com.https: Flags [P.], seq 1434:1478, ack 283, win >> 1002, options [nop,nop,TS val 622858283 ecr 50115], length 44 >> 17:58:53.429508 IP server12811.teamviewer.com.https > >> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423: Flags [P.], seq >> 868:916, ack 344, win 256, options [nop,nop,TS val 1649734 ecr 622858088], >> length 48 >> 17:58:53.429604 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423 >>> server12811.teamviewer.com.https: Flags [.], ack 916, win 245, options >> [nop,nop,TS val 622858287 ecr 1649734], length 0 >> 17:58:53.432428 IP 14.140.226.234.STATIC-Pune-vsnl.net.in.47901 > >> ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh: Flags [.], ack >> 48128, win 501, options [nop,nop,TS val 19927796 ecr 622858178], length 0 >> 17:58:53.432458 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh > >> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [.], seq 49600:51048, >> ack 49, win 1002, options [nop,nop,TS val 622858290 ecr 19927796], length >> 1448 >> 17:58:53.432463 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh > >> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [P.], seq 51048:51504, >> ack 49, win 1002, options [nop,nop,TS val 622858290 ecr 19927796], length >> 456 >> 17:58:53.470912 IP server12811.teamviewer.com.https > >> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423: Flags [P.], seq >> 916:963, ack 344, win 256, options [nop,nop,TS val 1649738 ecr 622858088], >> length 47 >> 17:58:53.471013 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423 >>> server12811.teamviewer.com.https: Flags [.], ack 963, win 245, options >> [nop,nop,TS val 622858329 ecr 1649738], length 0 >> 17:58:53.472207 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.55541 >>> server13000.teamviewer.com.https: Flags [P.], seq 1478:1522, ack 283, win >> 1002, options [nop,nop,TS val 622858330 ecr 50115], length 44 >> 17:58:53.480516 IP 14.140.226.234.STATIC-Pune-vsnl.net.in.47901 > >> ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh: Flags [P.], seq >> 49:97, ack 48128, win 501, options [nop,nop,TS val 19927843 ecr 622858178], >> length 48 >> 17:58:53.480573 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh > >> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [.], ack 97, win 1002, >> options [nop,nop,TS val 622858338 ecr 19927843], length 0 >> >> >> >> >> >> >> >> >> and eth1 >> >> 17:59:38.329207 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >> seq 235:282, ack 371, win 65535, length 47 >> 17:59:38.481005 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [.], >> ack 282, win 64078, length 0 >> 17:59:38.705836 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 371:416, ack 282, win 64078, length 45 >> 17:59:38.705901 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 416, win 65535, length 0 >> 17:59:38.706052 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 416:463, ack 282, win 64078, length 47 >> 17:59:38.706067 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 463, win 65535, length 0 >> 17:59:38.842171 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >> seq 282:329, ack 463, win 65535, length 47 >> 17:59:38.907181 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 463:510, ack 329, win 65535, length 47 >> 17:59:38.907251 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 510, win 65535, length 0 >> 17:59:38.920789 IP 192.168.3.3.4606 > 192.168.3.1.squid: Flags [P.], seq >> 95:142, ack 94, win 65489, length 47 >> 17:59:38.920852 IP 192.168.3.1.squid > 192.168.3.3.4606: Flags [.], ack >> 142, win 65535, length 0 >> 17:59:39.056293 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >> seq 329:376, ack 510, win 65535, length 47 >> 17:59:39.139277 IP 192.168.3.1.squid > 192.168.3.3.4606: Flags [P.], seq >> 94:141, ack 142, win 65535, length 47 >> 17:59:39.221329 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 510:555, ack 376, win 65488, length 45 >> 17:59:39.221389 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 555, win 65535, length 0 >> 17:59:39.221485 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 555:602, ack 376, win 65488, length 47 >> 17:59:39.221502 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 602, win 65535, length 0 >> 17:59:39.289657 IP 192.168.3.3.4606 > 192.168.3.1.squid: Flags [.], ack >> 141, win 65442, length 0 >> 17:59:39.353948 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >> seq 376:423, ack 602, win 65535, length 47 >> 17:59:39.465344 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [.], >> ack 423, win 65441, length 0 >> 17:59:39.783793 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 602:647, ack 423, win 65441, length 45 >> 17:59:39.783859 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 647, win 65535, length 0 >> 17:59:39.783963 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 647:694, ack 423, win 65441, length 47 >> 17:59:39.783980 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 694, win 65535, length 0 >> 17:59:39.904000 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >> seq 423:470, ack 694, win 65535, length 47 >> 17:59:39.938403 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 694:741, ack 470, win 65394, length 47 >> 17:59:39.938469 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 741, win 65535, length 0 >> 17:59:39.952010 IP 192.168.3.3.4606 > 192.168.3.1.squid: Flags [P.], seq >> 142:189, ack 141, win 65442, length 47 >> 17:59:39.952084 IP 192.168.3.1.squid > 192.168.3.3.4606: Flags [.], ack >> 189, win 65535, length 0 >> 17:59:40.061688 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >> seq 470:517, ack 741, win 65535, length 47 >> 17:59:40.121592 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [.], >> ack 517, win 65347, length 0 >> 17:59:40.151038 IP 192.168.3.1.squid > 192.168.3.3.4606: Flags [P.], seq >> 141:188, ack 189, win 65535, length 47 >> 17:59:40.160299 IP 192.168.3.1 > 192.168.3.2: ICMP echo request, id >> 18191, seq 3338, length 64 >> 17:59:40.160423 IP 192.168.3.2 > 192.168.3.1: ICMP echo reply, id 18191, >> seq 3338, length 64 >> 17:59:40.160456 IP 192.168.3.1.46544 > 192.168.3.2.http: Flags [S], seq >> 782350204, win 14600, options [mss 1460,sackOK,TS val 622905018 ecr >> 0,nop,wscale 6], length 0 >> 17:59:40.160552 IP 192.168.3.2.http > 192.168.3.1.46544: Flags [R.], seq >> 0, ack 782350205, win 0, length 0 >> 17:59:40.274009 IP 192.168.3.3.4606 > 192.168.3.1.squid: Flags [.], ack >> 188, win 65395, length 0 >> 17:59:40.299307 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 741:786, ack 517, win 65347, length 45 >> 17:59:40.299365 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 786, win 65535, length 0 >> 17:59:40.299463 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >> seq 786:833, ack 517, win 65347, length 47 >> 17:59:40.299479 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >> ack 833, win 65535, length 0 >> 17:59:40.420492 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >> seq 517:564, ack 833, win 65535, length 47 >> 17:59:40.559059 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [.], >> ack 564, win 65300, length 0 >> >> >> >> dun know much abt this how to check this? >> >> > > On Tue, Mar 20, 2012 at 6:38 PM, David Coulson <[email protected]>wrote: > >> Means the client can't be a real server or the lvs router. >> >> Reply to the list not me. >> >> Sent from my iPhone >> >> On Mar 20, 2012, at 8:42 AM, Reet Vyas <[email protected]> wrote: >> >> separate client means? I am testing this from my machine >> >> On Tue, Mar 20, 2012 at 6:00 PM, Reet Vyas <[email protected]> wrote: >> >>> my tcpdump on eth0 >>> >>> win 1002, options [nop,nop,TS val 622858179 ecr 19927684], length 480 >>> 17:58:53.331753 IP >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.55541 > >>> server13000.teamviewer.com.https: Flags [P.], seq 1346:1390, ack 283, win >>> 1002, options [nop,nop,TS val 622858189 ecr 50106], length 44 >>> 17:58:53.359331 IP server12811.teamviewer.com.https > >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423: Flags [P.], seq >>> 820:868, ack 240, win 256, options [nop,nop,TS val 1649727 ecr 622858022], >>> length 48 >>> 17:58:53.359433 IP >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423 > >>> server12811.teamviewer.com.https: Flags [.], ack 868, win 245, options >>> [nop,nop,TS val 622858217 ecr 1649727], length 0 >>> 17:58:53.378801 IP >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.55541 > >>> server13000.teamviewer.com.https: Flags [P.], seq 1390:1434, ack 283, win >>> 1002, options [nop,nop,TS val 622858236 ecr 50106], length 44 >>> 17:58:53.388839 IP server13000.teamviewer.com.https > >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.55541: Flags [.], ack >>> 1390, win 260, options [nop,nop,TS val 50115 ecr 622858142], length 0 >>> 17:58:53.390759 IP 14.140.226.234.STATIC-Pune-vsnl.net.in.47901 > >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh: Flags [.], ack >>> 46880, win 501, options [nop,nop,TS val 19927754 ecr 622858135], length 0 >>> 17:58:53.390788 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh >>>> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [.], seq 48128:49576, >>> ack 49, win 1002, options [nop,nop,TS val 622858248 ecr 19927754], length >>> 1448 >>> 17:58:53.390794 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh >>>> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [P.], seq >>> 49576:49600, ack 49, win 1002, options [nop,nop,TS val 622858248 ecr >>> 19927754], length 24 >>> 17:58:53.396228 IP server12811.teamviewer.com.https > >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423: Flags [.], ack >>> 344, win 256, options [nop,nop,TS val 1649731 ecr 622858088], length 0 >>> 17:58:53.417494 IP >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423 > >>> server12811.teamviewer.com.https: Flags [P.], seq 344:399, ack 868, win >>> 245, options [nop,nop,TS val 622858275 ecr 1649731], length 55 >>> 17:58:53.425619 IP >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.55541 > >>> server13000.teamviewer.com.https: Flags [P.], seq 1434:1478, ack 283, win >>> 1002, options [nop,nop,TS val 622858283 ecr 50115], length 44 >>> 17:58:53.429508 IP server12811.teamviewer.com.https > >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423: Flags [P.], seq >>> 868:916, ack 344, win 256, options [nop,nop,TS val 1649734 ecr 622858088], >>> length 48 >>> 17:58:53.429604 IP >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423 > >>> server12811.teamviewer.com.https: Flags [.], ack 916, win 245, options >>> [nop,nop,TS val 622858287 ecr 1649734], length 0 >>> 17:58:53.432428 IP 14.140.226.234.STATIC-Pune-vsnl.net.in.47901 > >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh: Flags [.], ack >>> 48128, win 501, options [nop,nop,TS val 19927796 ecr 622858178], length 0 >>> 17:58:53.432458 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh >>>> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [.], seq 49600:51048, >>> ack 49, win 1002, options [nop,nop,TS val 622858290 ecr 19927796], length >>> 1448 >>> 17:58:53.432463 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh >>>> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [P.], seq >>> 51048:51504, ack 49, win 1002, options [nop,nop,TS val 622858290 ecr >>> 19927796], length 456 >>> 17:58:53.470912 IP server12811.teamviewer.com.https > >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423: Flags [P.], seq >>> 916:963, ack 344, win 256, options [nop,nop,TS val 1649738 ecr 622858088], >>> length 47 >>> 17:58:53.471013 IP >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.45423 > >>> server12811.teamviewer.com.https: Flags [.], ack 963, win 245, options >>> [nop,nop,TS val 622858329 ecr 1649738], length 0 >>> 17:58:53.472207 IP >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.55541 > >>> server13000.teamviewer.com.https: Flags [P.], seq 1478:1522, ack 283, win >>> 1002, options [nop,nop,TS val 622858330 ecr 50115], length 44 >>> 17:58:53.480516 IP 14.140.226.234.STATIC-Pune-vsnl.net.in.47901 > >>> ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh: Flags [P.], seq >>> 49:97, ack 48128, win 501, options [nop,nop,TS val 19927843 ecr 622858178], >>> length 48 >>> 17:58:53.480573 IP ABTS-KK-static-133.233.166.122.airtelbroadband.in.ssh >>>> 14.140.226.234.STATIC-Pune-vsnl.net.in.47901: Flags [.], ack 97, win >>> 1002, options [nop,nop,TS val 622858338 ecr 19927843], length 0 >>> >>> >>> >>> >>> >>> >>> >>> >>> and eth1 >>> >>> 17:59:38.329207 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >>> seq 235:282, ack 371, win 65535, length 47 >>> 17:59:38.481005 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [.], >>> ack 282, win 64078, length 0 >>> 17:59:38.705836 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 371:416, ack 282, win 64078, length 45 >>> 17:59:38.705901 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 416, win 65535, length 0 >>> 17:59:38.706052 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 416:463, ack 282, win 64078, length 47 >>> 17:59:38.706067 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 463, win 65535, length 0 >>> 17:59:38.842171 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >>> seq 282:329, ack 463, win 65535, length 47 >>> 17:59:38.907181 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 463:510, ack 329, win 65535, length 47 >>> 17:59:38.907251 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 510, win 65535, length 0 >>> 17:59:38.920789 IP 192.168.3.3.4606 > 192.168.3.1.squid: Flags [P.], seq >>> 95:142, ack 94, win 65489, length 47 >>> 17:59:38.920852 IP 192.168.3.1.squid > 192.168.3.3.4606: Flags [.], ack >>> 142, win 65535, length 0 >>> 17:59:39.056293 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >>> seq 329:376, ack 510, win 65535, length 47 >>> 17:59:39.139277 IP 192.168.3.1.squid > 192.168.3.3.4606: Flags [P.], seq >>> 94:141, ack 142, win 65535, length 47 >>> 17:59:39.221329 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 510:555, ack 376, win 65488, length 45 >>> 17:59:39.221389 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 555, win 65535, length 0 >>> 17:59:39.221485 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 555:602, ack 376, win 65488, length 47 >>> 17:59:39.221502 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 602, win 65535, length 0 >>> 17:59:39.289657 IP 192.168.3.3.4606 > 192.168.3.1.squid: Flags [.], ack >>> 141, win 65442, length 0 >>> 17:59:39.353948 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >>> seq 376:423, ack 602, win 65535, length 47 >>> 17:59:39.465344 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [.], >>> ack 423, win 65441, length 0 >>> 17:59:39.783793 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 602:647, ack 423, win 65441, length 45 >>> 17:59:39.783859 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 647, win 65535, length 0 >>> 17:59:39.783963 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 647:694, ack 423, win 65441, length 47 >>> 17:59:39.783980 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 694, win 65535, length 0 >>> 17:59:39.904000 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >>> seq 423:470, ack 694, win 65535, length 47 >>> 17:59:39.938403 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 694:741, ack 470, win 65394, length 47 >>> 17:59:39.938469 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 741, win 65535, length 0 >>> 17:59:39.952010 IP 192.168.3.3.4606 > 192.168.3.1.squid: Flags [P.], seq >>> 142:189, ack 141, win 65442, length 47 >>> 17:59:39.952084 IP 192.168.3.1.squid > 192.168.3.3.4606: Flags [.], ack >>> 189, win 65535, length 0 >>> 17:59:40.061688 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >>> seq 470:517, ack 741, win 65535, length 47 >>> 17:59:40.121592 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [.], >>> ack 517, win 65347, length 0 >>> 17:59:40.151038 IP 192.168.3.1.squid > 192.168.3.3.4606: Flags [P.], seq >>> 141:188, ack 189, win 65535, length 47 >>> 17:59:40.160299 IP 192.168.3.1 > 192.168.3.2: ICMP echo request, id >>> 18191, seq 3338, length 64 >>> 17:59:40.160423 IP 192.168.3.2 > 192.168.3.1: ICMP echo reply, id 18191, >>> seq 3338, length 64 >>> 17:59:40.160456 IP 192.168.3.1.46544 > 192.168.3.2.http: Flags [S], seq >>> 782350204, win 14600, options [mss 1460,sackOK,TS val 622905018 ecr >>> 0,nop,wscale 6], length 0 >>> 17:59:40.160552 IP 192.168.3.2.http > 192.168.3.1.46544: Flags [R.], seq >>> 0, ack 782350205, win 0, length 0 >>> 17:59:40.274009 IP 192.168.3.3.4606 > 192.168.3.1.squid: Flags [.], ack >>> 188, win 65395, length 0 >>> 17:59:40.299307 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 741:786, ack 517, win 65347, length 45 >>> 17:59:40.299365 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 786, win 65535, length 0 >>> 17:59:40.299463 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [P.], >>> seq 786:833, ack 517, win 65347, length 47 >>> 17:59:40.299479 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [.], >>> ack 833, win 65535, length 0 >>> 17:59:40.420492 IP 192.168.3.1.squid > 192.168.3.2.kv-server: Flags [P.], >>> seq 517:564, ack 833, win 65535, length 47 >>> 17:59:40.559059 IP 192.168.3.2.kv-server > 192.168.3.1.squid: Flags [.], >>> ack 564, win 65300, length 0 >>> >>> >>> >>> dun know much abt this how to check this? >>> >>> >>> >>> >>> On Tue, Mar 20, 2012 at 5:49 PM, David Coulson >>> <[email protected]>wrote: >>> >>>> You need to do a packet capture or something to figure out what is not >>>> working. You can't test from the lvs router. You need a separate client. >>>> >>>> Sent from my iPhone >>>> >>>> On Mar 20, 2012, at 8:15 AM, Reet Vyas <[email protected]> wrote: >>>> >>>> I did that but still no luck I just want to know wat i am trying to >>>> configure is correct or not .. Can i access url from VIP as >>>> 192.168.3.10:8080 or not? this is the VIP of my lvs router and it is >>>> working with reasl server 192.168.3.2:8080 .. >>>> >>>> >>>> On Tue, Mar 20, 2012 at 5:07 PM, David Coulson >>>> <[email protected]>wrote: >>>> >>>>> >>>>> http://kb.linuxvirtualserver.org/wiki/Windows_Servers_in_LVS/DR_and_LVS/TUN_Clusters >>>>> >>>>> >>>>> On 3/20/12 7:36 AM, Reet Vyas wrote: >>>>> >>>>> how to change to DR mode and my real servers are windows..how to do >>>>> this on windows >>>>> >>>>> On Tue, Mar 20, 2012 at 4:56 PM, David Coulson >>>>> <[email protected]>wrote: >>>>> >>>>>> Change it to use DR mode, then on each of your real servers do: >>>>>> >>>>>> iptables -t nat -A PREROUTING -d 192.168.3.10 -j REDIRECT >>>>>> >>>>>> does it work then? >>>>>> >>>>>> >>>>>> On 3/20/12 7:10 AM, Reet Vyas wrote: >>>>>> >>>>>>> Its yep I am using NAT for this lvs setup gateway of realserver is >>>>>>> vip of >>>>>>> my lvs router. Is this wrong?? If u can pleas suggest how to do it i >>>>>>> wasted my three days still no results :( >>>>>>> >>>>>>> On Tue, Mar 20, 2012 at 4:17 PM, Graeme Fowler<[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> On Tue, 2012-03-20 at 06:40 -0400, David Coulson wrote: >>>>>>>> >>>>>>>>> Actually, piranha is supported on el6. I must have been thinking of >>>>>>>>> something else. >>>>>>>>> >>>>>>>> Piranha was removed from Fedora 17, which implies that it will be >>>>>>>> removed from the next release of RedHat Enterprise Linux. As that's >>>>>>>> some >>>>>>>> time away, it's going to be around for a while yet. >>>>>>>> >>>>>>>> Looking at Reet's question though - what address does the client have >>>>>>>> that you're using to test your setup? It must *not* be on the same >>>>>>>> network range as the realservers. >>>>>>>> >>>>>>>> Graeme >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Please read the documentation before posting - it's available at: >>>>>>>> http://www.linuxvirtualserver.org/ >>>>>>>> >>>>>>>> LinuxVirtualServer.org mailing list - >>>>>>>> [email protected] >>>>>>>> Send requests to [email protected] >>>>>>>> or go to http://lists.graemef.net/mailman/listinfo/lvs-users >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>> Please read the documentation before posting - it's available at: >>>>>>> http://www.linuxvirtualserver.org/ >>>>>>> >>>>>>> LinuxVirtualServer.org mailing list - >>>>>>> [email protected] >>>>>>> Send requests to [email protected] >>>>>>> or go to http://lists.graemef.net/mailman/listinfo/lvs-users >>>>>>> >>>>>> >>>>> >>>> >>> >> > _______________________________________________ > Please read the documentation before posting - it's available at: > http://www.linuxvirtualserver.org/ > > LinuxVirtualServer.org mailing list - [email protected] > Send requests to [email protected] > or go to http://lists.graemef.net/mailman/listinfo/lvs-users _______________________________________________ Please read the documentation before posting - it's available at: http://www.linuxvirtualserver.org/ LinuxVirtualServer.org mailing list - [email protected] Send requests to [email protected] or go to http://lists.graemef.net/mailman/listinfo/lvs-users
