On Wednesday 23 October 2002 14:12, Joseph Mack wrote:
Hi Joseph,
> are you trying to connect to the VIP from the director?
I tried, sorry. This is wrong as I read again on the page. Now trying on a
different mashine. Same effect. I set debug to 100 via /proc ... Let's have a
look: (now with telnet)
root@codeman:[/] # telnet 10.0.0.40
Trying 10.0.0.40...
(nothing happens but the debug output below on the director)
Oct 23 16:32:03 rot kernel: IPVS: lookup_service fwm 0 TCP 10.0.0.40:23 hit
Oct 23 16:32:03 rot kernel: IPVS: look/in TCP 10.0.0.10:41004->10.0.0.40:23
not hit
Oct 23 16:32:03 rot kernel: IPVS: ip_vs_wlc_schedule(): Scheduling...
Oct 23 16:32:03 rot kernel: IPVS: WLC: server 10.0.1.12:23 activeconns 0
refcnt 1 weight 1 overhead 0
Oct 23 16:32:03 rot kernel: IPVS: Bind-masq fwd:R s:NONE c:10.0.0.10:41004
v:10.0.0.40:23 d:10.0.1.12:23 flg:470100 cnt:4 destcnt:2
Oct 23 16:32:03 rot kernel: IPVS: Schedule masq fwd:R s:NONE c:10.0.0.10:41004
v:10.0.0.40:23 d:10.0.1.12:23 flg:470100 cnt:4
Oct 23 16:32:03 rot kernel: IPVS: Set-state masq fwd:R s:NONE
c:10.0.0.10:41004 v:10.0.0.40:23 d:10.0.1.12:23 flg:470100 cnt:4
Oct 23 16:32:03 rot kernel: IPVS: direct routing succeeded.
Oct 23 16:32:03 rot kernel: IPVS: lookup_service fwm 0 TCP 10.0.0.40:22 not
hit
fw-rot:~# ipvsadm -L -n
IP Virtual Server version 1.0.8 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.0.0.40:23 wlc
-> 10.0.1.12:23 Route 1 0 0
-> 10.0.1.11:23 Route 1 0 1
-> 10.0.1.10:23 Route 1 0 0
fw-rot:~# ipchains -L -n -v
Chain input (policy ACCEPT: 12244 packets, 3888429 bytes):
Chain forward (policy ACCEPT: 0 packets, 0 bytes):
Chain output (policy ACCEPT: 9385 packets, 1717129 bytes):
fw-rot:~#
ciao, Marc
|