CrackedTech

Now a days visiting on Internet is not as safe as it used to be. There are plenty of software that we use, and with those comes a lot of vulnerabilities. There are websites waiting for our ONE CLICK to begin the damage. Unless the software are continuously being updated, the vulnerabilities can be targeted and damage can be done to our computers. (And that’s why you should always update that Adobe every time you get a popup after restart). To get in details, the hackers try to launch the addon in our browser, and if the addon (or the browser, or Windows itself) is old enough, they can exploit any old vulnerabilities and can even access your computer remotely. Your antivirus will not always work if the vulnerabilities in the applications are being exploited. The simple way to be safe on Internet (apart from having Antivirus and Firewall), is to have ALL the updates for all software (and Window$) installed. One good thing is that your Window$ will inform you once the u...

In case you are having HP ProCurve Core Switches, and need to configure redundancy on it, you need to configure VRRP to achieve it. I will assume you have the knowledge of HSRP for this post. Somehow, HP ProCurve switches does not support a separate Virtual IP address than the Physical IP address for VRRP. Although, many other vendors do support it (Virtual IP being different than the Physical IP addresses (in the same network)). HP ProCurve requires that the Virtual IP address to be the same as the Master's Physical IP address. I am not sure why they want us to enforce the Virtual IP address being the same as Master's Physical IP address, since this creates issues, especially in Monitoring software. For e.g., you want to monitor both Cores by their IP address. Since they are running VRRP, and if master fails, the Master's IP address will still show as "UP", since the virtual IP (which is same as Master's Physical IP address) has shifted to the Backup/S...

In case you are thinking to configure NAT in HP ProCurve switches, forget about it. NAT is NOT supported in ProCurve switches.

The " passive-interface " in Cisco for OSPF is renamed as " silent-interface " in H3C. The syntax and purpose is exactly the same. (Example is shown below). # Stops the interface from sending OSPF packets. <hostname> system-view [hostname] ospf 1 [hostname-ospf-1] silent-interface Gigabitethernet 0/1

If you want to give IP address to an interface of ProCurve switch, its simply not possible. What you can do is to create a vlan, assign an IP address to that vlan, and then assign the interface as untagged member (access port) for that new vlan.

There is an option for Source IP for Telent and AAA in HP ProCurve devices. The same source IP command is also valid for Syslog, Radius, NTP, TFTP, etc. The command is available in global view. The syntax is: ip source-interface ... For e.g., PROCURVE(config)# ip source-interface ?  radius       RADIUS protocol.  sntp         SNTP protocol.  syslog       SYSLOG protocol.  tacacs       TACACS+ protocol.  telnet       TELNET protocol.  tftp         TFTP protocol.  sflow        SFLOW protocol.  all          All listed above protocols. PROCURVE(config)# ip source-interface tacacs ?  IP-ADDR      Specify the IP address.  loopback     Specify the loopback interface.  vlan         Specify the VLAN interface.

When it comes to traceroute, H3C routers behave like firewalls. i.e., They will NOT respond to the traceroute, and hence there will be an output of 3 stars (*) followed by Request timed out for hop of H3C router. Although, while troubleshooting, it becomes quite necessary to have all the hops displayed in front of you. To enable this feature where you will be able to get the output in traceroute for H3C routers, just issue this one command in H3C router (in system-view): [Router-name] ip ttl-expires enable Check out the results below for traceroute before and after executing the above command on the third hop (which is H3C router). Results for Traceroute before and after enabling ttl-expire on H3C router