Showing posts with label Juniper. Show all posts
Showing posts with label Juniper. Show all posts
Configuration: Windows native DialUP VPN client & Netscreen
As the subject of this topic states I want to create a dialup VPN to a Netscreen Firewall. To make it more complex I will choose the onboard Windows VPN client. At the moment only a few documentations exist and most of them contain only pieces of the whole setup process. Different threads in discussion groups out there state that the whole XP-VPN/Netscreen thing will not be possible but they lack the proof that this cannot be done.How To Install Olive 12.1R1.9 With Qemu
The article describes installation of Junos 12.1R1.9 on emulated x86 hardware. Hardware is emulated by Qemu and Junos installed on it is known as Olive.
As Olive does not have Packet Forwarding Engine PFE attached, packet forwarding is exclusively depending on performance of the host CPU. In addition, they are also configurations known as not working on Olive. Considering these limits, Olive can never substitute real Juniper hardware.
In spite all of that Olive is an excellent tool for testing configurations that can be later deployed on real Juniper hardware. Thanks to GNS3 project that offers lightweight GUI for Qemu, complex labs can be easily deployed without real need of knowing Qemu commands.
My goal was to rewrite these articles for actual Junos 12.1R1.9 version and create a guide that helps you to install Junos. Please use links above if you feel that you need to clarify details or further explanation.
As Olive does not have Packet Forwarding Engine PFE attached, packet forwarding is exclusively depending on performance of the host CPU. In addition, they are also configurations known as not working on Olive. Considering these limits, Olive can never substitute real Juniper hardware.
In spite all of that Olive is an excellent tool for testing configurations that can be later deployed on real Juniper hardware. Thanks to GNS3 project that offers lightweight GUI for Qemu, complex labs can be easily deployed without real need of knowing Qemu commands.
My goal was to rewrite these articles for actual Junos 12.1R1.9 version and create a guide that helps you to install Junos. Please use links above if you feel that you need to clarify details or further explanation.
JUNOS OLIVE 12.1R1.9 VMware/Qemu for GNS3
First download JunOS Olive 12.1R1.9 and setup all requirement http://certcollection.org/forum/topic/150241-juniper-junos-olive-121r19-for-vmwareqemu/
Note: you can also download from some other link by searching on google if this link is found inactive
then download StarWind V2V Converter
http://www.starwindsoftware.com/converter
Step 1
Note: you can also download from some other link by searching on google if this link is found inactive
then download StarWind V2V Converter
http://www.starwindsoftware.com/converter
Step 1
JUNOS Emulators: Features You CAN & You CAN’T PRACTICE
Emulators runs the real JUNOS software(which runs on a router) on a virtual machine using Qemu or the VMware. As per experience you can practice almost all the features but for sure there are few which you can't.
2:- OSPF & ISIS. If you are using Qemu, under protocol ISIS you need to
configure interface type "point-to-point" otherwise adjacency will not be up. If you are using VM ware then you don’t need "point-to-point".
3:- BGP, you can configure almost all the knobs mentioned in the books.
4:- Policies works just fine with either emulators.
5:- MPLS TE also works fine.
2:- Few firewall features
3:- L2 VPN
4:- Multicasting
JUNOS allows to configure the hardware or services which are currently not running in the router, means you can configure an ATM or a frame-relay interface and save the configuration but this configuration will not be associated with any interface, in short you can just type the command even for the hardware which is not present but you cannot see it working.
If you are a beginner then there is lot more you could do with these.
Best of luck.
You CAN do the following:
1:- Basic system configuration like snmp, syslog, user accounts & NTP etc.2:- OSPF & ISIS. If you are using Qemu, under protocol ISIS you need to
configure interface type "point-to-point" otherwise adjacency will not be up. If you are using VM ware then you don’t need "point-to-point".
3:- BGP, you can configure almost all the knobs mentioned in the books.
4:- Policies works just fine with either emulators.
5:- MPLS TE also works fine.
You CAN'T do the following:
1:- VRRP on either emulators2:- Few firewall features
3:- L2 VPN
4:- Multicasting
JUNOS allows to configure the hardware or services which are currently not running in the router, means you can configure an ATM or a frame-relay interface and save the configuration but this configuration will not be associated with any interface, in short you can just type the command even for the hardware which is not present but you cannot see it working.
If you are a beginner then there is lot more you could do with these.
Best of luck.
Remote VPN To Netscreen Device - [XAuth with Cisco ACS RADIUS]
NetScreen has implemented XAuth to allow another layer of authentication for VPN between a Remote Client and a Netscreen VPN Device. This negotiation takes please after the first phase of the IPSEC. You may verify authentication to the Netscreen Device’s local authentication database, radius, Secure ID, and LDAP server. You may as before use groups to combine the dial-up users or use individual dial-up users.You cannot use the group function if you are using Secure-ID or a LDAP server.
Use Funk RADIUS server to support such NetScreen-specific attributes as admin privileges, user groups, and remote L2TP and XAuth IP address, and DNS and WINS server address assignments, you must load the Funk dictionary file (netscreen.dct) that defines these attributes onto the RADIUS server. If using Cisco ACS Radius, load the Cisco dictionary file (NSRadDef2.ini). A dictionary file defines vendor-specific attributes (VSAs) that you can load onto a RADIUS server. Afterdefining values for these VSAs, NetScreen can then query them when a user logs in to the NetScreendevice. NetScreen VSAs include admin privileges, user groups, and remote L2TP and XAuth IP address, and DNS and WINS server address assignments.
Use Funk RADIUS server to support such NetScreen-specific attributes as admin privileges, user groups, and remote L2TP and XAuth IP address, and DNS and WINS server address assignments, you must load the Funk dictionary file (netscreen.dct) that defines these attributes onto the RADIUS server. If using Cisco ACS Radius, load the Cisco dictionary file (NSRadDef2.ini). A dictionary file defines vendor-specific attributes (VSAs) that you can load onto a RADIUS server. Afterdefining values for these VSAs, NetScreen can then query them when a user logs in to the NetScreendevice. NetScreen VSAs include admin privileges, user groups, and remote L2TP and XAuth IP address, and DNS and WINS server address assignments.
[VIDEO] - Step By Step Guide To Install NSM 2009 On RHEL 5
I have just completed the installation of nsm20091r1 on RHEL(Redhat) 5 with the help of this tutorial, but there were also some additional steps done by me that are not mentioned in this tutorial. All the additional steps are also added in the tutorial below
Within this tutorial we will be installing Juniper NSM 2009.1 onto a RHEL (Redhat) 5 server.
Click Here To Play The Installation Video
Step By Step Guide To Install JunOS Olive in VMWware Fusion
Tested with VMWare Fusion Version 3.1.2 and JunOS 10.4.R3.
Requirements
VMWare Fusion #should also work with VMWare Workstation
FreeBSD 7.1
JunOS M-, MX- oder T-Series Router Firmware
Disc (8GB) Partition overview:
ad0s1a / 1024M
ad0s1b swap 1024M
ad0s1d swap 24M
ad0s1e /config 12M
ad0s1f /var the rest
Command summary to prepare the original JunOS Image to an Olive Image:
Requirements
VMWare Fusion #should also work with VMWare Workstation
FreeBSD 7.1
JunOS M-, MX- oder T-Series Router Firmware
Disc (8GB) Partition overview:
ad0s1a / 1024M
ad0s1b swap 1024M
ad0s1d swap 24M
ad0s1e /config 12M
ad0s1f /var the rest
Command summary to prepare the original JunOS Image to an Olive Image:
Step By Step Guide To Install JunOS on GNS3 [Part 1] [Updated]
This article explain you how to emulate Juniper JunOS on a PC using Qemu. This is an updated and enhancedversion of excellent howtos from Juniper Clue and Internetwork Pro as well asHimawan Nugroho’s blog. I mainly focused on Qemu, so if you wish to install JunOS on a real PC or using VMware, please have a look at the Juniper Clue article for more information (and of course Google).
So what’s new you would say? First, I chose to use the latest version of Qemu: the 0.11.0 which supports the Intel e1000 network card emulation since version 0.10.0. and includes several fixes for it. I have modified and adapted the old patch for Qemu 0.11.0, it includes the UDP tunnel (connection to dynamips/GNS3), PCAP and LCAP support. Also, the patch allows multicast traffic with the e1000, i82557b and i82559er Qemu emulated network cards.
Moreover, this article show how to emulate JunOS on multiple operating systems: Mac OS X, Windows XP and Linux Ubuntu 9.04 without using an untrustworthy obscure binary downloaded from a forum you can’t even read the language.Disclaimer
Please note that JunOS is not provided and will not be. So please don’t ask. Also, I do not take any responsibility on what happen on your PC, keep in mind this howto requires some patience and that is not for complete beginners. Moreover, this howto doesn’t necessarily present the best and/or easiest way to emulate JunOS. This is the cleanest and less intrusive for me but please feel free to give me constructive comments and tell what worked or didn’t worked for you.
Installation
Subscribe to:
Posts (Atom)
