1. 15 Aug, 2006 2 commits
  2. 09 Dec, 2005 1 commit
  3. 02 Nov, 2005 1 commit
  4. 13 Oct, 2005 1 commit
  5. 16 Aug, 2005 1 commit
  6. 15 Jun, 2005 1 commit
    • Robert Ricci's avatar
      Add a PRUNE_VLANS option, which prevents us from creating VLANs on · 5d27bc6b
      Robert Ricci authored
      switches that don't need to have them.
      We always create VLANs on the leader, though, so that it can be used
      as a sort of global list of what VLANs are available, and is
      atomically lockable.
      Makes some changes to the private VLAN code which are not yet well
      tested - but that's okay, because no one uses private VLANs right now.
  7. 22 Apr, 2005 1 commit
  8. 27 Jan, 2005 1 commit
  9. 21 Dec, 2004 1 commit
  10. 03 Dec, 2004 1 commit
  11. 01 Dec, 2004 1 commit
    • Robert Ricci's avatar
      Add user-visible support for trunking. · cfdf5c00
      Robert Ricci authored
      Added support for Cisco switches to enable and disable trunking for a
      Added two new command-line options:
      -N <port> <vlans>
      	Enable trunking on a port, allowing the given list of VLANs to
      	cross the trunk
      -U <port>:
      	Disable trunking for the port
      This functionality is needed for Mike's firewall support.
  12. 30 Nov, 2004 1 commit
  13. 10 Nov, 2004 1 commit
  14. 09 Sep, 2004 1 commit
  15. 22 Oct, 2003 1 commit
    • Robert Ricci's avatar
      Change the way the switch modules for snmpit get their configuration · c069a419
      Robert Ricci authored
      information. Rather than pass it all in, which was getting very
      cumbersome, and inconsistent between Cisco and Intel switches, the
      modules query the database themselves (via a new function in
      Also in this commit are two new options for switch stacks - the
      ability to specify minimum and maximum VLAN number to use.
  16. 06 Oct, 2003 1 commit
  17. 04 Aug, 2003 1 commit
  18. 28 Apr, 2003 1 commit
  19. 17 Mar, 2003 1 commit
  20. 14 Mar, 2003 1 commit
  21. 07 Mar, 2003 1 commit
  22. 03 Mar, 2003 1 commit
  23. 18 Feb, 2003 1 commit
  24. 10 Feb, 2003 1 commit
  25. 07 Feb, 2003 2 commits
  26. 06 Feb, 2003 1 commit
  27. 17 Jan, 2003 1 commit
    • Robert Ricci's avatar
      New features: · 2d7b6b82
      Robert Ricci authored
          Accept [switch.]<module>/<port> format for ports, so that we can
      	deal with ports not in the database (mostly for my own
      	debugging sanity.)
          A -n option that prevents assign from changing hardware settings
          	(though, unlike TESTMODE, does read some information from
      	the switches)
          Private VLAN support, through the -x,-y, and -z switches. There
      	are only 5 letters of the alphabet left, so I've given up on
      	memnonic switches.
          Worked a bit on making VLAN deletion more efficient, but with
          	little sucess
      Private VLANs work like so:
      Make a primary private VLAN with:
      snmpit -m myvlan-primary -y primary
      Attach a community VLAN to it like so:
      snmpit -m myvlan-community -y community -x myvlan-primary -z cisco2.1/15
      Put some ports into the community VLAN:
      snmpit -m myvlan-community pc1:0 pc2:0
  28. 10 Jan, 2003 1 commit
  29. 05 Aug, 2002 1 commit
  30. 16 Jul, 2002 1 commit
  31. 07 Jul, 2002 1 commit
  32. 24 Jun, 2002 2 commits
  33. 19 Jun, 2002 1 commit
  34. 17 Jun, 2002 1 commit
    • Robert Ricci's avatar
      Made some functions that previously took only a single port or VLAN · 13381879
      Robert Ricci authored
      take more than one. This can increase efficiency, since, for example,
      we now only have to lock the VLAN edit buffer once when tearing down
      an experiment, instead of once per VLAN. There are still other
      functions (setVlanOnTrunks comes to mind) that could benefit from this
      These optimization have been made only for Ciscos - minimal changes
      necessary to keep Intel support working were made, but they will still
      have the same old slow behavior.
  35. 21 Feb, 2002 1 commit
    • Robert Ricci's avatar
      Actually call the code to pick which VLANs are allowed on which trunk. · afb28fde
      Robert Ricci authored
      When dealing with trunks, since they may be EtherChannels, we have to
      make another lookup on the switch to get the ifIndex for the whole
      channel - can't just use the ifIndex of one of the ports like you
      can from the Cisco CLI.
      These changes make snmpit slightly slower - it now has to get more information
      from the switches when it's going to create or delete VLANs. However, this
      is on the order of fractions of seconds, so it shouldn't be too noticable.
  36. 20 Feb, 2002 1 commit
    • Robert Ricci's avatar
      Code for picking which VLANs are allowed to go across which trunks. · 11e0ea5f
      Robert Ricci authored
      As much of it as possible switch-independant, and put in snmpit_lib.
      Should work for arbitrarily complicated switch toplogies, as long as
      there are not multiple trunks between two switches. (Multiple ports
      combined into one trunk are fine, however.)
      As a result of this, VLAN creations and deletions now need to operate
      on all switches, not just on the ones that have ports in the VLAN.
      This is because the traffic may have to traverse switches that have no
      ports in the VLAN to reach other switches that do.
      Not called yet. I've done simple testing, but need to do more, as this
      could get us into major trouble if it has bugs.
  37. 28 Jan, 2002 1 commit