4235 IDS Sensor monitoring several VLANS & TCP Reset (packet Injection)

Similar Questions

• IDS TCP reset

  
  

  The original Cisco sent sensors the TCP Reset for only the attacker host.

  However, later versions of Cisco sensors now send TCP resets both the aggressor and the victim in order to allow a better chance to close the connection.

  While the conflict is probably originated with which version of the Cisco probe writers were more familiar with.

  Given that the safe is out after the change had already intervened to sensors, SECURITY review most likely expect a response "sent both the atacking and attacked guests.

• TCP Reset and blocking

  I'm IPS-4270-20 configuration.

  I want to know how TCP Reset would reset a session without having an IP address.

  Then what interface would BOW orders blocking and rate limiting actions on managed devices.

  Kind regards

  Shahzad.

  Your switchports will be set to 'access' If you use the 'pair of inline physical interface' mode and it will be a trunk when you use "pair mode for vlan inline.

  And here's a post from Marc regarding the alternative tcp, its rarely need reset to:

  "Under most of the facilities the tcp reset interface replacement is not necessary.

  By default the ports TCP resets will come back on the same interface where the attack was detected.

  So if your interface promiscuity is connected to a 100 Mbps for tracking hub then the tcp reset will be sent back this same interface promiscuitee in the hub.

  Or if your interface promiscuity is connected to the span switch port, the tcp reset will be sent back the same interface of promiscuity in that span port.

  The question becomes is the sensor can send reset tcp, but if the switch will accept them. Various switches will accept from the span port tcp resets. Some switches require only an extra parameter on the extended configuration to tell the switch to allow incoming packets to the span port.

  BUT there are some switches that do NOT allow incoming packets of their span ports.

  These ituations are the reason for the replacement tcp reset the configuration of the interface.

  Need 2 remote sensing interfaces (one for surveillance of promiscuity and the used the other as just replacing tcp reset interface). The port command and control NOT allow as the other tcp reset interface.

  Connect to the interface promiscuity to the scope of the switch port. You configure the second interface as the alternate tcp reset interface of the first interface of promiscuity. Then plug the second interface on the switch of the saem (but do not have the 2nd one a span port).

  Now, when the sensor detects an attack on interface 1 it will NOT send tcp resets the interface 1, but rather will send the reset tcp on the 2nd interface.

  Given that the switch does not accept that the tcp resets since the span port you need of the second interface for tcp resets in the switch.

  It is also possible with taps where the taps (because the taps have no way to accept incoming packets).

  The alternative tcp reset interface configuration is ignored when it is configured for online tracking. It is used only with supervision of promiscuity. "

  Concerning

  Farrukh

• TCP resets

  Hi all

  I would like to get your comments on TCP resets sent from IPS running inline.  If the sensor is configured to deny the striker, refuse the connection or even refuse to package, is there a reason to send a TCP reset?  It seems to me that send a just reset confirms a valid IP address to the attacker.

  I can see the reason to reset if the IPS is running in "Promiscuous" mode, as you would like the host to severe inside the connection, but I do not see the advantage to send it when the IPS is already denied the connection in one form or another.

  Thoughts?

  Thank you

  Jeff S.

  The document says:

  Excerpt from http://www.cisco.com/en/US/docs/security/ips/5.1/configuration/guide/cli/cliEvAct.html

  Inline package deny action is represented as an action of package ignored in the alert. When a package inline deny occurs for a TCP connection, it is automatically upgraded to an inline action to refuse the connection and considered a refusal flow in the alert. If IPS denies a single packet, TCP continues to try to send this packet even again and again, so IPS denies any connection to ensure forever, he succeeds with sends it again.

  In the case of a connection line refuse, the IPS automatically sends a one-way TCP reset, which appears as a unidirectional reset TCP sent in the alert. When the SPI refuses the connection, it leaves an open connection on the client (usually the attacker) and the server (usually the victim). Too many open connections can lead to problems of resources on the victim. So the IPS sends a TCP delivered the victim to close the connection on the side of victim (usually the server), who keeps the resources of the victim. It also prevents a switch which would also connect to switch to a different network path and reach the victim. The IPS leaves the side attacking and rejects all traffic of it.

  Deny connection line and deny attacking pair victim line seems to have the same effect in the end, except that "Deny the perpetrator victim pair Inline" has an entry in the big "Deny".

  I hope that answers your query

