1. 21 Sep, 2009 1 commit
  2. 20 May, 2009 1 commit
  3. 25 May, 2007 1 commit
  4. 01 Dec, 2006 1 commit
  5. 28 Nov, 2006 1 commit
  6. 14 Sep, 2005 2 commits
  7. 31 Aug, 2005 1 commit
  8. 25 Apr, 2005 1 commit
  9. 15 Apr, 2005 1 commit
  10. 04 Apr, 2005 1 commit
    • Timothy Stack's avatar
      · 463ee6b1
      Timothy Stack authored
      Mote and robot related stuff.  The main thing is the addition of relay
      capabilities to capture and related things.
      
      	* GNUmakefile.in: Add the capture and tip subdirectories to the
      	client and client-install targets.
      
      	* configure, configure.in, config.h.in: Detect srandomdev() for
      	capture and add "mote/newmote" script.
      
      	* capture/GNUmakefile.in, capture/capture.c: Add "relay"
      	capabilities to capture.
      
      	* capture/capquery.c: Query the capserver for the relay receiver's
      	port number.
      
      	* capture/capserver.c: Small hack to return the port number
              for a node.
      
      	* db/libdb.pm.in, db/xmlconvert.in: Add virt_tiptunnels table.
      
      	* event/program-agent/program-agent.c: Change log file names to
      	something a little more user-friendly.  Add a "MODIFY" event
      	handler that lets the user set agent attributes (command, tag,
      	timeout) without having to run a program.
      
      	* event/sched/GNUmakefile.in, event/sched/console-agent.cc,
      	event/sched/console-agent.h, event/sched/event-sched.c: Add
      	console agents that can be used to snapshot a section of the
      	capture log file.
      
      	* event/sched/node-agent.cc: Some minor cleanup.
      
      	* event/sched/simulator-agent.cc, event/sched/simulator-agent.h:
      	Add the config data to the report mail.  Add a "RESET" event
      	handler that runs "loghole clean".  Save the report mail in a file
      	so it gets archived with the rest of the logs.
      
      	* lib/libtb/tbdefs.h: Add CONSOLE object type.
      
      	* mote/GNUmakefile.in, mote/newmote: Add newmote script, just a
      	quick hack to add motes to the DB.
      
      	* mote/tbuisp.in: Add another backend for loading motes through
      	their relay capture server.
      
      	* robots/mtp/mtp_dump.c: Dump the min/max values for x and y,
      	handy for figuring out the bounds of the camera.
      
      	* sql/database-fill.sql: Change the RELOAD-MOTE/SHUTDOWN ->
      	ALWAYSUP/SHUTDOWN mode transition to ALWAYSUP/ISUP since stated
      	doesn't seem to run triggers after a state change by a mode
      	transition.
      
      	* tbsetup/tbreport.in: Change the ordering of the eventlist so it
      	displays event-sequences appropriately.
      
      	* tbsetup/ns2ir/GNUmakefile.in, tbsetup/ns2ir/console.tcl,
      	tbsetup/ns2ir/node.tcl, tbsetup/ns2ir/parse.tcl.in,
      	tbsetup/ns2ir/sim.tcl.in: Add a "console" agent that represents
      	the serial console for a node.
      
      	* tbsetup/ns2ir/sequence.tcl: Add an "append" method so it is
      	easier to build sequences dynamically.
      
      	* tbsetup/ns2ir/topography.tcl: Make checkdest available to
      	regular users.
      
      	* tip/GNUmakefile.in, tip/tiptunnel.c: Add support for uploading a
      	file to a relay version of capture and exporting the end
      	connection as a pty.
      
      	* tmcd/decls.h, tmcd/common/libsetup.pm: Bump version number since
      	the dosubnodelist change is not backwards compatible.
      
      	* tmcd/tmcd.c: Make dosubnodelist and dosubconfig callable even
      	when a node isn't allocated.  Add dotiptunnels command that
      	returns which serial consoles are to be mounted on a node.  Add
      	mote version of subconfig that returns information needed to
      	startup the relay version of capture.
      
      	* tmcd/common/bootsubnodes: For motes, startup the relay version
      	of capture (XXX stargate specific).
      
      	* tmcd/common/libsetup.pm, tmcd/common/libtmcc.pm,
      	tmcd/common/config/rc.config, tmcd/common/config/rc.tiptunnels:
      	Client side changes for mounting another nodes serial line.
      
      	* tmcd/common/rc.bootsetup: Always boot the subnodes, even when
      	free.  This is used for motes since their capture needs to be up
      	for reloading at the time.
      
      	* tmcd/linux/ixpboot: Shuffle some code around so the script
      	doesn't fail if the ixp isn't allocated.
      
      	* utils/loghole.in: Add "digest.out" and "report.mail" as global
      	logs to be saved in archives and display the "report.mail" file
      	when showing a loghole archive.
      
      	* xmlrpc/emulabserver.py.in: Scrub more of the return values to
      	get rid of "None"s.
      463ee6b1
  11. 10 Nov, 2004 1 commit
  12. 29 Apr, 2003 1 commit
  13. 10 Sep, 2002 1 commit
    • Chad Barb's avatar
      · 9280811f
      Chad Barb authored
      Added makefile mojo to install "tip has been deprecated" script
      in place of tip in testbed.
      9280811f
  14. 16 Aug, 2002 1 commit
    • Chad Barb's avatar
      · 2e142429
      Chad Barb authored
      Changed format for passing in command to execute
      to use @s instead of %s..
      also removed exteraneous output when not using -v.
      2e142429
  15. 09 Jul, 2002 1 commit
    • Chad Barb's avatar
      · 8897a657
      Chad Barb authored
      Added "console" binary target for tiptunnel... use in the same way as "tip"
      (e.g. logged into plastic).
      8897a657
  16. 08 Jul, 2002 1 commit
  17. 28 Jun, 2002 1 commit
  18. 26 Jun, 2002 1 commit
  19. 11 Jun, 2002 1 commit
  20. 05 Apr, 2002 2 commits
    • Chad Barb's avatar
      Added SSL to capture (enabled with -DWITHSSL) · 2e536ba3
      Chad Barb authored
      To tip (or tiptunnel on a normal acl,) capture behaves the same.
      However, if a client connects and presents "USESSL" as the first six characters of their
      connection key, both sides initiate SSL negotiation.
      The server then attempts to get the key again. The second one is used for the check.
      
      SSL initialization is done on the first attempt by a client to connect via SSL.
      Capture assumes $(prefix)/etc/capture/cert.pem contains its certificate unless
      the '-c <certfile>' option is used.. if the certificate is not found or invalid, that
      connection fails, but normal connections will still succeed (and it will try to find the file
      again, next time an SSL connection is attempted.)
      
      On the client side, tiptunnel only uses ssl if there is a "ssl-server-cert:"
      property in the acl file. This is the SHA hash of the certificate that the capture server is
      expected to have (in hex.) If the certificate presented by the server does not hash to the
      same value, the connection is dropped.
      2e536ba3
    • Chad Barb's avatar
      · 86c3a23a
      Chad Barb authored
      Added "fakie telnet" to tunnel; tells client to not act stupid (no local echo and no line-at-a-time,)
      and filters out client telnet replies so they don't blow the server's mind.
      86c3a23a
  21. 02 Apr, 2002 1 commit
    • Chad Barb's avatar
      · b05398fe
      Chad Barb authored
      Tiptunnel can now take "ssl-server-cert:" property from the ACL file,
      which is a SHA hash of the expected server certificate.
      
      (this is used to verify the server's identity,
      thus precluding man-in-the-middle attacks.)
      
      If no "ssl-server-cert:" is in the ACL,
      it will revert to using a normal TCP connection.
      
      In this version, authentication is still the same (even over SSL.)
      (next step: add SSL to capture server.)
      b05398fe
  22. 29 Mar, 2002 1 commit
    • Chad Barb's avatar
      The tip tunnel.. · 025a6441
      Chad Barb authored
      Essentially tip, but instead of presenting a tty, it opens a tunnel port that (for instance)
      telnet can talk to. Example (on credit):
      
      tiptunnel /var/log/tiplogs/pc1.acl telnet
      
      Will open up a local port then fork/exec telnet with "localhost" and the tunnel port number as arguments.
      (Functionally equivalent to "tip pc1", only with telnet escape sequences)
      
      A later version of this program is what users will likely download for the quick-tip-through-the-web scheme.
      (next step: SSL)
      025a6441
  23. 29 Aug, 2001 1 commit
    • Leigh Stoller's avatar
      Fixup capture/tip/power_rpc27 so that capture returns a positive · ed55f418
      Leigh Stoller authored
      ack/nak for a connection so that the connecting process knows what the
      hell is going on. Turned out to be necessary for power control since
      we do that in parallel, and because it stays busy for 10 seconds on
      each power control. I think we will end up revisiting this at some
      point, adding blocking connections instead of connect/fail status.
      ed55f418
  24. 20 Aug, 2001 1 commit
  25. 16 Aug, 2001 2 commits
  26. 14 Aug, 2001 1 commit
    • Leigh Stoller's avatar
      Move .acl file into tiplogs directory since nothing in /dev/tip · 3a67ca5f
      Leigh Stoller authored
      is actually used anymore.
      Added a "generic" entry to /etc/remote so that we do not need tip
      entries for each node; they all look the same anyway.
      Change tip to lookup up generic /etc/remote entry, just to make
      tip happy. The acl file comes from the tiplogs directory, as
      set in the header file.
      3a67ca5f
  27. 13 Aug, 2001 1 commit
  28. 09 Aug, 2001 1 commit
  29. 31 Jul, 2001 1 commit
  30. 24 Jul, 2001 1 commit
    • Leigh Stoller's avatar
      Checkpoint new version of capture/tip that is sockets based instead · 34499cb6
      Leigh Stoller authored
      of pty/tty based (since they have several annoying problems
      associated). Note that permission is granted via the use of an "acl"
      file; /dev/tip/machine.acl, which must be set to the group of the
      project the node is in, so the user can read out the process id number
      and the random bits that are used by capture to grant permission to
      use (tip sends the random bits across first thing). This handshake is
      due to change to a request/challenge scheme as described by Dave in
      email to the testbed list.
      34499cb6
  31. 26 Jun, 2001 1 commit
  32. 05 Jan, 2001 1 commit
  33. 04 Jan, 2001 2 commits
  34. 03 Jan, 2001 1 commit
  35. 02 Jan, 2001 1 commit
  36. 26 Dec, 2000 1 commit
    • Mike Hibler's avatar
      The Evisceration of Tip, Chapter 1. · 51f40ab4
      Mike Hibler authored
      Taken from the man page (ntip.1):
      ----
           Ntip differs from the traditional tip in a number of ways:
      
           1.   It does not support calling a remote system, all auto-dialing code
                has been removed.
      
           2.   All the cheezy file transfer support has been removed.
      
           3.   Most of the tilde escapes have been removed.  Mostly these were the
                file trasfer related ones.  See below for what remains.
      
           4.   Ntip ignores 90% of the remote(5) capabilities.  You can set the
                baud rate (br) and the device (dv).  Period.
      
           5.   All of tips variables are still present, but most don't do anything.
                It is left as an exercise to the interested user to differentiate.
      
           6.   By default, it operates in ``raw'' mode instead of the usual
                ``cbreak'' mode.  This means that all input processing (if any) is
                performed by the remote system.  Raw mode also disables
                ``raisechar'' and ``force'' variable interpretation.  Yes, you can
                actually run emacs on an ntip line (modulo the '~' thing).
      
           7.   Tip is the poster-child for fork-without-exec, creating separate
                reader and writer processes executing ``the same code.''  Ntip is a
                child of convenience and consists of a single process using
                select(2).
      
           8.   Ntip no longer uses uucp(1) style locking.  It relies on the TIOCEX-
                CL ioctl (see tty(4))  to provide ``reasonably mutually exclusive''
                access.  While it is still technically possible that two parties
                could open the same line and both get ``exclusive'' access to it, we
                consider this to be the source of amusing anecdotes rather than a
                bug.
      ----
      51f40ab4