Some labs/classroom work require valid DNS names, for example, for certificates to be valid. Internally, all LabraNet users are allowed to use a domain .zz (for example, A1234.zz if your student-id is A1234). Under this domain, one can add as many hosts and DNS records as necessary.
The personal domains under .zz top level domain are resolvable only locally from classrooms and personal workstations in LabraNet. The domain/subdomains are also not DNSSEC signed.
To handle your records, log in to zz.labranet.jamk.fi using your LabraNet credentials.
If you have forgotten your LabraNet password or otherwise want to change it remotely, you can use the LabraNet Self-service portal when the following applies:
- Your account is not disabled / locked
- You have access to your JAMK email account
The Self-service portal can be found at:
By filling in your LabraNet username and reCAPTCHA, you can generate a password reset link which will be sent to your JAMK email account.
Opening the link from your email account will lead to a form with which the password change can be completed. Read the password requirements and fill in your new password twice and complete the reCAPTCHA. Click Submit to complete the password change.
- If you have forgotten your JAMK account password, you can reset it via Vetuma
- The email link is only valid for 10 minutes
If the password reset fails or you have trouble with the service otherwise, please contact LabraNet helpdesk.
GitLab is a web-based Git repository manager with additional features, such as wiki, issue-tracking and CI/CD pipelines. LabraNet Gitlab can be used by students to host their study related software development projects.
Logging into LabraNet GitLab
Users can use their LabraNet credentials to sign into the GitLab. If you don’t have a LabraNet account, see FAQ for more information. On the front page the LabraNet sign in-option has to be selected.
Backing up projects
Individual projects are not backed up, so users are responsible to keep backup copies of their projects. Repository contents can be backed up cloning the repository. The entire project, including wiki, issues and settings can also be exported.
You can access your home folder and other resources from your home network with VPN. Instructions for connecting to the LabraNet VPN and mounting your home folder can be found in the LabraNet Remote Access Guide
If you encounter any problems with VPN connection here are few remedies to known problems:
– DNS problems are often solved by flushing the DNS cache (in windows the command is “ipconfig /flushdns”, in linux you need to restart nscd daemon with command “/etc/init.d/nscd restart”)
– Connectivity problems are caused by not receiving proper routes from VPN connection, DHCP clearance is often needed to get VPN routes. In windows commands are: “ipconfig /release” and after that “ipconfig /renew”. In linux “dhclient -r” will renew DHCP bindings.
– Check whether the VPN tunnel is in full or split mode (See Advanced Routing in the Guide). Sometimes full tunnel mode works better
– In newer Mac OS X, check the Service order in the Network settings page, and the scutil –dns command output. Wrong service order will make the system use your default DNS servers, and the system cannot resolve LabraNet names.
– If the Windows 10 app freezes and doesn’t show connection options you can complete or close the connection using the following command line commands:
– To make the connection: rasdial.exe “connection name” (add username and password if you haven’t saved them in connection options: rasdial.exe “connection name” “username” “password”)
– To close the connection: rasdial.exe “connection name” /disconnect
LabraNet VPN Auto Triggering
Windows 10 adds the possibility to auto trigger VPN connections. This following guide shows how you can add applications that automatically trigger a VPN connection when launched. The example shows a custom application but you can use whatever application suits you best, for example MySQL Workbench.
Prerequisites for custom application
- Python installed and in path
- Example uses version 3.8.1
- VPN connection created with correct settings
- Credentials saved for the connection
Open a new PowerShell window. Run it as administrator if you want to save the shortcut to public desktop later as per these instructions.
Install PyInstaller for building an executable out of chosen Python-script
python -m pip install pyinstaller
Write your connection script. Here the input() function is chosen so that the script finishes and executable closes after enter is pressed
Write-Output ‘input(“Press enter to disconnect”)’ | Out-File -FilePath vpn.py -Encoding utf8
Build the executable.
python -m PyInstaller -F vpn.py
Move the created executable to current directory.
Move-Item .\dist\vpn.exe .
Configure vpn triggering. Split tunneling is required for triggering to work. IdleDisconnectSeconds define how long the connection stays on after the executable is closed.
$vpn = (Get-VpnConnection).Name
$app = “$((Get-Location).Path)\vpn.exe”
Set-VpnConnection -Name $vpn -SplitTunneling $True -IdleDisconnectSeconds 5
Add-VpnConnectionTriggerApplication -ConnectionName $vpn -ApplicationID $app
Create a shortcut to public desktop. If you did not lauch PowerShell as admin, either escalate privileges or change the $ShortcutLocation path below.
$ShortcutLocation = “[Environment]::GetFolderPath(‘CommonDesktopDirectory’)\Connect to LabraNet.lnk”
$WScriptShell = New-Object -ComObject WScript.Shell
$Shortcut = $WScriptShell.CreateShortcut($ShortcutLocation)
$Shortcut.TargetPath = $app
Check the connect automatically checkbox in vpn settings.
Connecting via auto trigger should function similarly to video below.
Some courses and theses are done in virtualized environments, such as the VMware vSphere Hypervisor (ESXi). SpiderNet Center is a clustered environment for handling lab virtual machines. SpiderNet_Virtual_Machines includes some common help and guidelines for using such environments and working with them.
If you bring us virtual machines for use in labs or the vCloud Director environment, the images should be VMware vSphere 5.0 compatible (VM version 8) and in OVF/OVA format as plain VMX/VMDK images can be troublesome. If using software other than VMware to create the images, please remove USB/Audio devices and use SCSI disks instead of SATA/IDE. More information about format conversion in the guide above.