• Disorders from several VLANS layer 2 layer 3

  Hello

  We have a layer switch 3 PowerConnect 6248 switch with multiple VLANs and active routing and also a layer 2 with a PowerConnect 5324 switch couple VLANS configured.  My goal is to have several VLANs, through level 3 for the layer 2 switch switch and all VLANS communicate between them.

  I followed the steps under the 3 layer + Layer section 2 to the title of this post:

  en.Community.Dell.com/.../19506015

  Unfortunately, it does not work.

  Here is my current set up and what I tried. My configuration is made via the web interface.

  The 6248 has VLAN 1, 64, 110, 150 and some other configured on the switch. The IP address of the 6248 is 192.168.64.1.  I'm trying to get some vlan 150 and 110 for the layer switch 2 for may I have some ports in the service of vlan vlan portion 150 and some 110.

  I have the IP routing (routing > IP > Interface Configuration) for vlan 150 as 192.168.150.1/24 and vlan 110 as 192.168.110.1/24.

  The 5324 is connected to the 6248 via a port (connected to the port 1 of the 5324 and 18 the 6248).  18 on the 6248 port is currently configured as general / Admit All/PVID 150.  Port 1 on the 5324 is currently configured for the same, but with a PVID of the 1.  150 of VLAN is sent without the label of the 6248 switch and vlan 110 is sent labeled.

  5324 switch is configured with an IP 192.168.150.2 and a gateway of 192.168.150.1.  I am able to access the web interface of the switch and connect machines in any port and get on the 192.168.150.0 subnet.  I created a vlan 110 on the 5324 and it the tag on ports 1 and 4, but port 4 will not any traffic to vlan 110. I tried many settings of belonging to port / vlan various which have all resulted in failure.

  I would greatly appreciate help on this.  It seems that such an easy feat, but I just can't understand it.  I have attached some pictures for people to see.

  

  

  

  

  

  

  

  

  

  I had figured it out.  I enabled Double VLAN on the trunk of the 6248 switch port and it works now.

• PowerConnect 5448 several VLANS between upstream and downstream server firewall

  I am struggling with what I thought, would be a simple task: route several subnets, each on one VLAN different, a firewall to a server.  In fact, I can't even pass the VLAN by default one still looking correct in the address tables and STP.

  Port 1 = firewall, VLAN 1 unidentified, 2 VLAN Tag, 1 PVID, tried the two trunk and general patterns

  17 = server NIC, VLAN 1 unidentified port, VLAN Tag, PVID 1 and 2 2, tried, tried both safe and general patterns

  VLAN 1 (firewall untagged) 10.84.195.0/24, 10.84.195.2 Interface IP and default gateway 10.84.195.1

  VLAN 2 (tag of firewall) 10.101.0.0/16, IP Interface 10.101.0.2 for 2 VLAN, firewall est.1

  The first thing I got was that something has not been properly marked by (Hyper-V, using SC VMM 2012 SP1) server or the firewall (Watchguard XTM 520).  Simple test: VPN Firewall, ping the switch to 10.101.0.2 with the tag, and works, remove the label and it doesn't.  Dynamic address table shows the two-way firewall.  Line 18 below appears right after the ping as planned on VLAN 2 with the same MAC address in VLAN 1.  In addition, I ping the switch 10.101.0.2 from the server and it works fine.  The table shows that VLAN 2 from the host (and 1 other VM), so it seems to me that everything is properly labeled.

  	15	VLAN 1	00907f8f571b	G1
  	16	VLAN 2	00155d1f1b07	G17
  	17	VLAN 2	001dd8b71c01	G17
  	18	VLAN 2	00907f8f571b	G1

  What I can't do, is ping through the switch to VLAN 2.  I can't ping my VPN server (10.101.20.1), and I can not ping to the gateway (10.101.0.1) from the server.  Note, it is not because of rules to firewall on each end.

  What Miss me?  I don't think I need a routing of layer 3 here, I don't have to go through VLAN, just have them several VLANS passes from one port to the other.

  Other things to note in case it is useful:

  -I have no connectivity not tag with everything else through the 10.84.195.xxx/24 switch.

  -If I delete the Tags VLAN port 2 1 trunk, I suddenly can ping the bridge VLAN 2 (10.101.0.1) from the server, although I suspect that it is because the same port is the default gateway for the switch.

  -For brevity, only 2 lines of the STP are listed below, but all ports are therefore based on the question of whether they are connected or not.

  G1 activated 128.1 Frw Desg P2P (STP) No. 4
  G2 activated 128.2 Dsbl Dsbl No. 100.

  -Latest firmware installed.

  -In addition, for people concerned about their security, I want to remove use VLAN by default in the future.

  Would it be possible for run you to stick your show output here in the forum.  In this way, we can take closer look at what you have configured.

  If you connect a desktop/laptop computer (with and intellectual property in the 10.101.0.0/16 range) in a port with the mode of access switchport VLAN 2 are you able to ping IP Interface 10.101.0.2 for 2 VLANS?  You could try to disconnect the firewall and the configurations for the port and work on getting through the switch with 2 terminals on a single VLAN.  Then, once this is confirmed as work connect the firewall back up with a trunk/general mode adding the VLAN necessary.

  You connect to the firewall on a layer 3 interface?  You need Layer 3 routing to reach the firewall correctly.

