Network Access

The new DHCP server (installed on June 2006) comes together with a new policy for the use of laptops within SISSA using either wired or wireless connections. The new policy aims at a tighter control of the users of the DHPC and at a more reasonable use of the resources.

Within the new policy, SISSA users will be asked to register their laptops to have full access to SISSA's network resources. This is a simple operation, to be done only ONCE, explained below. To complete the registration process you will need a valid SISSA's account on the central cluster. Three laptop registrations are available for each user (the older one is deleted when the limit of three is exceeded).

Unregistered laptops are no more allowed, according to Italian Law n.155 of 31/7/2005 that states that every user connecting to the internet must be identified.

1. Connect your laptop to the SISSA network (either via an ethernet cable or through a wireless card) using the DHCP server: an unprivileged address with the limitations stated above will be assigned to your laptop;
2. Point your browser to https://netreg.sissa.it/[/color] (it should just point there, whatever site you are pointing it to) - Read and understand the Acceptable Network Usage Policy; - If you accept the Policy, register with your username and password (i.e. the ones used on the central SISSA cluster, the shannon.sissa.it ones) and click on Accept - A pause is now needed to register your laptop and you will be asked to reboot it - After the reboot you will be connected to the network with the same privileges as any other SISSA workstation (i.e. connection to the print spooler, SSH from one internal machine to the other, connection to ouside network, etc.) - Your registration will be automatically deleted when your account expires If in doubt or experiencing problems, please contact our helpdesk@sissa.it or the phone number (+39-40-3787) 822. ===== Proxy Server ===== The use of a web proxy can improve both tranfer speed and response time when accessing many popular web sites, while reducing the total traffic on SISSA external link. This is achieved keeping a local copy of frequently visited pages. The local copy is validated before being served to the client, i.e. compared to a set of refresh patterns to ensure the information is still up-to-date, so users don't have to worry about being served stale web contents. You can configure your browser to use the proxy with the automatic configuration script provided at http://proxy.sissa.it/cgi-bin/proxy.pac. If you encounter any problem, please fill as much information as you can in the error reporting forms provided with proxy error messages. Your reports will help us to track down existing problems and improve service quality. ==== Browser-specific informations ==== === Netscape, Mozilla === - Open Edit → Preferences → Advanced → Proxy - Select “Automatic proxy configuration URL” - Fill in the URL provided above - Click on “OK” === Mozilla Firefox === - Open Edit → Preferences → General - Select the “Connection Settings…” button - Select “Automatic proxy configuration URL” - Click on “OK”, “OK” === Internet Explorer === - Open Tools → “Internet Options…” - Select the Connections tab - Select the “LAN Settings…” button - Select “Use automatic configuration script” - Fill in the URL provided above - Click on “OK”, “OK” A Windows 2000/XP setup wizard is available at link http://www.sissa.it/download/wizards/sissa_proxy_setup.vbs. === Opera === - Open Tools → Preferences - Select the Advanced tab → Network - Select the “Proxy servers” button - Select “Use automatic proxy configuration” - Fill in the URL provided above - Click on “OK”, “OK” === Konqueror === - Open Settings → Configure Konqueror → Proxy - Select “Use the following proxy configuration URL” - Fill in the URL provided above - Click on “OK” === Lynx, ELinks, Wget === BASH users can put this line into .bashrc file: export http_proxy=“http://proxy.sissa.it:3128/” TCSH users can put this line into .tcshrc file: setenv http_proxy “http://proxy.sissa.it:3128/” <note> Since lynx does not support proxy autoconfiguration, this configuration provides only fault tolerance, but no load balancing </note>.