• Connecting@Berkeley   email, USENET, HomeIP software and services for UC Berkeley
• AirBears   wireless network on campus
• software for logging into UNIX   ssh, putty, xming, winscp
• software for logging into Windows   Remote Desktop Client, rdesktop
• UCB VPN   puts your remote computer on a virtual UCB network
• EECS VPN   VPN for non-Instructional EECS accounts
• file-transfers.html   for non-Instructional EECS accounts
• home-ip.help   troubleshooting tips

if you are on an EECS UNIX or MacOSX computer:	You can login to one of our UNIX servers using 'ssh'.   Enable X11 tunneling before you login so UNIX graphics programs can open windows on your local computer (usually 'ssh -X').   You can copy the files to other UNIX accounts using 'sftp', the SSH file transfer program, which comes with the SSH package.   See ssh.help for more information about SSH on UNIX. All EECS UNIX systems have 'ssh' and 'sftp'.   Sample usage (for user 'jdoe'): /usr/sww/bin/ssh jdoe@cory.eecs.berkeley.edu /usr/sww/bin/sftp jdoe@cory.eecs.berkeley.edu:public_html index.html-new On MacOSX, you can logon to one of our Windows servers using the Remote Desktop Connection client.   You can set it so that the disks on your local computer are connected to the logon session on our server. When you start your RDC program, type in the name of our Windows server, then select Options->Local Resources->Local devices and click on "disks", then on "Connect".   Your local disks will appear in the My Computer window on our server, and you can drag files to and from them. On other UNIX systems, you can copy files to a Windows account using the UNIX 'smbclient' command.   See samba.help for more information.   For example (for username 'jdoe'): /usr/sfw/bin/smbclient '\\fileservice\named' -U jdoe EECS If all this fails, you could use email or USB memory to copy the file.
if you are on a non-EECS UNIX or MacOSX computer:	You can login to one of our UNIX servers using 'ssh'.   Enable X11 tunneling before you login so UNIX graphics programs can open windows on your local computer (usually 'ssh -X').   You can copy the files to your EECS UNIX account using 'sftp', the SSH file transfer program, which comes with the SSH package.   Most Linux and MacOSX systems include SSH.   See ssh.help for more information about SSH on UNIX. See ftp.help for free programs that you can install at home and use to transfer files from your account on the instrcutional UNIX computers. On MacOSX, you can logon to one of our Windows servers using the Remote Desktop Connection client.   You can set it so that the disks on your local computer are connected to the logon session on our server. When you start your RDC program, type in the name of our Windows server, then select Options->Local Resources->Local devices and click on "disks", then on "Connect".   Your local disks will appear in the My Computer window on our server, and you can drag files to and from them. On other UNIX systems, there is no way to connect directly to an EECS Windows directory to access or copy files.   You cannot use 'smbclient' (see above), because the related network ports are blocked from off campus for security reasons. If all this fails, you could use email or USB memory to copy the file.
if you are on an EECS Windows computer:	You can login to one of our UNIX servers using Putty.   Enable X11 tunneling and start Xming before you login so UNIX graphics programs can open windows on your PC.   You can copy files to your EECS UNIX account using WinSCP. All EECS Windows systems have Putty, WinSCP and Xming.   You can locate the program from the Start\Programs menu. You can logon to one of our Windows servers using the Remote Desktop Connection client.   You can set it so that the disks on your local computer are connected to the logon session on our server. When you start your RDC program, type in the name of our Windows server, then select Options->Local Resources->Local devices and click on "disks", then on "Connect". Your local disks will appear in the My Computer window on our server, and you can drag files to and from them. You can connect to your UNIX home directory (the Instructional UNIX file server is "mamba").   If your username were 'jdoe', you would type this in the Windows Start->Run... text entry box: net use X: \\mamba\jdoe /user:eecs\jdoe You can connect to another EECS Windows directory (the Instructional Windows file server is "fileservice").   If your username were 'jdoe', you would type this in the Windows Start->Run... text entry box: net use Y: \\fileservice\named\jdoe /user:eecs\jdoe Here are examples of home directory paths for EECS Windows accounts: \\fileservice\named\jdoe   (Instructional named account) \\fileservice\ee20n\sp07\ee20n-ab     (Instructional class account) \\home\home\jdoe   (non-Instructional account) If you are prompted for a Username and Password, here is an example: Username: EECS\jdoe Password: [ Windows password for jdoe ] Note that Windows can remember only ONE user's permissions per file server, so if you try to connect to a second home directory on the same server, you will not be asked for another Username and Password.   Instead, you will be connected using the permissions of the first connection you made.   So it is likely that the second connection will not have full access permissions or will not be permitted at all.   The only way you can get full acess to the second home directory is to logout of Windows, login again and connect to that home directory first. If all this fails, you could use email or USB memory to copy the file.
if you are on a non-EECS Windows computer:	You can login to one of our UNIX servers using Putty.   Enable X11 tunneling and start Xming before you login so UNIX graphics programs can open windows on your PC.   You can copy files to your EECS UNIX account using WinSCP. See ftp.help for free programs that you can install at home and use to transfer files from your account on the instrcutional UNIX computers. You can logon to one of our Windows servers using the Remote Desktop Connection client.   You can set it so that the disks on your local computer are connected to the logon session on our server. When you start your RDC program, type in the name of our Windows server, then select Options->Local Resources->Local devices and click on "disks", then on "Connect". Your local disks will appear in the My Computer window on our server, and you can drag files to and from them. If all this fails, you could use email or USB memory to copy the file.
Using email or removable media to transfer files:	You can copy files by emailing the files to yourself as attachments and downloading them from the email server to the computer (UNIX or Windows) where you read the email.   Instuctional accounts can logon to imail.eecs.berkeley.edu to read and post email. See "tar.help" "man tar" and "man uuencode" for methods of bundling UNIX files for delivery by email. You can copy files to removable media such as a CD-RW or DVD-RW disk, a flash memory card or a USB memory stick.   See multimedia.help for the current location of these drives in the EECS Instructional labs.