• WLC 2504 several VLANs multiple SSID

  I have three sites

  Data center management unit A - main - controller + Access - Point IP 172.16.x.x - Vlan 38

  Unit B - system managed by controller IP 172.17.x.x - Vlan 38 Access Points

  Unit C - system managed by controller IP 172.18.x.x - Vlan 38 Access Points

  In the network topology OSPF runs. We have several VLANS about 38 we wish to propagate through SSID, but maybe I'm not create more than 16. How to make a movement of the user of a unit for unit B how do mention Vlan IP for the user because it is 38 Vlan spread on each unit.

  UNIT A - UNIT B - UNIT C

  |                            |                               |

  172.16.X.X 172.17.X.X 172.18.X.X

  |                            |                               |

  VLAN 2-38 VLAN 2-38 VLAN 2-38

  |                            |                               |

  AP-1                          AP-2                        AP-3

  |                               |                               |

  User to user-1 user-2-3

  Need of advice and suggestion

  Hello Saad,

  If I understand your scenario, you have 2-38 or 16 VLAN for each unit. To ensure exactly the addressing specific IP must be assigned to the user, you must create groups of AP and add AP group particular AP. Let's say for the 1st floor that you used the subnet 192.168.1.0/24 and AP-group1 so all the first floor AP will be in AP group1. In addition to browse documents cisco you will get any idea on AP groups concept.

  In order to obtain roaming when users move from one unit to another unit we configure mobility in the controller. As OSPF is already running then you have reach-ability between the controller.

  Hope this information helps you.

• Several VLANs on bridges series 1300

  Hello

  I'm looking to plug a small building outside of a main bridge wireless campus. The building, I connect currently has two VLANs, the 1300 series bridges carry several VLANs via the wireless bridge? If so someone can point me to s document that explains it?

  Thank you very much

  Simon

  Hi Simon,.

  Yes they can, here is a link, I hope it helps you, look at the title of "bridge Configuration.

  http://www.Cisco.com/en/us/products/HW/wireless/ps4570/products_configuration_example09186a00801d0815.shtml

  Kind regards

  Milton Tizoc.

