SRX

last person joined: yesterday 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.
  • 1.  how to read a session information on SRX 1400

    Posted 02-06-2015 00:53

    here is a session informaiton on SRX 1400

     


    Session ID: 20285605, Policy name: VPN-ACF-CCT-to-Remote/101, State: Active, Timeout: 2, Valid
    In: 10.1.138.32/3 --> 172.29.0.44/21;icmp, If: reth1.803, Pkts: 1, Bytes: 100
    Out: 172.29.0.44/21 --> 10.1.138.32/3;icmp, If: st0.14, Pkts: 1, Bytes: 100

     

    I want to ask that  in the third line . it mean that FW receives a packet whose source is 172.29.0.44 and dinstination 10.1.138.32 ? .or it  just means FW just sends a packet whose source is 10.1.138.32 , destination 172.29.0.44 out of st0.14.

    or something else .

     



  • 2.  RE: how to read a session information on SRX 1400
    Best Answer

     
    Posted 02-06-2015 01:46

    Out: 172.29.0.44/21 --> 10.1.138.32/3;icmp, If: st0.14, Pkts: 1, Bytes: 100

     

    this means, SRX received the packet from 172.29.0.44/21 destined to 10.1.138.32/3 on st0.14. It was an ICMP packet with 100 Bytes.

     

     

    When the Pkts: is 0, it means SRX expects the reply on st0.14 interface with source as 172.29.0.44/21 and destination as 10.1.138.32/3

     

     Below URL will give some more details on SRX session table.

     

    http://www.juniper.net/documentation/en_US/junos12.1x44/topics/reference/command-summary/show-security-flow-session.html

     

    Thanks,

    Suraj

    Please Mark My Solution Accepted if it Helped, Kudos are Appreciated too



  • 3.  RE: how to read a session information on SRX 1400

    Posted 02-07-2015 02:07

    thank you so much



  • 4.  RE: how to read a session information on SRX 1400

     
    Posted 02-07-2015 18:11

    Hi caulfiedd@live.cn,

    Thanks,can we mark the post as an "Accepted Solution" so others can benefit.

     

    Thanks,

    Suraj

    Please Mark My Solution Accepted if it Helped, Kudos are Appreciated too



  • 5.  RE: how to read a session information on SRX 1400

    Posted 02-23-2015 05:08

    Good feedback,

     

    but not very clear for me..

     

    Does this example them mean, there was source NAT?

     

    Suraj, the link provided is nice, but does not show how to read the output. 

     

    I'd love to see an exmple of IN/OUT where we have NAT and where we don't have NAT. Anyone please?



  • 6.  RE: how to read a session information on SRX 1400

     
    Posted 02-24-2015 03:26

    Hello Willys,

     

    using the session info from OP:

     

    Session ID: 20285605, Policy name: VPN-ACF-CCT-to-Remote/101, State: Active, Timeout: 2, Valid
    In: 10.1.138.32/3 --> 172.29.0.44/21;icmp, If: reth1.803, Pkts: 1, Bytes: 100
    Out: 172.29.0.44/21 --> 10.1.138.32/3;icmp, If: st0.14, Pkts: 1, Bytes: 100

     

     

    Say, there was PAT being done to IP address 192.1.1.1/32.  Then the session would look like:

     

    Session ID: 20285605, Policy name: VPN-ACF-CCT-to-Remote/101, State: Active, Timeout: 2, Valid
    In: 10.1.138.32/3 --> 172.29.0.44/21;icmp, If: reth1.803, Pkts: 1, Bytes: 100
    Out: 172.29.0.44/21 --> 192.1.1.1/3;icmp, If: st0.14, Pkts: 1, Bytes: 100

     

     

    I would interpret the session entries like this:

    * source of the traffic is from 10.1.138.32 -> 172.29.0.44 (this is how the packet is put on the wire... how the FW initially sees the packet). 

    * incoming interface of the original packet is reth1.803 interface

    * the firewall is expecting traffic in the reverse direction to come in on st0.14 interface

    * there is NAT involved since the return traffic's destination IP has reference to 192.1.1.1, instead of 10.1.138.32.  This makes sense, as this is how the packet would be seen by the firewall.

     

     

    Hope this helps,

     

    Regards,

    Sam



  • 7.  RE: how to read a session information on SRX 1400

    Posted 02-24-2015 22:18

    Hi samc,

    Much clearer and makes sense. I will take an example. 

     

    Session ID: 200000001, Policy name: default-policy/2, Timeout: 1794, Valid
      In: 40.0.0.111/32852 --> 30.0.0.100/21;tcp, If: ge-0/0/2.0, Pkts: 25, Bytes: 1138
      Out: 30.0.0.100/21 --> 40.0.0.111/32852;tcp, If: ge-0/0/1.0, Pkts: 20, Bytes: 1152
    Total sessions: 1

     

    Traffic comes into SRX via ge-0/0/2.0 from Source:40.0.0.111 to Destination: 30.0.0.100

    Traffic is expected in the reverse direction , via ge-0/0/1.0 from Source: 30.0.0.100 to Destination 40.0.0.111.

    And in this case, no NAT has been Applied.