Linux TCP/IP and more
I used a serial connection, with USB -> RJ45-Serial – Cable
save config from usb configname.cfg to flash
minicom config from: /etc/minicom/minirc.juniper
Config:
1 2 3 4 5 6 7 8 9 | # Manuell erzeugte Datei - Verwenden Sie "minicom -s" zum Ändern pu port /dev/ttyUSB0 pu baudrate 9600 pu minit pu mreset pu mconnect pu mhangup pu escape-key ^M pu rtscts No |
Redirect incoming links with .htaccess to prevent duplicate content penalties
Create a .htaccess file under htdocs, with following content
1 2 | RewriteEngine on RewriteRule ^(.*)$ http://www.zeldor.biz/$1 [L,R=301] |
Each request to your site will be redirected to www.zeldor.biz
I think you have heard already of IPv4 address depletion. A new version of Internet addressing (New Internet protocol) system was prepared many years ago. But since everyone was using IPv4 address, the migration has not been implemented in a large scale. If we continue to use IPv4 address as on today, the entire range would be used up in less than one years. (Hurricane-Electric has a very nice counter.) Public IPv4 addresses are mainly used by Internet servers. Other PCs or Servers can use private IPv4 address which are not reachable from Internet. Although many methods like NAT (Network Address Translation) and CIDR (Classless Inter Domain Routing) were implemented to stretch the IPv4 address usage, it seems that it is reaching a level of saturation now.
It is sure that everyone must migrate to IPv6 address within a couple of months/ years. Some Internet registries are not so liberal in assigning free IPv4 address now. If you want to learn about IPv6 and make sure that you have skills to administer IPv6 address and servers, Hurricane Electric free IPv6 certification is a really great way to begin. You can register for this certification at: he.net. I will give you a brief overview of the tests in the following section.
Through this test set you will be able to:
-> Prove that you have IPv6 connectivity
-> Prove that you have a working IPv6 web server
-> Prove that you have a working IPv6 email address
-> Prove that you have working forward IPv6 DNS
-> Prove that you have working reverse IPv6 DNS for your mail server
-> Prove that you have name servers can respond to queries via IPv6
-> Prove your knowledge of IPv6 technologies through quick and easy testing
There are seven levels of certification available. The breakdown of each are given below:
Newb: Read the primer stuff, be able to answer some quick and easy questions.
Explorer: Verify that you can access ipv6.he.net over IPv6
Enthusiast: Verify that you have an IPv6 capable web server that we can connect to and fetch information from. This should be entered as a FQDN and not an IPv6 address, or you will have issues once you start working on the Guru level.
Administrator: Verify that you have a working IPv6 capable MTA by sending you an email only over IPv6.
Professional: Verify that your MTA has working reverse DNS (ex: dig mx $domain +short ; dig AAAA $mx +short ; dig -x $mx AAAA +short)
Guru: Verify that the authoritative NS for your domain have AAAA records, and respond to queries for the domain (ex: step 1 is dig ns $domain ; dig AAAA $ns | step 2 is dig AAAAA $domain @$nsAAAA)
Sage: Check to see if your domain’s authoritative NS have IPv6 glue with their listed TLD servers. Meaning the TLD server can directly answer for the host record (ex: dig +trace ns $domain to get the TLD server list then dig aaaa $ns @TLD +short for the glue).
After each test you will get a new certificate:
In order to do this, you need to do some sysdmin job:). I am going to specifically focus on Apache and PHP because I’m more of a LAMP user. If you use ASP on Microsofts IIS, I can’t help you (but hey!, Google is there to save your sunny day! :P)
Find your php.ini file in my case,
1 | vim /etc/php5/apache2/php.ini |
Look for the line that says: “expose_php On“
Change it to:
1 | expose_php Off |
Now our PHP is very silent
Note by PHP developer:
; Decides whether PHP may expose the fact that it is installed on the server
; (e.g. by adding its signature to the Web server header). It is no security
; threat in any way, but it makes it possible to determine whether you use PHP
; on your server or not.
Some IPv6 commands for daily use
Print the route packets trace to IPv6 network host.
1 | traceroute6 ipv6.idrobot.net |
Lookup AAAA record.
1 | dig AAAA ipv6.idrobot.net |
IPv6 DIG PTR reccord.
1 | dig -x 2001:470:1f0b:1604::254 |
Check redirector.name glue records by dig command.
As it is a .name domain first we should check root servers for .net by the following command:
1 | dig NS name |
You will get 10 root servers:
1 2 3 4 5 6 7 8 9 10 11 | ;; ANSWER SECTION: name. 10800 IN NS m6.nstld.com. name. 10800 IN NS d6.nstld.com. name. 10800 IN NS k6.nstld.com. name. 10800 IN NS f6.nstld.com. name. 10800 IN NS h6.nstld.com. name. 10800 IN NS g6.nstld.com. name. 10800 IN NS a6.nstld.com. name. 10800 IN NS j6.nstld.com. name. 10800 IN NS l6.nstld.com. name. 10800 IN NS c6.nstld.com. |
You can choose any root server for next query , I will take g6.nstld.com
1 | dig ns1.redirector.name @g6.nstld.com |
As output I get:
1 2 3 4 | ;; ADDITIONAL SECTION: ns1.redirector.name. 10800 IN A 188.40.116.206 ns1.redirector.name. 10800 IN AAAA 2001:470:1f0b:1604::3 ns2.redirector.name. 10800 IN A 188.40.116.216 |