• 1252 config several VLAN trunking on ethernet not

  Hi all I am new to these forums, but have read some posts on configurations for an AP from 1252 to switch 2950.

  I have several VLANS andmultiple SSID configuration on my ap.  The switch knows the VLANS on the access point

  I think that in the config.

  When I put the 2950 in trunk mode on the port, the ap is conencted too, I can see no longer the access point. And none of my ssid / VLAN traffic through the stem net ether to the switch.  I think I have a problem with the config of the ap specifically either in the British Virgin Islands (do not understand this virtual port) or in bridge groups. (Never worked with foredeck groups.)

  The AP is in stand-alone mode.

  Here is my config on the side of the ap.

  interface Dot11Radio0

  no ip address

  no ip route cache

  !

  the cipher mode vlan 300 encryption tkip aes - ccm

  !

  broadcasting-key vlan 300 change 600 members-notice change in capacity

  !

  !

  SSID 101

  !

  SSID 300

  !

  countermeasure tkip duration of maintaining 120

  gain of antenna 0

  Base-1 speed, 0 2.0 5.5 11.0 6.0 12.0 9.0 18.0 24.0 36.0 48.0 54.0 m0. M1. M2. M3. M4. M5. M6. M7. M8. M9. M10. M11. M12. M13. M14. M15.

  root of station-role

  Bridge-Group 1

  Bridge-Group 1 block-unknown-source

  No source of bridge-Group 1-learning

  unicast bridge-Group 1-floods

  Bridge-Group 1 covering-disabled people

  !

  interface Dot11Radio0.100

  encapsulation dot1Q 100

  no ip route cache

  Bridge-group 100

  100 block-unknown-source bridge-group

  No source of bridge-group 100-learning

  No bridge group 100 unicast-flooding

  Bridge-group 100 covering people with reduced mobility

  !

  interface Dot11Radio0.300

  encapsulation dot1Q 300

  no ip route cache

  Bridge-group 255

  Bridge-group subscriber-loop-control 255

  Bridge-group 255 block-unknown-source

  No source of bridge-group 255-learning

  No bridge group 255 unicast-flooding

  Bridge-group 255 covering people with reduced mobility

  !

  interface Dot11Radio1

  no ip address

  no ip route cache

  !

  the cipher mode vlan 300 encryption tkip aes - ccm

  !

  broadcasting-key vlan 300 change 600 members-notice change in capacity

  !

  !

  SSID 101

  !

  SSID 300

  !

  countermeasure tkip duration of maintaining 120

  gain of antenna 0

  DFS block 3 Strip

  Speed - Basic6.0 9.0 12.0 18.0 36.0 24.0 48.0 54.0 m0. M1. M2. M3. M4. M5. M6. M7. M8. M9. M10. M11. M12. M13. M14. M15.

  channel SFR

  root of station-role

  !

  interface Dot11Radio1.100

  encapsulation dot1Q 100

  no ip route cache

  Bridge-group 100

  100 block-unknown-source bridge-group

  No source of bridge-group 100-learning

  No bridge group 100 unicast-flooding

  !

  interface Dot11Radio1.300

  encapsulation dot1Q 300

  no ip route cache

  Bridge-group 255

  Bridge-group subscriber-loop-control 255

  Bridge-group 255 block-unknown-source

  No source of bridge-group 255-learning

  No bridge group 255 unicast-flooding

  Bridge-group 255 covering people with reduced mobility

  !

  interface GigabitEthernet0

  no ip address

  no ip route cache

  automatic duplex

  automatic speed

  !

  interface GigabitEthernet0.51

  51 native encapsulation dot1Q

  no ip route cache

  Bridge-Group 1

  No source of bridge-Group 1-learning

  Bridge-Group 1 covering-disabled people

  !

  interface GigabitEthernet0.100

  encapsulation dot1Q 100

  no ip route cache

  Bridge-group 100

  No source of bridge-group 100-learning

  Bridge-group 100 covering people with reduced mobility

  !

  interface GigabitEthernet0.300

  encapsulation dot1Q 300

  no ip route cache

  Bridge-group 255

  No source of bridge-group 255-learning

  Bridge-group 255 covering people with reduced mobility

  !

  interface BVI1

  IP 10.131.10.70 255.255.255.0

  no ip route cache

  !

  51 of VLAN is what I'm trying to trunk more.  VLAN 100 is my networks vlan normal almost everything at the moment.  And my attempt to secure traffic wireless to a new vlan Vlan 300 more course on my local network.

  VLAN 51 has no ip address range

  IP VLAN 100 range is 10.131.10.0

  10.131.11.0 between 300 VLAN

  The routing goes to my switch 3750 core / router, but the access point is conencted to a 2950 namely shared resources to my layer distribution on a stack of 2975.  Once again the vlan 300 works on the 2975 stack and will pull dhcp if it is enabled.  Have not tried this on the 2950 yet, but I suspect it will also work based on the setting of the trunk on the s950 battery of 2975.

  In any case, I want to be able to do is have multiple VLANs configured on the AP (from most secure to least guarantee based on the capabilities of the equipment) and that traffic vlan tag go to my 3750 possibly for other guidelines.

  Here, any help would be greatly appreciated.

  Thank you for taking the time to read this.

  Sincerely,

  Kevin Pulford

  Systems administrator

  Harmon city, Inc.

  Yes, remove the vlan 51 can tell vlan 100 is the native, and there will be a link to bridge - Group 1.  Then change the switch port to vlan 100 native.  You should then be able to reach the access point via telnet/GUI.

  orders will be:

  config t

  No int dot11radio0.51

  No int dot11radio1.51

  No int g0.51

  int dot11radio0.100

  100 native encapsulation dot1q

  int dot11radio1.100

  100 native encapsulation dot1q

  int g0.100

  encapsulation dot1q 100 natively.

  To be sure, save reboot and wr mem.

