Passing GRE traffic across ASA

Hi,
I have an enviroment where I do need to pass the GRE traffic between two routers, the ASA-5510 is in between them.
Your help is appreciated. Sending a URL for similar setup, is great.
Sami

Hi,
Have you tried adding a static NAT for the router's external interface which is located behind the inside interface of the ASA ?
Example .. let's say the router which is behind the inside (higher priority) interface of the ASA is 10.10.10.10 then you could add a static as below
static (inside,outside) 10.10.10.10 10.10.10.10 mask 255.255.255.255
Note: the above assumes that the second router is behind the outside interface (lower priority) of the ASA and that the second router knows how to reach 10.10.10.10. Obviously 10.10.10.10 should also know how to get to the second router.
next you will need to allow GRE on both interfaces.
access-list inside-out permit GRE host 10.10.10.10 host
access-list outside-in permit GRE host host 10.10.10.10
access-group inside-out in interface inside
access-group outside-in in interface outside
Give it a try ..
I hope it helps .. please rate it if it does !!!

Similar Messages

  • 3230 Mobile Access Router not Passing Traffic across WMICs

    I'm unable to pass traffic across the WMICs. I've assigned the BVIs ip addresses in the same subnet and I'm seeing the devices associated. I attached the configurations.
    Thanks,

    A ruggedized router in a flexible and compact design, ideally suited to create mobile networks in and around vehicles.
    Here is the URL for the furthere information for grounding in the vehicales and description :
    http://www.cisco.com/en/US/prod/collateral/routers/ps272/prod_presentation0900aecd802948c0.pdf
    http://www.cisco.com/en/US/products/hw/routers/ps272/ps4375/index.html

  • GRE tunnel through asa no pptp, l2tp, ipsec

    Hello!
    can't understand how to configure GRE tunnel through ASA
    i have one router with public ip, connected to internet
    ASA 8.4 with public ip connected to internet
    router with private ip behind ASA.
    have only one public ip on ASA with /30 mask
    have no crypto
    have network behind ASA and PAT for internet users.
    can't nat GRE? cause only TCP/UDP nated(?)
    with packet-tracer i see flow already created but tunnel doesn't work

    A "clean" way would be to use a protocol that can be PATted. That could be GRE over IPSec. With that you have the additional benefit that your communication is protected through the internet.
    Don't stop after you've improved your network! Improve the world by lending money to the working poor:
    http://www.kiva.org/invitedby/karsteni

  • Monitoring GRE traffic with Netflow

    Hi,
    I have a GRE tunnel between an 3660 and a 3725. Under this tunnel there are many routers from SP, that we not even can see.
    The problem is that at Netflow it shows me only a high GRE traffic, giving me only details if using Nbar but still like that loosing all of informations available at Netflow reports (Conversations, source, etc).
    So, does anybody knows what should be configured at routers to enable netflow detailed informations of GRE tunnel?
    Rds,
    Alex

    ip flow-cache timeout active 5
    ip flow-export source Loopback0
    ip flow-export version 5
    ip flow-export destination [Server IP] 9996
    interface Tunnel0
    description tunnel vers rct2sin2
    bandwidth 27000
    ip address x.x.x.x x.x.x.x
    ip mtu 1472
    ip nbar protocol-discovery
    ip route-cache flow
    ip tcp adjust-mss 1432
    load-interval 30
    These are my confiurations and the router is a 3660.
    Rds,
    Alex

  • Cisco ASA 5505 - 1st VPN works, 2nd VPN can't get traffic across

    This is my first Cisco configuration ever so go easy on me.  A lot of the commands that I used here I don't really understand.  I got them from Googling configs.  I have the need for more than one VPN on this thing, and I've been fighting with this thing for hours today without any luck.
    The first VPN I setup, labeled vpn1 here works perfectly.  I connect via the public IP on the DSL and I can get traffic to my 192.168.1.0/24 network without any problems.
    I pretty much duplicated the configuration for the 2nd VPN, just replacing my 192.168.1.0/24 subnet w/ the network connected to a third interface on the ASA (10.4.0.0 255.255.240.0).  I successfully make connection to this VPN, but I cannot get traffic to traverse the VPN.  I'm using the address 10.4.0.1 to test pings.  The ASA itself can ping 10.4.0.1 as that interface of the ASA has 10.4.13.10 255.255.240.0, which is the same subnet (range is 10.4.0.0 - 10.4.15.255).
    Here is my config (edited for names and passwords)
    ciscoasa# show run
    : Saved
    ASA Version 8.2(5)
    hostname ciscoasa
    enable password ********** encrypted
    passwd ********** encrypted
    names
    interface Ethernet0/0
    switchport access vlan 2
    interface Ethernet0/1
    interface Ethernet0/2
    switchport access vlan 3
    interface Ethernet0/3
    interface Ethernet0/4
    interface Ethernet0/5
    interface Ethernet0/6
    interface Ethernet0/7
    interface Vlan1
    nameif inside
    security-level 100
    ip address 192.168.1.1 255.255.255.0
    interface Vlan2
    nameif outside
    security-level 0
    pppoe client vpdn group ISP_DSL
    ip address pppoe setroute
    interface Vlan3
    no forward interface Vlan1
    nameif private
    security-level 100
    ip address 10.4.13.10 255.255.240.0
    ftp mode passive
    access-list 100 extended permit icmp any any
    access-list nonat remark ACL for Nat Bypass
    access-list nonat extended permit ip 192.168.1.0 255.255.255.0 192.168.2.0 255.255.255.0
    access-list nonat extended permit ip 10.4.0.0 255.255.240.0 192.168.3.0 255.255.255.0
    access-list vpn_SplitTunnel remark ACL for VPN Split Tunnel
    access-list vpn_SplitTunnel standard permit 192.168.1.0 255.255.255.0
    access-list vpn_SplitTunnel standard permit 10.4.0.0 255.255.240.0
    pager lines 24
    logging asdm informational
    mtu inside 1500
    mtu outside 1492
    mtu private 1500
    ip local pool vpn1pool 192.168.2.100-192.168.2.110
    ip local pool vpn2pool 192.168.3.100-192.168.3.110
    no failover
    icmp unreachable rate-limit 1 burst-size 1
    no asdm history enable
    arp timeout 14400
    global (outside) 1 interface
    nat (inside) 0 access-list nonat
    nat (inside) 1 0.0.0.0 0.0.0.0
    nat (private) 0 access-list nonat
    access-group 100 in interface outside
    timeout xlate 3:00:00
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
    timeout tcp-proxy-reassembly 0:01:00
    timeout floating-conn 0:00:00
    dynamic-access-policy-record DfltAccessPolicy
    aaa authentication ssh console LOCAL
    http server enable
    http 192.168.1.0 255.255.255.0 inside
    no snmp-server location
    no snmp-server contact
    snmp-server enable traps snmp authentication linkup linkdown coldstart
    crypto ipsec transform-set strong-des esp-3des esp-md5-hmac
    crypto ipsec security-association lifetime seconds 28800
    crypto ipsec security-association lifetime kilobytes 4608000
    crypto dynamic-map dynmap 30 set transform-set strong-des
    crypto map vpn1 65535 ipsec-isakmp dynamic dynmap
    crypto map vpn1 interface outside
    crypto map vpn2 65535 ipsec-isakmp dynamic dynmap
    crypto isakmp identity address
    crypto isakmp enable outside
    crypto isakmp policy 11
    authentication pre-share
    encryption 3des
    hash md5
    group 2
    lifetime 86400
    telnet timeout 5
    ssh 0.0.0.0 0.0.0.0 inside
    ssh 0.0.0.0 0.0.0.0 outside
    ssh timeout 10
    console timeout 0
    vpdn group ISP_DSL request dialout pppoe
    vpdn group ISP_DSL localname [email protected]
    vpdn group ISP_DSL ppp authentication chap
    vpdn username [email protected] password **********
    dhcp-client update dns
    dhcpd auto_config outside
    dhcpd address 192.168.1.100-192.168.1.200 inside
    threat-detection basic-threat
    threat-detection statistics access-list
    no threat-detection statistics tcp-intercept
    webvpn
    group-policy vpn2 internal
    group-policy vpn2 attributes
    vpn-idle-timeout 120
    vpn-tunnel-protocol IPSec
    split-tunnel-policy tunnelspecified
    split-tunnel-network-list value vpn_SplitTunnel
    group-policy vpn1 internal
    group-policy vpn1 attributes
    vpn-idle-timeout 120
    vpn-tunnel-protocol IPSec
    split-tunnel-policy tunnelspecified
    split-tunnel-network-list value vpn_SplitTunnel
    username cssadmin password ********** encrypted
    username vpn2user password ********** encrypted
    username vpn1user password ********** encrypted
    tunnel-group vpn1-VPN type remote-access
    tunnel-group vpn1-VPN general-attributes
    address-pool vpn1pool
    default-group-policy vpn1
    tunnel-group vpn1-VPN ipsec-attributes
    pre-shared-key **********
    tunnel-group vpn2-VPN type remote-access
    tunnel-group vpn2-VPN general-attributes
    address-pool vpn2pool
    default-group-policy vpn2
    tunnel-group vpn2-VPN ipsec-attributes
    pre-shared-key *****
    prompt hostname context
    no call-home reporting anonymous
    Cryptochecksum:f5137c68c4b4a832c9dff8db808004ae
    : end
    Theories:  after fighting with it for a while and having another guy in my office look at it, we decided that the problem is probably that even though the pings are probably reaching 10.4.0.1, they have no route back to my VPN subnet 192.168.3.0/24.  I contacted the admins of the 10.4.0.0 network and asked if they could add a route to 192.168.3.0/24 via 10.4.13.10, but he said there is no router of default gateway on the network to even configure.
    So, what do I do?  Maybe NAT the VPN traffic?  If that is the correct answer, what lines would I put/change in the config to NAT that traffic.
    I'm assuming the reason the 1st VPN works is because the ASA is the default gateway for the inside 192.168.1.0/24 network.
    Thanks in advance for any insight you can provide.

    Hello Belnet,
    What do the logs show from the ASA.
    Can you post them ??
    Any other question..Sure..Just remember to rate all of the community answers.
    Julio

  • GRE traffic can not pass through LRT224 IPSec Tunnel

    Hi,
    We have a trouble when using Cisco Router GRE tunnel plus LRT224 IPSec Gateway-Gateway Tunnel.
    We found after reboot, GRE packets can not pass trough LRT224 IPSec tunnel. need to restart serval time then gre will back to normal.
    Besides that, GRE keepalive packets can not pass trough LRT224 IPSec Tunnel.
    please help. I had tried to upgrade to latest firmware version.
    Firmware Version : v1.0.3.09 (Dec 26 2014 14:28:46) 
    A-END:
    interface Tunnel1
    ip address 10.216.80.105 255.255.255.252
    ip mtu 1400
    ip nat outside
    ip virtual-reassembly in
    ip tcp adjust-mss 1360
    ip ospf network point-to-point
    ip ospf hello-interval 3
    ip ospf cost 10000
    tunnel source 10.216.81.2
    tunnel destination 10.216.80.90
    end
    B-END:
    interface Tunnel11
    ip address 10.216.80.110 255.255.255.252
    ip mtu 1400
    ip tcp adjust-mss 1360
    ip ospf network point-to-point
    ip ospf cost 10000
    ip ospf hello-interval 3
    tunnel source 10.216.80.91
    tunnel destination 10.216.81.3
    end
    CISCO2911 <> LRT224 <> INTERNET <> LRT224 <> CISCO 2621
    San

    Can you post the results from the below command for the Cisco Routers?
    IOS Command: "sh version"
    Why not static route without NAT through the LRT224 IPSec VPN?
    Just curious why did you use LRT224's for the Site to Site VPN instead of the Cisco Routers?
    Please remember to Kudo those that help you.
    Linksys
    Communities Technical Support

  • 3G VPN established but no traffic using ASA 5505

      Hi All,
    hoping that someone can help me here. We are able to esatblish VPN connection but we cannot pass traffic out.
    Here are the details.
    ISP has a range of 25.16.0.0/15 and they are doing Natting.
    We are using Raven X and ASA5505 is connected. Session is established but can't pass traffic or ping.
    router output:
    ASA Version 8.2(2)
    hostname DR-5505-50
    domain-name dont know
    enable password xxxxxx encrypted passwd kOuREZbrVpcZibgH encrypted names name 192.168.0.0 Corp name 10.10.0.0 device !
    interface Vlan1
    nameif inside
    security-level 100
    ip address 10.10.254.254 255.255.255.0
    interface Vlan2
    nameif outside
    security-level 0
    ip address dhcp setroute
    interface Ethernet0/0
    switchport access vlan 2
    interface Ethernet0/1
    interface Ethernet0/2
    interface Ethernet0/3
    interface Ethernet0/4
    interface Ethernet0/5
    interface Ethernet0/6
    interface Ethernet0/7
    ftp mode passive
    clock timezone EST -5
    clock summer-time EDT recurring
    dns server-group DefaultDNS
    domain-name network.comsame-security-traffic permit inter-interface same-security-traffic permit intra-interface object-group network never  network-object Jobsites 255.255.0.0  network-object Corp 255.255.0.0 access-list outside_1_cryptomap extended permit ip 10.10.254.0
    255.255.255.0 object-group network access-list inside_nat0_outbound extended permit ip 10.10.254.0
    255.255.255.0 object-group networkn
    access-list inside_access_in extended permit ip 10.10.254.0 255.255.255.0 any pager lines 24 logging asdm informational mtu inside 1500 mtu outside 1500 icmp unreachable rate-limit 1 burst-size 1 icmp permit any inside icmp permit any outside no asdm history enable arp timeout 14400 global (outside) 1 interface nat (inside) 0 access-list inside_nat0_outbound nat (inside) 1 0.0.0.0 0.0.0.0 access-group inside_access_in in interface inside access-group outside_access_in in interface outside timeout xlate 3:00:00 timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02 timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat
    0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect
    0:02:00
    timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute timeout tcp-proxy-reassembly 0:01:00 dynamic-access-policy-record DfltAccessPolicy aaa authentication ssh console LOCAL http server enable http 0.0.0.0 0.0.0.0 outside http 0.0.0.0 0.0.0.0 inside snmp-server host inside 192.168.152.28 community edsnmp version 2c no snmp-server location no snmp-server contact snmp-server community edsnmp snmp-server enable traps snmp authentication linkup linkdown coldstart crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac crypto ipsec security-association lifetime seconds 28800 crypto ipsec security-association lifetime kilobytes 4608000 crypto map outside_map 1 match address outside_1_cryptomap crypto map outside_map 1 set pfs group1 crypto map outside_map 1 set peer 204.101.74.2 crypto map outside_map 1 set transform-set ESP-3DES-SHA crypto map outside_map interface outside crypto isakmp identity hostname crypto isakmp enable outside crypto isakmp policy 10  authentication pre-share  encryption 3des  hash sha  group 2  lifetime 86400 crypto isakmp policy 65535  authentication pre-share  encryption 3des  hash sha  group 2  lifetime 86400 no crypto isakmp nat-traversal telnet timeout 5 ssh 0.0.0.0 0.0.0.0 inside ssh 0.0.0.0 0.0.0.0 outside ssh timeout 60 console timeout 0 management-access inside dhcpd auto_config outside !
    dhcpd address 10.10.254.70-10.10.254.169 inside dhcpd dns 192.168.152.21 192.168.160.21 interface inside dhcpd lease 432000 interface inside dhcpd domain name.com interface inside dhcpd option 3 ip 10.10.254.254 interface inside dhcpd enable inside !
    vpnclient management clear
    threat-detection basic-threat
    threat-detection statistics access-list
    no threat-detection statistics tcp-intercept webvpn  tunnel-group-list enable username admin password Xhasdfuasdhsdfh encrypted privilege 15 tunnel-group x.x.x.x type ipsec-l2l tunnel-group x.x.x.xipsec-attributes  pre-shared-key dynamicvpn !
    prompt hostname context
    call-home
    profile CiscoTAC-1
      no active
      destination address http
    whatever.com
      destination address email [email protected]
      destination transport-method http
      subscribe-to-alert-group diagnostic
      subscribe-to-alert-group environment
      subscribe-to-alert-group inventory periodic monthly
      subscribe-to-alert-group configuration periodic monthly
      subscribe-to-alert-group telemetry periodic daily
    Cryptochecksum:
    Log file:
    6|May 06 2013|07:00:01|302016|192.168.160.21|53|10.10.254.70|57967|Teardown UDP connection 245 for outside:192.168.160.21/53 to inside:10.10.254.70/57967 duration 0:02:07 bytes 148
    6|May 06 2013|07:00:01|302016|192.168.152.21|53|10.10.254.70|57967|Teardown UDP connection 243 for outside:192.168.152.21/53 to inside:10.10.254.70/57967 duration 0:02:08 bytes 111
    6|May 06 2013|06:59:58|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:57|302015|192.168.160.21|53|10.10.254.70|52108|Built outbound UDP connection 349 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/52108 (10.10.254.70/52108)
    6|May 06 2013|06:59:56|302015|192.168.160.21|53|10.10.254.70|50503|Built outbound UDP connection 348 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/50503 (10.10.254.70/50503)
    6|May 06 2013|06:59:56|302016|192.168.160.21|53|10.10.254.70|54304|Teardown UDP connection 241 for outside:192.168.160.21/53 to inside:10.10.254.70/54304 duration 0:02:07 bytes 236
    6|May 06 2013|06:59:56|302016|192.168.152.21|53|10.10.254.70|54304|Teardown UDP connection 240 for outside:192.168.152.21/53 to inside:10.10.254.70/54304 duration 0:02:08 bytes 177
    6|May 06 2013|06:59:56|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:56|302015|192.168.152.21|53|10.10.254.70|52108|Built outbound UDP connection 346 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/52108 (10.10.254.70/52108)
    6|May 06 2013|06:59:55|302015|192.168.152.21|53|10.10.254.70|50503|Built outbound UDP connection 345 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/50503 (10.10.254.70/50503)
    6|May 06 2013|06:59:55|302016|192.168.160.21|53|10.10.254.70|65422|Teardown UDP connection 238 for outside:192.168.160.21/53 to inside:10.10.254.70/65422 duration 0:02:07 bytes 136
    6|May 06 2013|06:59:55|302016|192.168.152.21|53|10.10.254.70|65422|Teardown UDP connection 237 for outside:192.168.152.21/53 to inside:10.10.254.70/65422 duration 0:02:08 bytes 102
    6|May 06 2013|06:59:54|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:54|302015|192.168.160.21|53|10.10.254.70|51008|Built outbound UDP connection 344 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/51008 (10.10.254.70/51008)
    6|May 06 2013|06:59:53|302015|192.168.152.21|53|10.10.254.70|51008|Built outbound UDP connection 343 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/51008 (10.10.254.70/51008)
    6|May 06 2013|06:59:53|302016|192.168.160.21|53|10.10.254.70|50300|Teardown UDP connection 236 for outside:192.168.160.21/53 to inside:10.10.254.70/50300 duration 0:02:07 bytes 152
    6|May 06 2013|06:59:53|302016|192.168.152.21|53|10.10.254.70|50300|Teardown UDP connection 234 for outside:192.168.152.21/53 to inside:10.10.254.70/50300 duration 0:02:08 bytes 114
    6|May 06 2013|06:59:53|302016|192.168.160.21|53|10.10.254.70|49286|Teardown UDP connection 235 for outside:192.168.160.21/53 to inside:10.10.254.70/49286 duration 0:02:07 bytes 152
    6|May 06 2013|06:59:53|302016|192.168.152.21|53|10.10.254.70|49286|Teardown UDP connection 233 for outside:192.168.152.21/53 to inside:10.10.254.70/49286 duration 0:02:08 bytes 114
    6|May 06 2013|06:59:52|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:50|302016|192.168.160.21|53|10.10.254.70|57306|Teardown UDP connection 231 for outside:192.168.160.21/53 to inside:10.10.254.70/57306 duration 0:02:07 bytes 152
    6|May 06 2013|06:59:50|302016|192.168.152.21|53|10.10.254.70|57306|Teardown UDP connection 229 for outside:192.168.152.21/53 to inside:10.10.254.70/57306 duration 0:02:08 bytes 114
    6|May 06 2013|06:59:50|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:49|302014|129.22.177.79|31663|10.10.254.70|34470|Teardown TCP connection 322 for outside:129.22.177.79/31663 to inside:10.10.254.70/34470 duration 0:00:30 bytes 0 SYN Timeout
    6|May 06 2013|06:59:49|302016|192.168.160.21|53|10.10.254.70|54646|Teardown UDP connection 230 for outside:192.168.160.21/53 to inside:10.10.254.70/54646 duration 0:02:07 bytes 160
    6|May 06 2013|06:59:49|302016|192.168.152.21|53|10.10.254.70|54646|Teardown UDP connection 227 for outside:192.168.152.21/53 to inside:10.10.254.70/54646 duration 0:02:08 bytes 120
    6|May 06 2013|06:59:49|302016|192.168.160.21|53|10.10.254.70|64481|Teardown UDP connection 228 for outside:192.168.160.21/53 to inside:10.10.254.70/64481 duration 0:02:07 bytes 152
    6|May 06 2013|06:59:49|302016|192.168.152.21|53|10.10.254.70|64481|Teardown UDP connection 226 for outside:192.168.152.21/53 to inside:10.10.254.70/64481 duration 0:02:08 bytes 114
    6|May 06 2013|06:59:48|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:47|305012|10.10.254.70|34468|192.168.13.100|55721|Teardown dynamic TCP translation from inside:10.10.254.70/34468 to outside:192.168.13.100/55721 duration 0:01:30
    6|May 06 2013|06:59:46|305012|10.10.254.70|34467|192.168.13.100|48446|Teardown dynamic TCP translation from inside:10.10.254.70/34467 to outside:192.168.13.100/48446 duration 0:01:30
    6|May 06 2013|06:59:46|302016|192.168.152.21|53|10.10.254.70|63417|Teardown UDP connection 224 for outside:192.168.152.21/53 to inside:10.10.254.70/63417 duration 0:02:07 bytes 111
    6|May 06 2013|06:59:46|302016|192.168.160.21|53|10.10.254.70|63417|Teardown UDP connection 223 for outside:192.168.160.21/53 to inside:10.10.254.70/63417 duration 0:02:08 bytes 148
    6|May 06 2013|06:59:46|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:44|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:42|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:40|302015|192.168.152.21|53|10.10.254.70|62424|Built outbound UDP connection 339 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/62424 (10.10.254.70/62424)
    6|May 06 2013|06:59:40|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:39|302015|192.168.160.21|53|10.10.254.70|62424|Built outbound UDP connection 337 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/62424 (10.10.254.70/62424)
    6|May 06 2013|06:59:38|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:37|302016|192.168.152.21|53|10.10.254.70|59943|Teardown UDP connection 219 for outside:192.168.152.21/53 to inside:10.10.254.70/59943 duration 0:02:07 bytes 108
    6|May 06 2013|06:59:37|302016|192.168.160.21|53|10.10.254.70|59943|Teardown UDP connection 218 for outside:192.168.160.21/53 to inside:10.10.254.70/59943 duration 0:02:08 bytes 144
    6|May 06 2013|06:59:37|302015|192.168.152.21|53|10.10.254.70|58710|Built outbound UDP connection 336 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/58710 (10.10.254.70/58710)
    6|May 06 2013|06:59:36|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:36|302015|192.168.160.21|53|10.10.254.70|58710|Built outbound UDP connection 334 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/58710 (10.10.254.70/58710)
    6|May 06 2013|06:59:36|302016|192.168.152.21|53|10.10.254.70|51377|Teardown UDP connection 217 for outside:192.168.152.21/53 to inside:10.10.254.70/51377 duration 0:02:07 bytes 114
    6|May 06 2013|06:59:36|302016|192.168.160.21|53|10.10.254.70|51377|Teardown UDP connection 215 for outside:192.168.160.21/53 to inside:10.10.254.70/51377 duration 0:02:08 bytes 152
    6|May 06 2013|06:59:34|302016|192.168.152.21|53|10.10.254.70|56751|Teardown UDP connection 214 for outside:192.168.152.21/53 to inside:10.10.254.70/56751 duration 0:02:07 bytes 111
    6|May 06 2013|06:59:34|302016|192.168.160.21|53|10.10.254.70|56751|Teardown UDP connection 213 for outside:192.168.160.21/53 to inside:10.10.254.70/56751 duration 0:02:08 bytes 148
    6|May 06 2013|06:59:34|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:32|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:32|302016|192.168.152.21|53|10.10.254.70|63965|Teardown UDP connection 212 for outside:192.168.152.21/53 to inside:10.10.254.70/63965 duration 0:02:07 bytes 114
    6|May 06 2013|06:59:32|302016|192.168.160.21|53|10.10.254.70|63965|Teardown UDP connection 210 for outside:192.168.160.21/53 to inside:10.10.254.70/63965 duration 0:02:08 bytes 152
    6|May 06 2013|06:59:30|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:28|302016|192.168.152.21|137|10.10.254.70|137|Teardown UDP connection 211 for outside:192.168.152.21/137 to inside:10.10.254.70/137 duration 0:02:04 bytes 150
    6|May 06 2013|06:59:28|302015|192.168.152.21|53|10.10.254.70|57795|Built outbound UDP connection 332 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/57795 (10.10.254.70/57795)
    6|May 06 2013|06:59:28|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:28|302016|192.168.152.21|53|10.10.254.70|60822|Teardown UDP connection 206 for outside:192.168.152.21/53 to inside:10.10.254.70/60822 duration 0:02:07 bytes 114
    6|May 06 2013|06:59:28|302016|192.168.160.21|53|10.10.254.70|60822|Teardown UDP connection 205 for outside:192.168.160.21/53 to inside:10.10.254.70/60822 duration 0:02:08 bytes 152
    6|May 06 2013|06:59:27|302015|192.168.160.21|53|10.10.254.70|57795|Built outbound UDP connection 330 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/57795 (10.10.254.70/57795)
    6|May 06 2013|06:59:26|302015|192.168.152.21|53|10.10.254.70|54989|Built outbound UDP connection 329 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/54989 (10.10.254.70/54989)
    6|May 06 2013|06:59:26|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:25|302015|192.168.160.21|53|10.10.254.70|54989|Built outbound UDP connection 328 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/54989 (10.10.254.70/54989)
    6|May 06 2013|06:59:25|302015|192.168.152.21|53|10.10.254.70|58248|Built outbound UDP connection 327 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/58248 (10.10.254.70/58248)
    6|May 06 2013|06:59:24|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:24|302015|192.168.160.21|53|10.10.254.70|58248|Built outbound UDP connection 325 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/58248 (10.10.254.70/58248)
    6|May 06 2013|06:59:22|302016|192.168.152.21|53|10.10.254.70|52148|Teardown UDP connection 204 for outside:192.168.152.21/53 to inside:10.10.254.70/52148 duration 0:02:07 bytes 111
    6|May 06 2013|06:59:22|302016|192.168.160.21|53|10.10.254.70|52148|Teardown UDP connection 201 for outside:192.168.160.21/53 to inside:10.10.254.70/52148 duration 0:02:08 bytes 148
    6|May 06 2013|06:59:22|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:20|302013|129.22.177.79|31663|10.10.254.70|34471|Built outbound TCP connection 324 for outside:129.22.177.79/31663 (129.22.177.79/31663) to inside:10.10.254.70/34471 (192.168.13.100/60918)
    6|May 06 2013|06:59:20|305011|10.10.254.70|34471|192.168.13.100|60918|Built dynamic TCP translation from inside:10.10.254.70/34471 to outside:192.168.13.100/60918
    6|May 06 2013|06:59:20|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:20|302016|192.168.152.21|53|10.10.254.70|50470|Teardown UDP connection 200 for outside:192.168.152.21/53 to inside:10.10.254.70/50470 duration 0:02:07 bytes 135
    6|May 06 2013|06:59:20|302016|192.168.160.21|53|10.10.254.70|50470|Teardown UDP connection 199 for outside:192.168.160.21/53 to inside:10.10.254.70/50470 duration 0:02:08 bytes 180
    6|May 06 2013|06:59:20|302014|71.207.1.189|1761|10.10.254.70|34468|Teardown TCP connection 275 for outside:71.207.1.189/1761 to inside:10.10.254.70/34468 duration 0:01:02 bytes 376 TCP FINs
    6|May 06 2013|06:59:19|302013|129.22.177.79|31663|10.10.254.70|34470|Built outbound TCP connection 322 for outside:129.22.177.79/31663 (129.22.177.79/31663) to inside:10.10.254.70/34470 (192.168.13.100/64832)
    6|May 06 2013|06:59:19|305011|10.10.254.70|34470|192.168.13.100|64832|Built dynamic TCP translation from inside:10.10.254.70/34470 to outside:192.168.13.100/64832
    6|May 06 2013|06:59:18|302014|67.86.118.52|17365|10.10.254.70|34467|Teardown TCP connection 274 for outside:67.86.118.52/17365 to inside:10.10.254.70/34467 duration 0:01:02 bytes 453 TCP FINs
    6|May 06 2013|06:59:18|302013|173.164.60.149|12864|10.10.254.70|34469|Built outbound TCP connection 321 for outside:173.164.60.149/12864 (173.164.60.149/12864) to inside:10.10.254.70/34469 (192.168.13.100/39628)
    6|May 06 2013|06:59:18|305011|10.10.254.70|34469|192.168.13.100|39628|Built dynamic TCP translation from inside:10.10.254.70/34469 to outside:192.168.13.100/39628
    6|May 06 2013|06:59:18|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:17|302016|192.168.152.21|53|10.10.254.70|54536|Teardown UDP connection 198 for outside:192.168.152.21/53 to inside:10.10.254.70/54536 duration 0:02:07 bytes 114
    6|May 06 2013|06:59:17|302016|192.168.160.21|53|10.10.254.70|54536|Teardown UDP connection 197 for outside:192.168.160.21/53 to inside:10.10.254.70/54536 duration 0:02:08 bytes 152
    6|May 06 2013|06:59:16|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:14|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:13|302016|192.168.152.21|53|10.10.254.70|57635|Teardown UDP connection 196 for outside:192.168.152.21/53 to inside:10.10.254.70/57635 duration 0:02:07 bytes 102
    6|May 06 2013|06:59:13|302016|192.168.160.21|53|10.10.254.70|57635|Teardown UDP connection 195 for outside:192.168.160.21/53 to inside:10.10.254.70/57635 duration 0:02:08 bytes 136
    6|May 06 2013|06:59:12|302015|192.168.152.21|53|10.10.254.70|60510|Built outbound UDP connection 319 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/60510 (10.10.254.70/60510)
    6|May 06 2013|06:59:12|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:12|302015|192.168.152.21|53|10.10.254.70|50779|Built outbound UDP connection 317 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/50779 (10.10.254.70/50779)
    6|May 06 2013|06:59:11|302015|192.168.160.21|53|10.10.254.70|60510|Built outbound UDP connection 316 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/60510 (10.10.254.70/60510)
    6|May 06 2013|06:59:11|302016|192.168.152.21|53|10.10.254.70|49716|Teardown UDP connection 194 for outside:192.168.152.21/53 to inside:10.10.254.70/49716 duration 0:02:07 bytes 111
    6|May 06 2013|06:59:11|302016|192.168.152.21|53|10.10.254.70|57570|Teardown UDP connection 193 for outside:192.168.152.21/53 to inside:10.10.254.70/57570 duration 0:02:07 bytes 156
    6|May 06 2013|06:59:11|302016|192.168.160.21|53|10.10.254.70|49716|Teardown UDP connection 192 for outside:192.168.160.21/53 to inside:10.10.254.70/49716 duration 0:02:08 bytes 148
    6|May 06 2013|06:59:11|302016|192.168.160.21|53|10.10.254.70|57570|Teardown UDP connection 191 for outside:192.168.160.21/53 to inside:10.10.254.70/57570 duration 0:02:08 bytes 208
    6|May 06 2013|06:59:11|302015|192.168.160.21|53|10.10.254.70|50779|Built outbound UDP connection 315 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/50779 (10.10.254.70/50779)
    6|May 06 2013|06:59:10|302015|192.168.152.21|53|10.10.254.70|64783|Built outbound UDP connection 314 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/64783 (10.10.254.70/64783)
    6|May 06 2013|06:59:10|302016|192.168.152.21|53|10.10.254.70|63136|Teardown UDP connection 190 for outside:192.168.152.21/53 to inside:10.10.254.70/63136 duration 0:02:07 bytes 111
    6|May 06 2013|06:59:10|302016|192.168.160.21|53|10.10.254.70|63136|Teardown UDP connection 189 for outside:192.168.160.21/53 to inside:10.10.254.70/63136 duration 0:02:08 bytes 148
    6|May 06 2013|06:59:10|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:09|302015|192.168.160.21|53|10.10.254.70|64783|Built outbound UDP connection 313 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/64783 (10.10.254.70/64783)
    6|May 06 2013|06:59:08|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:06|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:04|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:03|305012|10.10.254.70|34458|192.168.13.100|26157|Teardown dynamic TCP translation from inside:10.10.254.70/34458 to outside:192.168.13.100/26157 duration 0:01:00
    6|May 06 2013|06:59:02|302016|192.168.160.21|53|10.10.254.70|54985|Teardown UDP connection 186 for outside:192.168.160.21/53 to inside:10.10.254.70/54985 duration 0:02:07 bytes 152
    6|May 06 2013|06:59:02|302016|192.168.152.21|53|10.10.254.70|54985|Teardown UDP connection 184 for outside:192.168.152.21/53 to inside:10.10.254.70/54985 duration 0:02:08 bytes 114
    6|May 06 2013|06:59:02|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:59:00|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:58|305012|10.10.254.70|34457|192.168.13.100|43659|Teardown dynamic TCP translation from inside:10.10.254.70/34457 to outside:192.168.13.100/43659 duration 0:01:00
    6|May 06 2013|06:58:58|305012|10.10.254.70|34456|192.168.13.100|47534|Teardown dynamic TCP translation from inside:10.10.254.70/34456 to outside:192.168.13.100/47534 duration 0:01:00
    6|May 06 2013|06:58:58|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:57|305012|10.10.254.70|34455|192.168.13.100|4536|Teardown dynamic TCP translation from inside:10.10.254.70/34455 to outside:192.168.13.100/4536 duration 0:01:00
    6|May 06 2013|06:58:57|302016|192.168.160.21|53|10.10.254.70|57758|Teardown UDP connection 182 for outside:192.168.160.21/53 to inside:10.10.254.70/57758 duration 0:02:07 bytes 152
    6|May 06 2013|06:58:57|302016|192.168.160.21|53|10.10.254.70|56258|Teardown UDP connection 181 for outside:192.168.160.21/53 to inside:10.10.254.70/56258 duration 0:02:07 bytes 148
    6|May 06 2013|06:58:57|302016|192.168.152.21|53|10.10.254.70|57758|Teardown UDP connection 180 for outside:192.168.152.21/53 to inside:10.10.254.70/57758 duration 0:02:08 bytes 114
    6|May 06 2013|06:58:57|302016|192.168.152.21|53|10.10.254.70|56258|Teardown UDP connection 179 for outside:192.168.152.21/53 to inside:10.10.254.70/56258 duration 0:02:08 bytes 111
    6|May 06 2013|06:58:57|305012|10.10.254.70|34454|192.168.13.100|39886|Teardown dynamic TCP translation from inside:10.10.254.70/34454 to outside:192.168.13.100/39886 duration 0:01:00
    6|May 06 2013|06:58:56|302015|192.168.152.21|53|10.10.254.70|65123|Built outbound UDP connection 309 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/65123 (10.10.254.70/65123)
    6|May 06 2013|06:58:56|305012|10.10.254.70|34453|192.168.13.100|34856|Teardown dynamic TCP translation from inside:10.10.254.70/34453 to outside:192.168.13.100/34856 duration 0:01:00
    6|May 06 2013|06:58:56|305012|10.10.254.70|34452|192.168.13.100|33908|Teardown dynamic TCP translation from inside:10.10.254.70/34452 to outside:192.168.13.100/33908 duration 0:01:00
    6|May 06 2013|06:58:56|302016|67.84.253.214|56426|10.10.254.70|64582|Teardown UDP connection 185 for outside:67.84.253.214/56426 to inside:10.10.254.70/64582 duration 0:02:01 bytes 44
    6|May 06 2013|06:58:56|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:56|302015|192.168.152.21|53|10.10.254.70|65511|Built outbound UDP connection 307 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/65511 (10.10.254.70/65511)
    6|May 06 2013|06:58:56|302016|192.168.160.21|53|10.10.254.70|54190|Teardown UDP connection 178 for outside:192.168.160.21/53 to inside:10.10.254.70/54190 duration 0:02:07 bytes 148
    6|May 06 2013|06:58:56|302016|192.168.152.21|53|10.10.254.70|54190|Teardown UDP connection 177 for outside:192.168.152.21/53 to inside:10.10.254.70/54190 duration 0:02:08 bytes 111
    6|May 06 2013|06:58:55|302015|192.168.160.21|53|10.10.254.70|65123|Built outbound UDP connection 306 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/65123 (10.10.254.70/65123)
    6|May 06 2013|06:58:55|302015|192.168.160.21|53|10.10.254.70|65511|Built outbound UDP connection 305 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/65511 (10.10.254.70/65511)
    6|May 06 2013|06:58:54|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:53|302016|192.168.160.21|53|10.10.254.70|57069|Teardown UDP connection 175 for outside:192.168.160.21/53 to inside:10.10.254.70/57069 duration 0:02:07 bytes 236
    6|May 06 2013|06:58:53|302016|192.168.152.21|53|10.10.254.70|57069|Teardown UDP connection 173 for outside:192.168.152.21/53 to inside:10.10.254.70/57069 duration 0:02:08 bytes 177
    6|May 06 2013|06:58:52|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:51|302015|192.168.152.21|53|10.10.254.70|51914|Built outbound UDP connection 303 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/51914 (10.10.254.70/51914)
    6|May 06 2013|06:58:51|302016|192.168.160.21|53|10.10.254.70|53582|Teardown UDP connection 169 for outside:192.168.160.21/53 to inside:10.10.254.70/53582 duration 0:02:07 bytes 120
    6|May 06 2013|06:58:51|302016|192.168.152.21|53|10.10.254.70|53582|Teardown UDP connection 166 for outside:192.168.152.21/53 to inside:10.10.254.70/53582 duration 0:02:08 bytes 90
    6|May 06 2013|06:58:50|302016|178.46.108.7|36497|10.10.254.70|64582|Teardown UDP connection 96 for outside:178.46.108.7/36497 to inside:10.10.254.70/64582 duration 0:02:34 bytes 108
    6|May 06 2013|06:58:50|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:50|302015|192.168.160.21|53|10.10.254.70|51914|Built outbound UDP connection 302 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/51914 (10.10.254.70/51914)
    6|May 06 2013|06:58:48|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:48|302015|192.168.152.21|53|10.10.254.70|65020|Built outbound UDP connection 300 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/65020 (10.10.254.70/65020)
    6|May 06 2013|06:58:47|302014|50.72.9.170|12248|10.10.254.70|34454|Teardown TCP connection 252 for outside:50.72.9.170/12248 to inside:10.10.254.70/34454 duration 0:00:50 bytes 389 TCP FINs
    6|May 06 2013|06:58:47|302014|174.91.241.232|53766|10.10.254.70|34458|Teardown TCP connection 260 for outside:174.91.241.232/53766 to inside:10.10.254.70/34458 duration 0:00:44 bytes 384 TCP FINs
    6|May 06 2013|06:58:47|302014|24.202.182.58|43715|10.10.254.70|34452|Teardown TCP connection 249 for outside:24.202.182.58/43715 to inside:10.10.254.70/34452 duration 0:00:51 bytes 440 TCP FINs
    6|May 06 2013|06:58:47|302015|192.168.160.21|53|10.10.254.70|65020|Built outbound UDP connection 299 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/65020 (10.10.254.70/65020)
    6|May 06 2013|06:58:46|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:45|305012|10.10.254.70|34448|192.168.13.100|53786|Teardown dynamic TCP translation from inside:10.10.254.70/34448 to outside:192.168.13.100/53786 duration 0:01:30
    6|May 06 2013|06:58:44|305012|10.10.254.70|34447|192.168.13.100|43394|Teardown dynamic TCP translation from inside:10.10.254.70/34447 to outside:192.168.13.100/43394 duration 0:01:30
    6|May 06 2013|06:58:44|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:44|302016|192.168.152.21|53|10.10.254.70|62190|Teardown UDP connection 162 for outside:192.168.152.21/53 to inside:10.10.254.70/62190 duration 0:02:07 bytes 111
    6|May 06 2013|06:58:44|302016|192.168.160.21|53|10.10.254.70|62190|Teardown UDP connection 158 for outside:192.168.160.21/53 to inside:10.10.254.70/62190 duration 0:02:08 bytes 148
    6|May 06 2013|06:58:42|302015|192.168.152.21|53|10.10.254.70|57574|Built outbound UDP connection 297 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/57574 (10.10.254.70/57574)
    6|May 06 2013|06:58:42|302016|192.168.152.21|53|10.10.254.70|52009|Teardown UDP connection 157 for outside:192.168.152.21/53 to inside:10.10.254.70/52009 duration 0:02:07 bytes 111
    6|May 06 2013|06:58:42|302016|192.168.152.21|53|10.10.254.70|56201|Teardown UDP connection 156 for outside:192.168.152.21/53 to inside:10.10.254.70/56201 duration 0:02:07 bytes 114
    6|May 06 2013|06:58:42|302016|192.168.160.21|53|10.10.254.70|56201|Teardown UDP connection 154 for outside:192.168.160.21/53 to inside:10.10.254.70/56201 duration 0:02:08 bytes 152
    6|May 06 2013|06:58:42|302016|192.168.160.21|53|10.10.254.70|52009|Teardown UDP connection 153 for outside:192.168.160.21/53 to inside:10.10.254.70/52009 duration 0:02:08 bytes 148
    6|May 06 2013|06:58:42|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:41|302015|192.168.152.21|53|10.10.254.70|54805|Built outbound UDP connection 296 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/54805 (10.10.254.70/54805)
    6|May 06 2013|06:58:41|302015|192.168.160.21|53|10.10.254.70|57574|Built outbound UDP connection 295 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/57574 (10.10.254.70/57574)
    6|May 06 2013|06:58:40|302015|192.168.160.21|53|10.10.254.70|54805|Built outbound UDP connection 294 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/54805 (10.10.254.70/54805)
    6|May 06 2013|06:58:40|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:39|302016|192.168.152.21|53|10.10.254.70|49838|Teardown UDP connection 149 for outside:192.168.152.21/53 to inside:10.10.254.70/49838 duration 0:02:07 bytes 165
    6|May 06 2013|06:58:39|302016|192.168.160.21|53|10.10.254.70|49838|Teardown UDP connection 142 for outside:192.168.160.21/53 to inside:10.10.254.70/49838 duration 0:02:08 bytes 220
    6|May 06 2013|06:58:38|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:37|302016|192.168.152.21|53|10.10.254.70|65386|Teardown UDP connection 138 for outside:192.168.152.21/53 to inside:10.10.254.70/65386 duration 0:02:07 bytes 105
    6|May 06 2013|06:58:37|302016|192.168.160.21|53|10.10.254.70|65386|Teardown UDP connection 136 for outside:192.168.160.21/53 to inside:10.10.254.70/65386 duration 0:02:08 bytes 140
    6|May 06 2013|06:58:36|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:35|302016|76.119.99.25|62111|10.10.254.70|64582|Teardown UDP connection 140 for outside:76.119.99.25/62111 to inside:10.10.254.70/64582 duration 0:02:04 bytes 220
    6|May 06 2013|06:58:34|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:33|302016|192.168.1.134|34097|10.10.254.70|64582|Teardown UDP connection 143 for outside:192.168.1.134/34097 to inside:10.10.254.70/64582 duration 0:02:02 bytes 56
    6|May 06 2013|06:58:33|302015|192.168.152.21|53|10.10.254.70|64940|Built outbound UDP connection 291 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/64940 (10.10.254.70/64940)
    6|May 06 2013|06:58:32|302016|213.199.179.150|443|10.10.254.70|64582|Teardown UDP connection 141 for outside:213.199.179.150/443 to inside:10.10.254.70/64582 duration 0:02:01 bytes 44
    6|May 06 2013|06:58:32|302015|192.168.160.21|53|10.10.254.70|64940|Built outbound UDP connection 290 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/64940 (10.10.254.70/64940)
    6|May 06 2013|06:58:32|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:32|302016|192.168.160.21|53|10.10.254.70|62327|Teardown UDP connection 133 for outside:192.168.160.21/53 to inside:10.10.254.70/62327 duration 0:02:07 bytes 148
    6|May 06 2013|06:58:32|302016|192.168.152.21|53|10.10.254.70|62327|Teardown UDP connection 131 for outside:192.168.152.21/53 to inside:10.10.254.70/62327 duration 0:02:08 bytes 111
    6|May 06 2013|06:58:31|302016|111.221.77.161|443|10.10.254.70|64582|Teardown UDP connection 101 for outside:111.221.77.161/443 to inside:10.10.254.70/64582 duration 0:02:14 bytes 88
    6|May 06 2013|06:58:31|302016|192.168.160.21|53|10.10.254.70|50601|Teardown UDP connection 132 for outside:192.168.160.21/53 to inside:10.10.254.70/50601 duration 0:02:07 bytes 136
    6|May 06 2013|06:58:31|302016|192.168.152.21|53|10.10.254.70|50601|Teardown UDP connection 130 for outside:192.168.152.21/53 to inside:10.10.254.70/50601 duration 0:02:08 bytes 102
    6|May 06 2013|06:58:31|302016|69.142.74.136|5370|10.10.254.70|64582|Teardown UDP connection 97 for outside:69.142.74.136/5370 to inside:10.10.254.70/64582 duration 0:02:14 bytes 88
    6|May 06 2013|06:58:30|302016|187.35.72.228|9426|10.10.254.70|64582|Teardown UDP connection 98 for outside:187.35.72.228/9426 to inside:10.10.254.70/64582 duration 0:02:13 bytes 36
    6|May 06 2013|06:58:30|302015|192.168.152.21|53|10.10.254.70|52963|Built outbound UDP connection 288 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/52963 (10.10.254.70/52963)
    6|May 06 2013|06:58:30|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:30|302015|192.168.152.21|53|10.10.254.70|50141|Built outbound UDP connection 287 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/50141 (10.10.254.70/50141)
    6|May 06 2013|06:58:30|302016|192.168.160.21|53|10.10.254.70|49975|Teardown UDP connection 129 for outside:192.168.160.21/53 to inside:10.10.254.70/49975 duration 0:02:07 bytes 160
    6|May 06 2013|06:58:30|302016|192.168.152.21|53|10.10.254.70|49975|Teardown UDP connection 127 for outside:192.168.152.21/53 to inside:10.10.254.70/49975 duration 0:02:08 bytes 120
    6|May 06 2013|06:58:29|302016|192.168.160.21|53|10.10.254.70|57658|Teardown UDP connection 128 for outside:192.168.160.21/53 to inside:10.10.254.70/57658 duration 0:02:07 bytes 136
    6|May 06 2013|06:58:29|302016|192.168.152.21|53|10.10.254.70|57658|Teardown UDP connection 126 for outside:192.168.152.21/53 to inside:10.10.254.70/57658 duration 0:02:08 bytes 102
    6|May 06 2013|06:58:29|302015|192.168.160.21|53|10.10.254.70|52963|Built outbound UDP connection 286 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/52963 (10.10.254.70/52963)
    6|May 06 2013|06:58:29|302015|192.168.160.21|53|10.10.254.70|50141|Built outbound UDP connection 285 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/50141 (10.10.254.70/50141)
    6|May 06 2013|06:58:28|302014|184.64.37.48|80|10.10.254.70|34457|Teardown TCP connection 257 for outside:184.64.37.48/80 to inside:10.10.254.70/34457 duration 0:00:30 bytes 0 SYN Timeout
    6|May 06 2013|06:58:28|302014|184.64.37.48|443|10.10.254.70|34456|Teardown TCP connection 256 for outside:184.64.37.48/443 to inside:10.10.254.70/34456 duration 0:00:30 bytes 0 SYN Timeout
    6|May 06 2013|06:58:28|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:27|302014|184.64.37.48|53578|10.10.254.70|34455|Teardown TCP connection 254 for outside:184.64.37.48/53578 to inside:10.10.254.70/34455 duration 0:00:30 bytes 0 SYN Timeout
    6|May 06 2013|06:58:27|302015|192.168.152.21|53|10.10.254.70|57349|Built outbound UDP connection 283 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/57349 (10.10.254.70/57349)
    6|May 06 2013|06:58:26|302015|192.168.152.21|53|10.10.254.70|54841|Built outbound UDP connection 282 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/54841 (10.10.254.70/54841)
    6|May 06 2013|06:58:26|302014|184.64.37.48|53578|10.10.254.70|34453|Teardown TCP connection 250 for outside:184.64.37.48/53578 to inside:10.10.254.70/34453 duration 0:00:30 bytes 0 SYN Timeout
    6|May 06 2013|06:58:26|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:26|302015|192.168.160.21|53|10.10.254.70|57349|Built outbound UDP connection 281 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/57349 (10.10.254.70/57349)
    6|May 06 2013|06:58:25|302015|192.168.160.21|53|10.10.254.70|54841|Built outbound UDP connection 280 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/54841 (10.10.254.70/54841)
    6|May 06 2013|06:58:25|302016|192.168.160.21|53|10.10.254.70|63377|Teardown UDP connection 118 for outside:192.168.160.21/53 to inside:10.10.254.70/63377 duration 0:02:07 bytes 236
    6|May 06 2013|06:58:25|302016|192.168.152.21|53|10.10.254.70|63377|Teardown UDP connection 104 for outside:192.168.152.21/53 to inside:10.10.254.70/63377 duration 0:02:08 bytes 177
    6|May 06 2013|06:58:24|302016|192.168.160.21|53|10.10.254.70|53894|Teardown UDP connection 107 for outside:192.168.160.21/53 to inside:10.10.254.70/53894 duration 0:02:07 bytes 164
    6|May 06 2013|06:58:24|302016|192.168.160.21|53|10.10.254.70|53008|Teardown UDP connection 106 for outside:192.168.160.21/53 to inside:10.10.254.70/53008 duration 0:02:07 bytes 164
    6|May 06 2013|06:58:24|302016|192.168.160.21|53|10.10.254.70|62979|Teardown UDP connection 105 for outside:192.168.160.21/53 to inside:10.10.254.70/62979 duration 0:02:07 bytes 164
    6|May 06 2013|06:58:24|302016|192.168.152.21|53|10.10.254.70|53894|Teardown UDP connection 92 for outside:192.168.152.21/53 to inside:10.10.254.70/53894 duration 0:02:08 bytes 123
    6|May 06 2013|06:58:24|302016|192.168.152.21|53|10.10.254.70|53008|Teardown UDP connection 91 for outside:192.168.152.21/53 to inside:10.10.254.70/53008 duration 0:02:08 bytes 123
    6|May 06 2013|06:58:24|302016|192.168.152.21|53|10.10.254.70|62979|Teardown UDP connection 90 for outside:192.168.152.21/53 to inside:10.10.254.70/62979 duration 0:02:08 bytes 123
    6|May 06 2013|06:58:24|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:24|302016|192.168.160.21|53|10.10.254.70|54579|Teardown UDP connection 100 for outside:192.168.160.21/53 to inside:10.10.254.70/54579 duration 0:02:07 bytes 128
    6|May 06 2013|06:58:24|302016|192.168.152.21|53|10.10.254.70|54579|Teardown UDP connection 86 for outside:192.168.152.21/53 to inside:10.10.254.70/54579 duration 0:02:08 bytes 96
    6|May 06 2013|06:58:22|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:22|302016|192.168.160.21|53|10.10.254.70|50518|Teardown UDP connection 94 for outside:192.168.160.21/53 to inside:10.10.254.70/50518 duration 0:02:05 bytes 80
    6|May 06 2013|06:58:22|302016|192.168.152.21|53|10.10.254.70|50518|Teardown UDP connection 93 for outside:192.168.152.21/53 to inside:10.10.254.70/50518 duration 0:02:05 bytes 80
    6|May 06 2013|06:58:22|302016|192.168.160.21|53|10.10.254.70|61054|Teardown UDP connection 89 for outside:192.168.160.21/53 to inside:10.10.254.70/61054 duration 0:02:06 bytes 74
    6|May 06 2013|06:58:22|302016|192.168.152.21|53|10.10.254.70|61054|Teardown UDP connection 88 for outside:192.168.152.21/53 to inside:10.10.254.70/61054 duration 0:02:06 bytes 74
    6|May 06 2013|06:58:20|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:19|302016|192.168.160.21|53|10.10.254.70|49862|Teardown UDP connection 124 for outside:192.168.160.21/53 to inside:10.10.254.70/49862 duration 0:02:01 bytes 41
    6|May 06 2013|06:58:19|302016|192.168.160.21|53|10.10.254.70|52028|Teardown UDP connection 123 for outside:192.168.160.21/53 to inside:10.10.254.70/52028 duration 0:02:01 bytes 41
    6|May 06 2013|06:58:19|302016|192.168.152.21|53|10.10.254.70|52028|Teardown UDP connection 122 for outside:192.168.152.21/53 to inside:10.10.254.70/52028 duration 0:02:01 bytes 41
    6|May 06 2013|06:58:19|302016|192.168.152.21|53|10.10.254.70|49862|Teardown UDP connection 121 for outside:192.168.152.21/53 to inside:10.10.254.70/49862 duration 0:02:01 bytes 41
    6|May 06 2013|06:58:19|302016|192.168.160.21|53|10.10.254.70|63772|Teardown UDP connection 120 for outside:192.168.160.21/53 to inside:10.10.254.70/63772 duration 0:02:01 bytes 41
    6|May 06 2013|06:58:19|302016|192.168.152.21|53|10.10.254.70|63772|Teardown UDP connection 119 for outside:192.168.152.21/53 to inside:10.10.254.70/63772 duration 0:02:01 bytes 41
    6|May 06 2013|06:58:19|302016|192.168.160.21|53|10.10.254.70|55207|Teardown UDP connection 117 for outside:192.168.160.21/53 to inside:10.10.254.70/55207 duration 0:02:01 bytes 40
    6|May 06 2013|06:58:19|302016|192.168.152.21|53|10.10.254.70|55207|Teardown UDP connection 116 for outside:192.168.152.21/53 to inside:10.10.254.70/55207 duration 0:02:01 bytes 40
    6|May 06 2013|06:58:19|302016|192.168.160.21|53|10.10.254.70|51370|Teardown UDP connection 115 for outside:192.168.160.21/53 to inside:10.10.254.70/51370 duration 0:02:02 bytes 32
    6|May 06 2013|06:58:19|302016|192.168.152.21|53|10.10.254.70|51370|Teardown UDP connection 114 for outside:192.168.152.21/53 to inside:10.10.254.70/51370 duration 0:02:02 bytes 32
    6|May 06 2013|06:58:18|302016|192.168.160.21|53|10.10.254.70|54447|Teardown UDP connection 113 for outside:192.168.160.21/53 to inside:10.10.254.70/54447 duration 0:02:01 bytes 38
    6|May 06 2013|06:58:18|302016|192.168.152.21|53|10.10.254.70|54447|Teardown UDP connection 112 for outside:192.168.152.21/53 to inside:10.10.254.70/54447 duration 0:02:01 bytes 38
    6|May 06 2013|06:58:18|302016|192.168.160.21|53|10.10.254.70|53196|Teardown UDP connection 111 for outside:192.168.160.21/53 to inside:10.10.254.70/53196 duration 0:02:01 bytes 32
    6|May 06 2013|06:58:18|302016|192.168.152.21|53|10.10.254.70|53196|Teardown UDP connection 110 for outside:192.168.152.21/53 to inside:10.10.254.70/53196 duration 0:02:01 bytes 32
    6|May 06 2013|06:58:18|302016|192.168.160.21|53|10.10.254.70|59127|Teardown UDP connection 109 for outside:192.168.160.21/53 to inside:10.10.254.70/59127 duration 0:02:01 bytes 32
    6|May 06 2013|06:58:18|302016|192.168.152.21|53|10.10.254.70|59127|Teardown UDP connection 108 for outside:192.168.152.21/53 to inside:10.10.254.70/59127 duration 0:02:01 bytes 32
    6|May 06 2013|06:58:18|302016|157.55.130.158|443|10.10.254.70|64582|Teardown UDP connection 102 for outside:157.55.130.158/443 to inside:10.10.254.70/64582 duration 0:02:01 bytes 44
    6|May 06 2013|06:58:18|302016|126.159.50.221|5081|10.10.254.70|64582|Teardown UDP connection 95 for outside:126.159.50.221/5081 to inside:10.10.254.70/64582 duration 0:02:02 bytes 18
    6|May 06 2013|06:58:18|302015|192.168.152.21|53|10.10.254.70|57615|Built outbound UDP connection 277 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/57615 (10.10.254.70/57615)
    6|May 06 2013|06:58:18|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:17|302015|192.168.160.21|53|10.10.254.70|57615|Built outbound UDP connection 276 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/57615 (10.10.254.70/57615)
    6|May 06 2013|06:58:17|302014|65.183.143.163|10103|10.10.254.70|34448|Teardown TCP connection 203 for outside:65.183.143.163/10103 to inside:10.10.254.70/34448 duration 0:01:02 bytes 353 TCP FINs
    6|May 06 2013|06:58:17|302013|71.207.1.189|1761|10.10.254.70|34468|Built outbound TCP connection 275 for outside:71.207.1.189/1761 (71.207.1.189/1761) to inside:10.10.254.70/34468 (192.168.13.100/55721)
    6|May 06 2013|06:58:17|305011|10.10.254.70|34468|192.168.13.100|55721|Built dynamic TCP translation from inside:10.10.254.70/34468 to outside:192.168.13.100/55721
    6|May 06 2013|06:58:16|302014|184.37.189.185|60952|10.10.254.70|34447|Teardown TCP connection 202 for outside:184.37.189.185/60952 to inside:10.10.254.70/34447 duration 0:01:02 bytes 400 TCP FINs
    6|May 06 2013|06:58:16|302016|112.208.137.190|25040|10.10.254.70|64582|Teardown UDP connection 29 for outside:112.208.137.190/25040 to inside:10.10.254.70/64582 duration 0:02:08 bytes 184
    6|May 06 2013|06:58:16|302013|67.86.118.52|17365|10.10.254.70|34467|Built outbound TCP connection 274 for outside:67.86.118.52/17365 (67.86.118.52/17365) to inside:10.10.254.70/34467 (192.168.13.100/48446)
    6|May 06 2013|06:58:16|305011|10.10.254.70|34467|192.168.13.100|48446|Built dynamic TCP translation from inside:10.10.254.70/34467 to outside:192.168.13.100/48446
    6|May 06 2013|06:58:16|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:16|302016|37.229.14.159|5806|10.10.254.70|64582|Teardown UDP connection 28 for outside:37.229.14.159/5806 to inside:10.10.254.70/64582 duration 0:02:07 bytes 184
    6|May 06 2013|06:58:15|305012|10.10.254.70|34441|192.168.13.100|33964|Teardown dynamic TCP translation from inside:10.10.254.70/34441 to outside:192.168.13.100/33964 duration 0:01:30
    6|May 06 2013|06:58:15|302015|192.168.152.21|53|10.10.254.70|55062|Built outbound UDP connection 272 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/55062 (10.10.254.70/55062)
    6|May 06 2013|06:58:14|302015|192.168.160.21|53|10.10.254.70|55062|Built outbound UDP connection 271 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/55062 (10.10.254.70/55062)
    6|May 06 2013|06:58:14|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:12|302015|192.168.152.21|53|10.10.254.70|61073|Built outbound UDP connection 270 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/61073 (10.10.254.70/61073)
    6|May 06 2013|06:58:12|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:11|302015|192.168.160.21|53|10.10.254.70|61073|Built outbound UDP connection 268 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/61073 (10.10.254.70/61073)
    6|May 06 2013|06:58:10|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:10|302016|157.55.130.155|443|10.10.254.70|64582|Teardown UDP connection 31 for outside:157.55.130.155/443 to inside:10.10.254.70/64582 duration 0:02:01 bytes 18
    6|May 06 2013|06:58:10|302016|111.221.77.166|443|10.10.254.70|64582|Teardown UDP connection 30 for outside:111.221.77.166/443 to inside:10.10.254.70/64582 duration 0:02:01 bytes 18
    6|May 06 2013|06:58:08|302015|192.168.152.21|53|10.10.254.70|50088|Built outbound UDP connection 267 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/50088 (10.10.254.70/50088)
    6|May 06 2013|06:58:08|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:08|302016|10.10.254.70|68|10.10.254.254|67|Teardown UDP connection 19 for inside:10.10.254.70/68 to identity:10.10.254.254/67 duration 0:02:01 bytes 641
    6|May 06 2013|06:58:08|302016|255.255.255.255|68|10.10.254.254|67|Teardown UDP connection 17 for inside:255.255.255.255/68 to identity:10.10.254.254/67 duration 0:02:01 bytes 249
    6|May 06 2013|06:58:08|302016|0.0.0.0|68|255.255.255.255|67|Teardown UDP connection 16 for inside:0.0.0.0/68 to identity:255.255.255.255/67 duration 0:02:01 bytes 948
    6|May 06 2013|06:58:07|302015|192.168.160.21|53|10.10.254.70|50088|Built outbound UDP connection 265 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/50088 (10.10.254.70/50088)
    6|May 06 2013|06:58:06|302015|192.168.152.21|53|10.10.254.70|63993|Built outbound UDP connection 264 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/63993 (10.10.254.70/63993)
    6|May 06 2013|06:58:06|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:05|302015|192.168.160.21|53|10.10.254.70|63993|Built outbound UDP connection 263 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/63993 (10.10.254.70/63993)
    6|May 06 2013|06:58:04|302016|70.171.138.105|9016|10.10.254.70|64582|Teardown UDP connection 5 for outside:70.171.138.105/9016 to inside:10.10.254.70/64582 duration 0:02:01 bytes 18
    6|May 06 2013|06:58:04|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:03|302015|192.168.152.21|53|10.10.254.70|53734|Built outbound UDP connection 261 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/53734 (10.10.254.70/53734)
    6|May 06 2013|06:58:03|302013|174.91.241.232|53766|10.10.254.70|34458|Built outbound TCP connection 260 for outside:174.91.241.232/53766 (174.91.241.232/53766) to inside:10.10.254.70/34458 (192.168.13.100/26157)
    6|May 06 2013|06:58:03|305011|10.10.254.70|34458|192.168.13.100|26157|Built dynamic TCP translation from inside:10.10.254.70/34458 to outside:192.168.13.100/26157
    6|May 06 2013|06:58:03|302014|10.10.225.18|443|10.10.254.70|34451|Teardown TCP connection 221 for outside:10.10.225.18/443 to inside:10.10.254.70/34451 duration 0:00:30 bytes 0 SYN Timeout
    6|May 06 2013|06:58:02|302015|192.168.160.21|53|10.10.254.70|53734|Built outbound UDP connection 259 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/53734 (10.10.254.70/53734)
    6|May 06 2013|06:58:02|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:58:00|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:58|302013|184.64.37.48|80|10.10.254.70|34457|Built outbound TCP connection 257 for outside:184.64.37.48/80 (184.64.37.48/80) to inside:10.10.254.70/34457 (192.168.13.100/43659)
    6|May 06 2013|06:57:58|305011|10.10.254.70|34457|192.168.13.100|43659|Built dynamic TCP translation from inside:10.10.254.70/34457 to outside:192.168.13.100/43659
    6|May 06 2013|06:57:58|302013|184.64.37.48|443|10.10.254.70|34456|Built outbound TCP connection 256 for outside:184.64.37.48/443 (184.64.37.48/443) to inside:10.10.254.70/34456 (192.168.13.100/47534)
    6|May 06 2013|06:57:58|305011|10.10.254.70|34456|192.168.13.100|47534|Built dynamic TCP translation from inside:10.10.254.70/34456 to outside:192.168.13.100/47534
    6|May 06 2013|06:57:58|305012|10.10.254.70|34446|192.168.13.100|3562|Teardown dynamic TCP translation from inside:10.10.254.70/34446 to outside:192.168.13.100/3562 duration 0:01:00
    6|May 06 2013|06:57:58|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:58|302015|192.168.152.21|53|10.10.254.70|56866|Built outbound UDP connection 255 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/56866 (10.10.254.70/56866)
    6|May 06 2013|06:57:57|302013|184.64.37.48|53578|10.10.254.70|34455|Built outbound TCP connection 254 for outside:184.64.37.48/53578 (184.64.37.48/53578) to inside:10.10.254.70/34455 (192.168.13.100/4536)
    6|May 06 2013|06:57:57|305011|10.10.254.70|34455|192.168.13.100|4536|Built dynamic TCP translation from inside:10.10.254.70/34455 to outside:192.168.13.100/4536
    6|May 06 2013|06:57:57|302014|74.56.154.191|62152|10.10.254.70|34441|Teardown TCP connection 170 for outside:74.56.154.191/62152 to inside:10.10.254.70/34441 duration 0:01:11 bytes 6953 TCP FINs
    6|May 06 2013|06:57:57|302015|192.168.160.21|53|10.10.254.70|56866|Built outbound UDP connection 253 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/56866 (10.10.254.70/56866)
    6|May 06 2013|06:57:57|302013|50.72.9.170|12248|10.10.254.70|34454|Built outbound TCP connection 252 for outside:50.72.9.170/12248 (50.72.9.170/12248) to inside:10.10.254.70/34454 (192.168.13.100/39886)
    6|May 06 2013|06:57:57|305011|10.10.254.70|34454|192.168.13.100|39886|Built dynamic TCP translation from inside:10.10.254.70/34454 to outside:192.168.13.100/39886
    6|May 06 2013|06:57:56|302014|96.228.226.64|48962|10.10.254.70|34446|Teardown TCP connection 188 for outside:96.228.226.64/48962 to inside:10.10.254.70/34446 duration 0:00:58 bytes 363 TCP FINs
    6|May 06 2013|06:57:56|302015|192.168.152.21|53|10.10.254.70|59590|Built outbound UDP connection 251 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/59590 (10.10.254.70/59590)
    6|May 06 2013|06:57:56|302013|184.64.37.48|53578|10.10.254.70|34453|Built outbound TCP connection 250 for outside:184.64.37.48/53578 (184.64.37.48/53578) to inside:10.10.254.70/34453 (192.168.13.100/34856)
    6|May 06 2013|06:57:56|305011|10.10.254.70|34453|192.168.13.100|34856|Built dynamic TCP translation from inside:10.10.254.70/34453 to outside:192.168.13.100/34856
    6|May 06 2013|06:57:56|302013|24.202.182.58|43715|10.10.254.70|34452|Built outbound TCP connection 249 for outside:24.202.182.58/43715 (24.202.182.58/43715) to inside:10.10.254.70/34452 (192.168.13.100/33908)
    6|May 06 2013|06:57:56|305011|10.10.254.70|34452|192.168.13.100|33908|Built dynamic TCP translation from inside:10.10.254.70/34452 to outside:192.168.13.100/33908
    6|May 06 2013|06:57:56|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:55|302015|192.168.160.21|53|10.10.254.70|59590|Built outbound UDP connection 247 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/59590 (10.10.254.70/59590)
    6|May 06 2013|06:57:55|302015|192.168.152.21|53|10.10.254.70|63756|Built outbound UDP connection 246 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/63756 (10.10.254.70/63756)
    6|May 06 2013|06:57:54|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:54|302015|192.168.160.21|53|10.10.254.70|57967|Built outbound UDP connection 245 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/57967 (10.10.254.70/57967)
    6|May 06 2013|06:57:54|302014|10.10.225.18|443|10.10.254.70|34450|Teardown TCP connection 209 for outside:10.10.225.18/443 to inside:10.10.254.70/34450 duration 0:00:30 bytes 0 SYN Timeout
    6|May 06 2013|06:57:54|302014|10.10.225.18|443|10.10.254.70|34449|Teardown TCP connection 207 for outside:10.10.225.18/443 to inside:10.10.254.70/34449 duration 0:00:30 bytes 0 SYN Timeout
    6|May 06 2013|06:57:54|302015|192.168.160.21|53|10.10.254.70|63756|Built outbound UDP connection 244 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/63756 (10.10.254.70/63756)
    6|May 06 2013|06:57:53|302015|192.168.152.21|53|10.10.254.70|57967|Built outbound UDP connection 243 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/57967 (10.10.254.70/57967)
    6|May 06 2013|06:57:52|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:50|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:49|302015|192.168.160.21|53|10.10.254.70|54304|Built outbound UDP connection 241 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/54304 (10.10.254.70/54304)
    6|May 06 2013|06:57:48|302015|192.168.152.21|53|10.10.254.70|54304|Built outbound UDP connection 240 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/54304 (10.10.254.70/54304)
    6|May 06 2013|06:57:48|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:48|302015|192.168.160.21|53|10.10.254.70|65422|Built outbound UDP connection 238 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/65422 (10.10.254.70/65422)
    6|May 06 2013|06:57:47|302015|192.168.152.21|53|10.10.254.70|65422|Built outbound UDP connection 237 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/65422 (10.10.254.70/65422)
    6|May 06 2013|06:57:46|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:46|302015|192.168.160.21|53|10.10.254.70|50300|Built outbound UDP connection 236 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/50300 (10.10.254.70/50300)
    6|May 06 2013|06:57:46|302015|192.168.160.21|53|10.10.254.70|49286|Built outbound UDP connection 235 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/49286 (10.10.254.70/49286)
    6|May 06 2013|06:57:45|302015|192.168.152.21|53|10.10.254.70|50300|Built outbound UDP connection 234 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/50300 (10.10.254.70/50300)
    6|May 06 2013|06:57:45|302015|192.168.152.21|53|10.10.254.70|49286|Built outbound UDP connection 233 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/49286 (10.10.254.70/49286)
    6|May 06 2013|06:57:44|302020|10.10.254.70|1|192.168.152.21|0|Built outbound ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:43|305012|10.10.254.70|34440|192.168.13.100|17057|Teardown dynamic TCP translation from inside:10.10.254.70/34440 to outside:192.168.13.100/17057 duration 0:01:00
    6|May 06 2013|06:57:43|302015|192.168.160.21|53|10.10.254.70|57306|Built outbound UDP connection 231 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/57306 (10.10.254.70/57306)
    6|May 06 2013|06:57:42|305012|10.10.254.70|34439|192.168.13.100|24448|Teardown dynamic TCP translation from inside:10.10.254.70/34439 to outside:192.168.13.100/24448 duration 0:01:00
    6|May 06 2013|06:57:42|305012|10.10.254.70|34438|192.168.13.100|20628|Teardown dynamic TCP translation from inside:10.10.254.70/34438 to outside:192.168.13.100/20628 duration 0:01:00
    6|May 06 2013|06:57:42|302015|192.168.160.21|53|10.10.254.70|54646|Built outbound UDP connection 230 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/54646 (10.10.254.70/54646)
    6|May 06 2013|06:57:42|302015|192.168.152.21|53|10.10.254.70|57306|Built outbound UDP connection 229 for outside:192.168.152.21/53 (192.168.152.21/53) to inside:10.10.254.70/57306 (10.10.254.70/57306)
    6|May 06 2013|06:57:42|302021|192.168.152.21|0|10.10.254.70|1|Teardown ICMP connection for faddr 192.168.152.21/0 gaddr 10.10.254.70/1 laddr 10.10.254.70/1
    6|May 06 2013|06:57:42|302015|192.168.160.21|53|10.10.254.70|64481|Built outbound UDP connection 228 for outside:192.168.160.21/53 (192.168.160.21/53) to inside:10.10.254.70/64481 (10.10.254.70/64481)
    6|May 06 2013|06:57:41|302015|192.168.152.21|53|10.1

    First, make sure you correct the mask in the crypto ACL, per my other post.
    You should check with the other admin and make sure your crypto ACLs are exact mirrors of each other. It wouldn't be a bad idea to put a sniffer on the WAN side to see if you can detect asymmetrical operation (packets that should be encapsulated, but are not).
    It looks like the pool (192.168.100.0 255.255.255.248) is not part of a policy push from the other crypto endpoint.
    Are they actually using a /24 mask on their side, or is that an assumption on your part?
    Could it be that they are actually using a mask greater than /24 so as to not have an overlap?
    My concern was how a host on the far side with a /24 mask would initiate/respond to a host on your side. The host on their side would ARP your host believing it was directly reachable, due to the mask.
    Perhaps this might be resolved with "ip proxy-arp" configured on the internal interface of their router.
    Is their 192.168.100.0 /? network the connected network on the inside of their router, or buried deeper in their topology?

  • Multiple gateways for different Traffic on ASA 5510 firewall

    Hello,
    My network atthe moment is set up as:
    WAN, with three sites
    Site 1
    Site 2
    Site 3
    Site 1 is behind a non-Cisco firewall, which is connected to the internet via a Frame Relay link (using a Cisco 1721 router). We host a number of servers on the Internal network and DMZ's.
    All sites connect to the WAN using Cisco routers or switches.
    All internet traffic (IN and OUT) for all sites goes via the non-Cisco firewall.
    I am interested in the ASA 5510 with six interfaces.
    Using the ASA 5510 is it possible to set up two (2) internet connections, one via the Frame Relay and a second internet connection via an ADSL connection?
    Then, is it possible to direct the outward-bound traffic via specific gateways based upon either:
    (a) the type of traffic, say HTTP from users behind the firewall; or
    (b) the IP addresses of the host (i.e. users' PC versus the servers)
    Any assistance is welcome.
    Kind regards,
    IT@C

    yes you can do this with policy routing on the internet router in front of the firewall assuming that you are connecting both ISPs to that router. Also, remember that you can do vlans on the ASA. This may cut down on the # of interfaces that you use in your config.
    http://www.cisco.com/en/US/customer/products/ps6120/products_configuration_guide_chapter09186a0080636f89.html
    HTH, pls rate!

  • How to tell if GRE traffic is encrypted or not?

                       Hi Everyone
    Site A 
    Device A  has VPN Tunnel to
    Site B  Device B  over Wan link.
    Note Here Device A and B are end device and connect to ISP and do the encryption
    Site A  Device X which is internal device has simple GRE tunnel to Site Bs  internal device.
    My question is how can i find that this GRE tunnel gets encrypted at Device A or not?
    Currently encryption is only at Device A and B
    Thanks
    Mahesh

    Have you utilized some of the "show" and "debug" commands to verify that the IPSec security associations have been created and are in-place?  Some of the "debug" commands can show traffic hitting the crypto map.
    http://www.cisco.com/en/US/tech/tk583/tk372/technologies_tech_note09186a00800949c5.shtml#ipsec_sa
    What model routers are Device A and B?  You may be able to use something like RITE to mirror the traffic exiting the interface to a sniffer for a definitive "Doubting Thomas" proof. 
    http://www.cisco.com/en/US/docs/ios/12_4t/12_4t11/ht_rawip.html
    Ed

  • Passing URL parameter across Show detail item tabs

    Hi
    I have developed a sample jsr168 portlet which takes 1 input parameter and deployed it into the stand alone OC4J shipped with Jdev 10.1.3.4.0
    In the view controller i created a jspx page and added the portlet to it. The portlet is added under a ShowOnetab->ShowDetailItem component in the jspx page. I mapped the parameter which i pass in the url to the portlet in the pagedef file of the jspx page.
    The page works fine when i run it for the first time but if i were to move to another tab (ShowDetailItem) in the page and come back to the first tab the parameter is not registered even though it still exists in the url.
    Can somebody please sugget a way to persist URL parameters across tabs (ShowDetailItem) in the page.
    Thanks
    Nikhil

    Hi
    I have developed a sample jsr168 portlet which takes 1 input parameter and deployed it into the stand alone OC4J shipped with Jdev 10.1.3.4.0
    In the view controller i created a jspx page and added the portlet to it. The portlet is added under a ShowOnetab->ShowDetailItem component in the jspx page. I mapped the parameter which i pass in the url to the portlet in the pagedef file of the jspx page.
    The page works fine when i run it for the first time but if i were to move to another tab (ShowDetailItem) in the page and come back to the first tab the parameter is not registered even though it still exists in the url.
    Can somebody please sugget a way to persist URL parameters across tabs (ShowDetailItem) in the page.
    Thanks
    Nikhil

  • ExternalInterface: pass object reference across interface - how?

    I want to invoke methods on specific Javascript or
    ActionScript objects through calls across the ExternalInterface
    barrier. I would like to be able to do this either AS -> JS or
    JS -> AS.
    So I would like to pass an object reference across the
    interface. I'm not sure exactly what *is* getting passed (is it the
    serialized value of the object?), but it doesn't seem to work as an
    object reference.
    Here's a notional code sample. I have two symmetric object
    definitions, one in Javascript, one in ActionScript. During
    initialization, one instance of each object will be created and
    given a pointer to the other. Then they should each be able to
    invoke a method on the other to "do stuff".
    //----------[ code ]---------------------------------
    //--- Javascript ---
    class JSobj {
    var _asObj;
    JSobj.prototype.setASObj = function(obj) { _asObj = obj; }
    JSobj.prototype.callASObj = function(foo) {
    callASObjectMethod(_asObj, foo); } // does: _asObj.asMethod(foo);
    JSobj.prototype.jsMethod = function(bar) { /* do stuff */ }
    function callJSObjectMethod(obj, args) { obj.jsMethod(args);
    //--- ActionScript ---
    class ASobj {
    var _jsObj;
    public function set jsObj (obj:Object):void { _jsObj = obj;
    public function callJSObj (foo:Number):void {
    ExternalInterface.call("callJSObjectMethod", _jsObj, foo); } //
    does: _jsObj.jsMethod(foo);
    public function asMethod (bar:Number):void { /* do stuff */
    function callASObjectMethod (obj:Object, args) {
    obj.asMethod(args); }
    ExternalInterface.addCallback("callASObjectMethod",
    callASObjectMethod);
    //----------[ /code ]---------------------------------
    My workaround is to pass a uint as an opaque handle for the
    object, then resolve it when it is passed back. I'd rather pass a
    real reference if possible. Is there a way to pass object
    references between JS and AS?
    Thanks,
    -e-

    It's an object of a class that extends Object. I guess the answer is no then.
    Thanks for your answer

  • WAAS supprt for GRE traffic?

    We have WAAS running at both our data center and branch offices. We are connecting the WAAS device to the WAN routers directly and using WCCP for redirection. Some of our branch to data center traffic is running through GRE tunnels which begin/end in our branch and data center server switches. Question - can WAAS optimize traffic that is already in GRE tunnels?

    Greg,
    congiufre your redirection on the lan and wan interface service 61 on the lan interface and 62 on the wan interface. the wan interface in question is the gre tunnel.
    Regards.

  • Block / Deny ICMP Traffic cisco asa 5512-x

    hi expert
    I have cisco asa 5512x for configure as firewall and sslvpn.
    my customer want block/Deny icmp traffic from interface outside without block anything.
    i've configure form cli :
    icmp deny any outside
    but from outside can't open sslvpn url and asdm.

    Hi,
    Access for the Anyconnect/ASDM does not depend on the ICMP permit/deny commands on the ASA device.
    If you want to block the Pings to the ASA interface use the command:-
    icmp deny any outside etc.
    What do you mean by "i can ping from outside." Plzz explain.
    Thanks and Regards,
    Vibhor Amrodia

  • Inspect other firewall traffic using ASA 5585-X IPS SSP

    Is it possible to inspect traffic from other firewalls (say checkpoint firewall) apart from the one the ASA firewall the ASA IPS SSP is running on?
    Any help will be appreciated
    O.

    Hello Amit,
    Can you share :
    show ips detail
    show  module 1 details
    show service-policy
    Now, can you explain a little about this:
    on the switch end port tengig 1/8 is connected on nexus and specific vlans are monotored on that interface. But as of now i am not able to see any traffic on that interface. I dont know what wrong i am doing as this is the firstime on this IPS module. there is no ports connected on the firewall. only port connected is tengig 1/8 which is on the ips module which is in promisucs mode.
    I mean the firewall is the one that will redirect the traffic to the IPS sensor so not sure I follow you!
    Looking for some Networking Assistance? 
    Contact me directly at [email protected]
    I will fix your problem ASAP.
    Cheers,
    Julio Carvajal Segura
    http://laguiadelnetworking.com

  • Remote DNS server across ASA

    Hi guys,
    i am hoping if anyone can reply to my query below.
    We have got a new batch of servers and they reside on a separate VLAN 192.168.45.x 255.255.255.0
    Those  servers are required to be registered on the DNS server located on  the remote site (SITE 2). Please refer to the attached diagaram. We  also have a DNS server in our LAN but these new servers will need  to be in the domain in SITE 2
    Can anyone advise if need anythin else other than the following ACLs in the ASA firewall
    Access-list inside extended permit udp 192.168.45.0 255.255.255.0 host 10.10.100.150 eq 53
    Access-list inside extended permit tcp 192.168.45.0 255.255.255.0 host 10.10.100.150 eq 53
    Thanks
    jay

    The ACL entries above will allow DNS queries across the provider link from your local site. We are assuming matching entries allow the communications on the remote and and that routing etc. is all in place.. 
    You asked however about needing to be "registered" on the DNS server and in the domain. Also your diagram mentions the server is a DHCP server and you show it configured with the helper-address in your local core switch. DHCP uses TCP ports 67 and 68. When you say domain if you are talking about a Windows domain that is another set of ports.

Maybe you are looking for

  • Non SD invoice in COPA reporting and other expenses

    Hi Guys, With reference to my previous thread, is it the right way to assign non SD invoice to value fields thru PA transfer structure. What would be the business impact of this. and do we need to do assessment to this PA trasfer structure. And how t

  • ACL found but not expected.................

    I powered up my iMac (intel) and I got a blank white screen - up until this point it would be up and running in a second or two so this was a shock. I forced a shut down and had to restart a couple of times before I got a white screen with the apple

  • Help with IE6

    I am fairly new at websites, trying to make a site for my non-profit org (no $$ to hire a web guru). I have created the following site and try to make it visible to IE 6 and later users but no luck. The site is done with a few templates and I link th

  • Send RFQ to Vendor with all its Attached documents

    Hi, My requirement is to Develop Program which send(Email) RFQ data to Vendor along with all documents in attachment list of ME42. Standard solution: use ZENU output type but it do not send documents in attachment list. Your response is highly valuab

  • Load balancing over multiple E3s

    Hi all, For the same VP , can I make load balancing over multiple E3s connected bet the BPX 8600 and MGX 8850. Asking the question in another way: Is there a possibility for load balancing over multiple LSPs (multiple E3 interfaces) in Cell-Mode MPLS