1. Imail WEB mail client:   Just login to http://imail.eecs.berkeley.edu using your Instructional UNIX account.   You do not need to configure it yourself.

2. Your own email client:   You can configure an email client such as Firefox, Outlook, Eudora, mutt or pine to logon to our email server.   Here are instructions for configuring an email client for CalMail and Imail:   https://calmail.berkeley.edu/docs/client.html

   The CalMail instructions also work for Imail; just replace the server name calmail.berkeley.edu with imail.eecs.berkeley.edu in the instructions and use your EECS Instructional UNIX logon name and password.   Depending on which email client you are using, you will probably find the place to enter this information under a "Preferences" or "Options" menu, or in a configuration file.

   Here is the information that is needed for Imail:

   Purpose:	Name:	Settings:
   news server from on-campus; no password	news.csua.berkeley.edu	not SSL, no logon required, not SPA, port 119
   news server from off-campus; password required	(see new USENET server)	not SSL, requires logon, not SPA, port 119
   incoming email server	imail.eecs.berkeley.edu	IMAP, requires SSL, not SPA, port 993
   incoming email account name	login@imail.eecs.berkeley.edu	"login" = your Instructional UNIX account name
   outgoing mail server (ask your ISP)   *	typically it's just "mail" *	typically it's POP, not SSL, port 25 *
   outgoing email account name	you choose this	you configure this in your email client

   
   

   * Many ISPs block port 25 traffic to any but their own mail servers, to cut down on spam delivery. Alternatively, EECS faculty, grad students and staff with funded EECS accounts can login to "gateway.eecs.berkeley.edu" via port 587 for outgoing email service. See the EECS email page for details.

1. ~yourlogin/mbox, if that file exists
2. ~yourlogin/Mail, if you have our standard .procmailrc file
3. somewhere else, if you configure it in your .procmailrc file

.procmailrc (takes precedence)
.forward (if you do not have a .procmailrc)

• Login to your Instructional UNIX account.
• At the UNIX command line, type either (for example):
  (echo "me@newaddress.edu") > .forward
(echo ":0"; echo "\! me@newaddress.edu") > .procmailrc
  

We will keep forwarding your mail as long as the account has not been deleted from our disks (about a month after it expired).

The campus USENET newsgroup service on 'news.berkeley.edu' ('agate.berkeley.edu') ended on Dec 31, 2008.
The manager's message about it is posted on Micronet.

(January 2009)   The CSUA has generously volunteered to host a USENET server just for the ucb.* newsgroups (includes the EECS class newsgroups).   The server name is "news.csua.berkeley.edu". How to read and post to the newsgroups on "news.csua.berkeley.edu": Use the EECS Instructional WebNews client. This can be accessed from anywhere using an EECS Instructional UNIX account. Use a WEB client such as Thunderbird or a text-based client such as pine. See the email section above for information about configuring USENET clients for access. No logon is required for access from computers on UCB campus subnets, AirBears and the UCB VPN. A shared logon (username=usenet, password=gobears) is required for access from off-campus, to discourage spammers. You can include a link to a class newsgroup in a WEB page with this HTML code (using "cs152" as an example): <A HREF='news://news.csua.berkeley.edu/ucb.class.cs152'>CS152 Newsgroup</a> Result: CS152 Newsgroup

           unsecured               "secured"
   (home)-------------(computer1)--------------(computer2)
           (telnet)                  (ssh)
              ^               
              |
              +- This is where a cracker could get anything 
		      you type to computer1 or computer2
  

Questions about SSH:	Answers:
1. Is the "pass phrase" like the password on a UNIX account? Does it need to be long, and with nonalphabetic characters etc.? What happens if someone guesses it?	1. Passphrase is like a password, which is used to enable increased security (it is not required). "ssh-keygen" creates it. The UNIX "man ssh-keygen" command says "The passphrase may be empty to indicate no passphrase (host keys must have empty passphrase), or it may be a string of arbitrary length. Good passphrases are 10-30 characters long and are not simple sentences or otherwise easily guessable..." If someone guesses it, they can login to your account and do bad things.
2. Suppose you work on more than two accounts (for example: my home Mac, my campus Mac, my hera account, from which I access a variety of other accounts). Will one key suffice for the various accounts that I use for initial login, or should I have different keys?	2. The SSH passphrase is stored in files in your .ssh subdirectory on UNIX, or in your UserKeys folder on Windows. The files could be unique in each account, or they could be copied (do it securely using scp!) to other accounts.
3. Every time I login with ssh, I get the message that hera is sending a previously unknown key (or some such thing). What's going on here, and what's the proper response?	3. If you answer "yes" to the question, ssh will add the key of the remote host (ie "hera") to your ~/.ssh/known_hosts file (UNIX) and you won't be asked again, unless they change the host key on hera (or someone is pretending to be hera on the network).