• CSPM - 2.3.3i - S33 - exe IS NOT being handled IDS Sensor Version 3.1 (2) S25?

  After updating cspm2.3.3i to CSPM - 2.3.3i - S33 - exe of the magician. singnature update | next | load the cspm sensor signature update, I get messages warng to the sensor. order | status of the generations

  ------------------------------------------

  WARNING MESSAGES

  IDS Sensor Version 3.1 (2) specified S25 is newer than the last

  supported version. All the features are not supported.

  -----------------------------------------------

  What's wrong?

  It's just a warning message and a bug is cosmetic. You can ignore the message and click on generated orders to push the config.

  hope this helps,

  -Nairi

• SA520W VPN from Site to Site with several VLANs

  Hello

  I have a customer here with several VLANS in their places who wants to set up a VPN from Site to site between 2 devices SA520W. Unfortunately I can not find a way to set it up. In the VPN policy, I can choose between everything (which is not what I want, I want only traffict between subnets the routed via VPN), IP address unique, a beach (in a subnet) and a subnet itself - but only one. I don't find a way to configure several subnets in the selection of local traffic and remotely. Adding another IKE policy between the 2 sites does not either (which is good normally).

  Any ideas? Anything I'm doing wrong?

  Thank you for your help.

  Best regards

  Thomas

  I know that if you have an ASA or a router, you can define as VLANS to pass through the tunnel.

  Do not have access to a SA520W to test...

  A recommendation might be to post the question on the SMB community where they answered questions related to this product, just to check what other people did.

  Federico.

• Several VLAN, SSID

  I get to the point where my campus wireless network grows beyond the size of the subnet that I am uncomfortable dealing with.  I have a WISN and WCS and spin the latest IOS on each.  Is it possible to use several VLANS on a campus-wide SSID?

  Or, can I put the same SSID on both controllers and map it to two separate without causing problems roaming VIRTUAL networks?

  Thank you

  Eric

  Hi Eric,.

  Yes we do, and this feature is called grouping AP on WLC... Here is the sample configuration to do the same thing...

  http://www.Cisco.com/en/us/Tech/tk722/tk809/technologies_configuration_example09186a008073c723.shtml

  Concerning

  Surendra

• PowerConnect 2848 - several VLANS on the 1 port does not

  Hello everyone.

  I have a Dell PowerConnect 2848.  My router is a Netgear SRX5308. In the router, I've created several VLANs (VLAN ID 10 and 20) and would that pass to the ESXi server. If I connect the ESXi server directly to the router, everything works as expected. My VMs are picking up correct VLAN based on the parameters of ESXi.

  I need the 2848 between the two, because I need to add more devices and other servers with a VLAN specific.

  Currently I use port 25 for switch 2848.

  I put the switch to managed mode.

  I created switch-> VLAN-> belonging to a VLAN, VLAN ID 10 and 20.

  I select 10 VLANS and put the T on port 25.

  I select the VLAN 20 and put the T on port 25.  (I also tried to put a U on them, just to try, but did not work)

  But my virtual computer are not able to reach the DHCP on the router.

  Spanning Tree is enabled.

  I'm obviously missing something...

  I have already passed last week banging my head on this, but have not been able to pass traffic along.

  Help, please!

  So you're on the right track. If port 25 is facing the router? What port must face the ESXi Server? That port should also have VLAN 10 and 20 should be labelled.

