Forum Discussion

Krzysztof_Kozlo's avatar
Krzysztof_Kozlo
Icon for Nimbostratus rankNimbostratus
Aug 02, 2007

SERVER_CONNECTED fails with fastL4?

When I try to do something like

 

 

rule log_client_ip {

 

when SERVER_CONNECTED {

 

log "[IP::client_addr]:[TCP::client_port] connected to [IP::server_addr]:[TCP::server_port] via [IP::local_addr]:[TCP::local_port]"

 

}

 

when CLIENT_CLOSED {

 

log "[IP::client_addr]:[TCP::client_port] disconnected from [IP::local_addr]:[TCP::local_port]"

 

}

 

}

 

 

with fastL4 enabled, the connections no longer work, they time out. And instead of logging, I get a message in the logs:

 

 

Aug 1 19:40:32 tmm tmm[1215]: 01220001:3: TCL error: Rule log_client_ip - Error: No connection established IP::server_addr needs an established connection! (line 1) invoked from within "IP::server_addr"

 

 

Turning off fastL4 works like a charm. Also, I tried to split up the CLIENT_ACCEPTED part for the sake of testing:

 

 

when CLIENT_ACCEPTED {

 

log "[IP::client_addr]:[TCP::client_port] connected to [IP::local_addr]:[TCP::local_port]"

 

}

 

 

That line gets logged, but the connection still fails as long as SERVER_CONNECTED references the server_addr.

 

 

Anyone have any suggestions? I tried disabling pva, it didn't help.

1 Reply

  • That looks like a bug noted in CR61257. You can contact F5 support for info on which version(s) it's been fixed in.

     

     

    Take a look at these two posts for related info on this error and another you'll probably see after that:

     

     

    Event: SERVER_CONNECTED, can be used in the fastL4 profile?

     

    Click here

     

     

    TCP port logging/decision-making with a FastL4 profile

     

    Click here

     

     

    Aaron