On 5/4/06, Hisham Mardam Bey <[EMAIL PROTECTED]> wrote:
Does anyone know why I am having those sudden drops in connections?
I have an update on the situation. Here's what I did: [client]-->[loadbal]-->[my 2 backends]->[samba server] I mounted a samba share from the samba server onto the client machine, and I tried to use mplayer to play the file. The file starts up, plays a few frames, then it starts to break up. I had logging set to "misc" using pfctl, and this is what I noticed: May 4 21:24:12 openbsd-be1 /bsd: pf_map_addr: selected address 172.16.2.1 May 4 21:25:00 openbsd-be1 /bsd: pf_map_addr: selected address 172.16.2.2 May 4 21:25:00 openbsd-be1 /bsd: pf: loose state match: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:53533 [lo=3175794114 high=3175794116 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 PA seq=3175794115 ack=0 len=72 ackskew=0 pkts=2:0 May 4 21:25:00 openbsd-be1 /bsd: pf: loose state match: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:53533 [lo=3175794187 high=3175794116 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 PA seq=3175794187 ack=0 len=168 ackskew=0 pkts=3:0 May 4 21:25:00 openbsd-be1 /bsd: pf: loose state match: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:53533 [lo=3175794355 high=3175794116 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 PA seq=3175794355 ack=0 len=144 ackskew=0 pkts=4:0 .. .. May 4 21:25:21 openbsd-be1 /bsd: pf_map_addr: selected address 172.16.2.1 May 4 21:25:59 openbsd-be1 /bsd: pf_map_addr: selected address 172.16.2.2 May 4 21:25:59 openbsd-be1 /bsd: pf: loose state match: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:51976 [lo=3591429406 high=3591429408 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 PA seq=3591429407 ack=0 len=72 ackskew=0 pkts=2:0 May 4 21:25:59 openbsd-be1 /bsd: pf: loose state match: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:51976 [lo=3591429479 high=3591429408 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 PA seq=3591429479 ack=0 len=168 ackskew=0 pkts=3:0 .. .. May 4 21:27:47 openbsd-be1 /bsd: pf: loose state match: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:64164 [lo=2612578234 high=2612511261 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 A seq=2612578234 ack=0 len=0 ackskew=0 pkts=1964:0 May 4 21:27:47 openbsd-be1 /bsd: pf: BAD state: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:64164 [lo=2612578234 high=2612511261 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 PA seq=2612578234 ack=0 len=63 ackskew=0 pkts=1965:0 dir=in,fwd May 4 21:27:47 openbsd-be1 /bsd: pf: State failure on: 1 | 5 May 4 21:27:48 openbsd-be1 /bsd: pf: BAD state: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:64164 [lo=2612578234 high=2612511261 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 PA seq=2612578234 ack=0 len=63 ackskew=0 pkts=1965:0 dir=in,fwd May 4 21:27:48 openbsd-be1 /bsd: pf: State failure on: 1 | 5 .. .. May 4 21:27:58 openbsd-be1 /bsd: pf: loose state match: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:64164 [lo=2612578234 high=2612511261 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 RA seq=2612578234 ack=0 len=0 ackskew=0 pkts=1965:0 May 4 21:28:04 openbsd-be1 /bsd: pf_map_addr: selected address 172.16.2.2 May 4 21:28:04 openbsd-be1 /bsd: pf: loose state match: TCP 192.168.0.223:139 192.168.0.223:139 172.16.2.4:57934 [lo=2945241422 high=2945241424 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 PA seq=2945241423 ack=0 len=72 ackskew=0 pkts=2:0 .. .. The first couple of selects were happening when I was listing directories over the smb share. Then some packets came in correctly when playing the movie. When I started getting breakups in the movie, I noticed the errors. Then by the time it had reslected an address from the map, mplayer quit. I hope this sheds some more light on the situation. Regards, hisham. -- Hisham Mardam Bey MSc (Computer Science) http://hisham.cc/ +9613609386 Codito Ergo Sum (I Code Therefore I Am)