• Affecting several VLANS to a Port Group

  Hi all!

  We have 2 switches farm of server connections to the host server. Each of our 8 ESX servers has 4 physical network adapters that support virtual machines. We have 2 network cards to each physical switch. We have a single vSwitch and 2 port VM groups set up on each ESX Server. We use and configuration active / standby in Port groups so we can control what physical move the VM speaks to. All 4 network cards are available for the Group of ports, with connections going to spend 1 active and forward to switch connections 2. It is reversed on the other group of Port.

  We have several VLANS associated with our data center. Is it possible to put the tag VLAN on 2 port groups VM to support multiple VLANs? Otherwise, I think we have to put up a pair of these groups of ports for each VIRTUAL local area network, we want to make it available to the virtual machines on each ESX Server. Is this correct? We have some circuits/EtherChannel enabled on switches that work properly. However, we cannot port VM groups to pass traffic unless label them us, and it seems we can only enter a VIRTUAL local area network in the area.

  Thank you in advance for your help!

  Steve Hurd, MCSE, CCNA, VCP

  To use the trunks that are coming in your ESX host, you must have your VLAN Tag somewhere along the way.  If you are not at the level of the switch (since you're trunking), you will need to do the vSwitch, either the level of the virtual machine.

  VSwitch level, this by creating exchanges and then marking at the level of the port group.  Marking that is currently happening in the ESX/vSwitch, and your vm must use the port suitable for group the VLAN they need to use.

  Your last option is to tag at the level of the virtual machine itself.  To do this, your vSwitch must use VLAN 4095 tag, which allows all the VLANS to pass through, and all tags are marked.  The portgroup vSwitch here is basically a tunnel and will allow the unmodified traffic, but now, you have to mark your VLAN of the NETWORK adapter in your virtual machine.  It is very effective if you have a large number of virtual machines.  The most practical method will be to create the VLAN-based exchanges at the vSwitch level and go from there.

  Unlettered, somewhere, communication will not incorrectly, as the physical switch will assume that all traffic not marked will even vlan uses unmarked frames (vlan native), and machines on that vlan can communicate each other.

  -KjB

• Network IDS Sensor/system and retrieval of Images

  Ok.. on this page:

  http://www.Cisco.com/Kobayashi/SW-Center/ciscosecure/IDs/crypto/

  Objective: I want to burn an image from the Images "system and recovering" rather than order a CD from recovery for IDS.

  Issues related to the:

  1 is it possible or not that you must order the recovery CD?

  2. I see that the files under 'System and recovery Images' are in the format tar.pkg. Is this based on Linux or Solaris? Can I use Red Hat Linux to extract this file and then burn it to a CD?

  3. If so, is - anyone know how to extract the file?

  -TKS.

  Answers:

  (1) No, you must order the recovery CD.

  (2) there are 2 types of files: System and recovery.

  The system Images (- sys-) are used only for the installation of sensors that support ROMMON (like the 4215 IDS, IPS-4240 and IPS-4255). The sensors supporting ROMMON have no CDROM drives, and so the image must be tftpd to the sensor through ROMMON.

  System Images are used for recovery after disaster where the compactflash/hard disk from the sensor has been severely damaged or a new white compactflash/hard disk was placed in the sensor.

  Recovery (r) - Inages updated only the probe recovery Partition. They must be installed from a running Application Partition. The .pkg is a special Cisco IDS application-specific extension. There are special methods for unpacking and installation of the unerlying files.

  In ordinary situations the user will constantly update their software to sensor by the normal process of upgrade using large updates (- shift-), minor updates (- min-), Service Pack (sp) - or Signature updates (-- GIS).

  It isn't that where the effective Partition becomes corrupt that a user must always start on the recovery Partition and load a new Partition of Application.

  Most of the users will never update their recovery Partition. Thus, users who have purchased the IDS-4235 for example with the 4.0 software (1) will be a 4.0 (1) recovery Image. If they later upgraded to 4.1 (1) and the experience of corruption then they can always start the recovery Partition and reload 4.0 (1). If they do not want to return to 4.0 (1) provide us a recovery Image to update the Partition recovery to 4.1 (1).

  The only time wherever a recovery CD is really necessary is when the user goes from 3.x, 4.x, because of the drastic change between the 2 versions, or if the recovery Partition has also been damaged, or if you use a blank hard drive.

  3.

  I don't think the recovery or System Images contains the files needed to create a recovery CD. If I just remember additional files have been added to the recovery CD to make it bootable, which were not necessary on the system image or recovery since they were based on a sensor that was already underway.