Все-таки в очередной раз убедился что служба динамического DNS no-ip намного удобнее и интуитивно понятнее чем DynDNS. После моих танцев с бубном над DynDNS-клиентом для Linux я добился того что пинги стали проходить, но возвращался мой внутренний адрес (192.168.*.*) а вот внешний адрес отслеживать не получалось. В итоге плюнув на это все решил поставить клиент от no-ip. Сразу стало все легко и просто (хотя на моей хост машине в которой я запускаю VMware этот клиент уже есть и ставить его на виртуальную машину необязательно).

  Зато чуток погонял в Аллодов добил своего некра до 11 лвл жду теперь похода в орешек  

You’ve spent a lot of time and money collecting digital music. And by now, you have a pretty sweet library of MP3s and AACs to show for the effort.

But let’s say you want to take that library to go? Before you start carrying around a huge hard drive, you might want to try streaming your tunes online instead. All it takes to start streaming your music over the internet is a playlist, a server with some storage space, and a software player that can open and play an internet stream.

Step 1: Host it somewhere

Most web hosts offer data plans around $10 per month that come with plenty of storage and bandwidth to hold and serve your music. The rates get steeper once you want to store more than 200 or 300 gigabytes. Also, when you’re streaming, you’re paying for bandwidth. So, if you’re looking to share your collection with your friends as a stream, you’ll have to monitor your usage more closely or else end up paying through the nose.

Besides the cost, you trade off a good deal of control over the data because it resides on some machine out there in the ether.

Hosting music on your own computer using a broadband connection is a preferable option, especially since you know exactly where it is and there’s is no need to transfer your music anywhere. However, unless you have a static IP address, finding your computer (and your music) in the vast expanse of the internet can be a hassle. If your network provider keeps changing your IP address on you, try setting up Dynamic DNS using a service like DynDNS.

Tip: Webmonkey.com has an excellent introduction to using Dynamic DNS.
Tip: Dan Hilgert also has an explanation of his Dynamic DNS setup and streaming music guide.

Step 2: Create a playlist

Perhaps the easiest way to get your music online is to use your favorite music player. Most music players, including iTunes, Windows Media Player and WinAmp all use common playlist formats to play music online.

A playlist contains the names and location of your music files. It is downloaded and used by your media player to play the music files as a stream. It works pretty well, although the music players don’t allow skipping, fast forwarding or rewinding.

The most-used music file formats are MP3, Windows Media Player’s WMA and Apple’s mp4 (also known as AAC). We recommend using only these player files for universality. If you’re not sure which format to use, we’d recommend you default to MP3 to ensure the ultimate in compatibility.

Extended M3U

The easiest and most reliable method for streaming is to use M3U playlist files in conjunction with iTunes or Windows Media Player. Open a streaming URL by pressing Control-U (or Command-U for Mac) in either program.

An extended M3U file format looks like this:

#EXTM3U

#EXTINF:Birds In The Belly http://www.soundsofarcadio.com/mp3/BirdsintheBelly.mp3

#EXTINF:Hock It Like You Own It http://www.soundsofarcadio.com/mp3/HockItLikeYouOwnIt.mp3

#EXTINF:Kid I Know http://www.soundsofarcadio.com/mp3/AKidIKnow.mp3

You can follow the format shown above. Open the code up in a text editor and just paste in your own song info and URLs. When you’re done building your list, save the result as a .m3u file and open it up in your player.

If you’re a Windows user, you can download M3U Creator. The free desktop application will let you create and edit .m3u playlists in an easy-to-use interface.

XSPF

Another common playlist format is XSPF (pronounced “spiff”). This method is more practical for streaming music via a web page or Flash-based players, though many third-party applications support XSPF. For example, Yahoo Music Jukebox uses XSPF as its default playlist format.

The XSPF format is below. Note the “L” in “trackList” needs to be capitalized for it to be recognized by players.

<?xml version="1.0" encoding="UTF-8"?>
<playlist version="1" xmlns="http://xspf.org/ns/0/">
     <trackList>

       <track>
         <location>http://www.soundsofarcadio.com/mp3/BirdsintheBelly.mp3</location>
         <creator>Arcadio</creator>
         <album>Early Demo</album>
         <title>Birds in the Belly</title>
       </track>

       <track>
         <location>http://www.soundsofarcadio.com/mp3/HockItLikeYouOwnIt.mp3</location>
         <creator>Arcadio</creator>
         <album>Early Demo</album>
         <title>Hock It Like You Own It</title>
       </track>

       <track>
         <location>http://www.soundsofarcadio.com/mp3/AKidIKnow.mp3</location>
         <creator>Arcadio</creator>
         <album>Early Demo</album>
         <title>A Kid I Know</title>
       </track>

     </trackList>
</playlist>

Again, to make your own playlist file, just copy this code into a text editor, change the song info and the URLs, and save the results with the extension .xspf.

For a list of players and uses for XSPF files, visit the XSPF applications page. Included in the list is an M3U to XSPF file converter and some command line tools used to generate XSPF files from various music libraries online.

There are also some handy validation tools to make sure your spiffs are well-formed.

PLS

The PLS format is another streaming playlist option, and used mostly by professional online radio broadcasts. You’ll find a good deal of PLS-streaming music stations on Shoutcast.

The PLS file format looks like this:

[playlist]
NumberOfEntries=3

File1=http://www.soundsofarcadio.com/mp3/BirdsintheBelly.mp3
Title1=Birds in the Belly
Length1=-1

File2=http://www.soundsofarcadio.com/mp3/HockItLikeYouOwnIt.mp3
Title2=Hock It Like You Own It
Length2=-1

File3=http://www.soundsofarcadio.com/mp3/AKidIKnow.mp3
Title3=A Kid I Know
Length3=-1

Version=2

Length refers to the length of the song. Use -1 to have the music player ignore it entirely.

Download Software to Do It For You

Otherwise, you might want to give Shoutcast’s broadcasting tools a try. Shoutcast’s tools are extensions built on the Windows-only WinAmp music player, but some broadcasting tools for Mac and Linux are also available.

If you already have WinAmp, Spacial Audio Solutions offers a plugin to turn it into an internet radio station. Spacial also has software for the enthusiastic amateur and professional: SimpleCast and SAM Broadcaster.

iRadeo is a free streaming audio platform that allows anyone to start an online radio station. Once installed, iRadeo will automatically detect and stream any MP3 or WAV file formats that has been uploaded to the specified directory.

Finally, Peercast provides both direct and P2P streaming at the same time, allowing you to stream music online anonymously.

Don’t Feed the Lawyers

You could be fined for broadcasting music you don’t own the copyright to, and in most cases the penalties are pretty severe. There are also plenty of rabid music industry lawyers with a history of going to great lengths to prosecute copyright violators. That said, be careful how you distribute your streams.

Some of the software solutions listed here have built-in password protection. Otherwise, you’ll have to know some SSL and/or password protection web hosting configurations to lock down your stream.

Your other option — and probably the safest — is to just keep your station under wraps. You can listen to it freely, but don’t go spreading the word. Remember, the internet has ears!

Now that I have started my blog on wordpress, i am having all sorts of thoughts to customize it. After doing an extensive research y’day i found that i cant customize ,unless i move my blog to another server.

There are many ways to do this

1> You can you can purchase a plan at a web hosting provider for a few bucks a month.   OR

2>You can set it up on your home computer for free.

I dont intend to spend any money on this blog as of now , n moreover it will be fun to setup your own web server.

The cool thing about blogs (and many other web apps, like wikis) is that they don’t actually have to live online.

Lets look at how to set up weblog on your Windows PC using , WordPress in 7 Steps

Step 1: Install WAMP

1 . WAMP is an open source, simple installation package that bundles together Apache, MySQL, and PHP into one tight little Windows package. You can download WAMP here. Go ahead and accept the defaults unless you have a good reason to do otherwise and you know what you’re doing. Once you’ve finished, direct your browser the http://localhost/ and, if everything went smoothly, you should see the WAMP welcome page above.

Step 2: Change your MySQL password and create a new database

To add a password to your MySQL database. You can do this by clicking on the “PHPmyadmin” link on the WAMP homepage under Tools or by going to http://localhost/phpmyadmin/. To change your password, click on the “Privileges” link, then click the edit privileges icon for the user called, “root” (there should be no other users. If for some reason there are and you didn’t put them there, go ahead and delete them. On the “Edit Privileges” page, go to the “Change password” box, then change and save the password.

To continue using PHPmyadmin, we need to update your password in the config file. Open C:\wamp\phpmyadmin\config.inc.php in your favorite text editor (or just Notepad) and change:

$cfg['Servers'][$i]['password'] = ”;

to

$cfg['Servers'][$i]['password'] = ‘yournewpassword’;

Replacing yournewpassword with the password you just created with PHPmyadmin.

Step 3: Create a new database

Go back tohttp://localhost/phpmyadmin/ and enter a name for your database. It can be called whatever you want, but I kept things simple and called mine, “wordpress”. Hit the Create button and that’s all. Simple, huh?

Step 4: Download and extract WordPress

Go ahead and grab the latest WordPress package here. Unzip the package and extract all of its contents to C:\wamp\www. You can either keep the files in the folder called wordpress, in which case your blog’s URL will be localhost/wordpress/, or you can rename the folder if you’d prefer something like localhost/blog. If you want your root directory to bring up your blog, you can just extract all of the files inside the wordpress folder directly to the C:\wamp\www folder.

Step 5: Configure WordPress

Now we need to tell WordPress about your MySQL database. Assuming you installed WordPress in the default wordpress folder, open C:\wamp\www\wordpress\wp-config-sample.php in a text editor and add your database name, your database username (root), and your new password to the top of the file. (You won’t need to change the DB name if you called it wordpress, but you should replace username with root and password with the password you created in step 2. After you’ve edited the settings, save the file as wp-config.php.

Step 6: Install WordPress

Just go tohttp://localhost/wordpress/wp-admin/install.php (unless you put WordPress in a different folder in step 4). Continue through the dead-simple, two-step installation, until you’ve completed the installation. WordPress will have generated a new username and password that you’ll use to log in to your weblog’s Admin page. By default, the username is ‘admin’, and the password is a randomly generated string. Copy/write it down.

Step 7: You’re done. Configure and post to your blog

go to http://localhost/wordpress/wp-login.php and log in with the username and password WordPress created during the install (you did remember to write it down, right?). The first thing I’d do is change the admin password to something more memorable. To do that, log in and click on the Users tab, where you can add your personal info and change your password. Easy-peasy.

Congratulations, you’ve got your own, personal, locally hosted blog.Now that you’ve got WordPress installed on your local computer, you’ve got a lot of options. If you want to make your blog accessible to the outside world,you need to assign a domain name to your home web server like yourname.com – for an easy-to-remember, bookmarkable, professional web address.

Keep in mind that you wouldn’t be able to run a heavily trafficked blog from your home computer, but if it’s just a personal blog for friends and family, hosting it yourself is definitely an option.

How to assign a domain name to your webserver?

A dynamic DNS service is a constantly updated database of IP addresses and domain names. DynDNS.com is one provider of this service. For free, you can get one of the available DynDNS domain names plus a custom subdomain (like xyz.getmyip.net), or for a small fee you can register your own domain (like ashishjagani.com) and have it resolve to your home computer web server with DynDNS.

• Register for a free account at DynDNS. Agree to the site’s terms, and use a legitimate email address to complete registration. Once in awhile, DynDNS will email you at that address asking you to confirm that it continue your service.
• Log into your new account. Go to the “My Services” area on the left side. Under “Host Level Services” click “Add Host Services.” There, click “Add Dynamic DNS Host.” DynDNS will autofill your IP address (if you’re doing this from your home computer). Choose a domain and type in a custom subdomain, which can be anything from ajfundaes.myblog.org or ashish.is-a-geek.com or aj.dyndns.org.
• Now that your computer is registered with DynDNS, each time your computer’s IP address changes, it has to let DynDNS know. This can be done either with free updater client software or through your router. If your computer is connected directly to the Internet, download the DynDNS updater client for Mac or Windows here. Install and enter your DynDNS information so that your computer can update DynDNS’s database regularly

You’re done. Give your new domain a spin!

Type your new domain name by entering it in your web browser’s address bar. It should resolve to your home server. From here you can publicize or bookmark your server’s new domain name no matter how often your IP address changes.

No son gran cosa, no estan muy desarrolladas, y no son complejas.

He montado una Mediawiki en el Equipo de mi casa (ahora ya en Internet), y una pequeña Web en HTML en mi DropBox, para compartir todos los archivos.

Así que si necesitais protección Antivirus, o algun tipo de software para WinXp, entrar en
Mi Dropbox

Por otro lado, mi MediaWiki esta abierta a participación, no dudeis en escribir lo que sea. No hay censura (pero si Anti-Spam xd)

Xavi Gonzalez Wiki

Un saludo!

First of all, I want to apologize for not getting around to writing part 2 of my previous post yet. I have more free time now and have started research for that post, but haven’t had a chance to write everything down yet. Hopefully I’ll get to it soon.

Update: some people have been confused at to my intention or my recommended use of the code I present here.  Let me make a few things clear:

1. Don’t make these modifications on any production machine
2. Don’t make these modifications on any machine receiving a lot of traffic
3. This isn’t the best way to capture logins.

I called it a “hack” for a reason.  It’s something I threw together in a few minutes in order to gather the necessary data to conduct the analysis I did in my next post.  As dozzie pointed out, this can be done better by writing a PAM module.  My purpose here was not to write something robust, rather to write something quick in order to find a password file being used against me.  I apologize for any confusion.

Keeping in mind that:

• only a fraction of the subdomains pinged will actually be registered with DynDNS
• only a fraction of the registered subdomains will be offering authentication services
• only a fraction of the authentication services will allow predictable usernames*, and
• only a fraction of those valid usernames will have predictable passwords

* root logins aren’t allowed by default on openssh and many other SSH implementations.

The (hopefully) small number of boxes that can be owned by brute forcing with this method apparently outweighs the cost to our adversary(ies).  As I later discovered, our IP address wasn’t enumerated via our DynDNS entry, but was brute forced.  Yeah.  They are trying IP addresses sequentially.

We noticed the SSH logs for our box were getting suspiciously long and it was pretty obvious why:

09/24/2009 12:49:19 PM: [FAIL] An error occured during key exchange auth done
09/24/2009 12:49:19 PM: [NOTE] Connection from 118.46.137.101 disconnected
09/24/2009 12:49:20 PM: [FAIL] An error occured during key exchange auth done
09/24/2009 12:49:20 PM: [NOTE] Connection from 118.46.137.101 disconnected
(repeat about 100 times)...

Our gateway Snort agreed that something was up:

[ ** ] [ 1:2001219:18 ] ET SCAN Potential SSH Scan [ ** ]
[ Classification: Attempted Information Leak ] [ Priority: 2 ]
09/17-10:49:59.339210 118.46.137.101:50905 -> ***.***.***.***:22
(repeat about 100 times)...

The attacking IP addresses would change periodically.

Perhaps I could discover if this is a single attacker or if this is multiple attackers:

• If there is a single group behind these attacks, it would make sense that they would synchronize this work amongst the attacking IPs, allowing the attack to evade simple IDS rules and avoid duplication of effort.
• If there are multiple parties behind these attacks, it would make sense that the same username/password combinations would be tried by different hosts, pointing to a lack of synchronization.

Of course this is a lot of assuming and is hardly scientific, but promises to be a fun experiment regardless.

My first thought was: I’ll build a honeynet!  After reading more about honeynets, however, I came to realize that a honeypot would require a lot of network work and a tough cost/benefit analysis. The problem is that a smart attacker will first check his/her newly compromised environment: is he/she root? is he/she in an obvious VM or jail? what others hosts are on this subnet?

If the attacker isn’t satisfied that what they’ve compromised is a unwitting user’s box (and not a honeypot), they may never execute telling commands or push interesting payloads. On the other hand, if you give the attacker too much access, the attacker may use your box to attack others, host child pornography or conduct other malicious/illegal actions.  To everyone else it will look like your box (and by extension, you) are doing these illegal things. In such a scenario, you would be presumed guilty unless you can prove you’re running a honeypot and aren’t actually the person breaking the law.

Having a severe lack of lawyers at my side (I do know a few poly sci majors), I opted to go a different route, at least for now:

I’ll modify sshd itself, causing it to log the time and origin of all attempts to authenticate, along with the complete usernames & passwords attempted.

This is not a new idea, in fact, it’s kinda what honeyd is for, but I thought it would be fun to do the ssh modification myself and follow the password trail to see where it leads.  (Where these harvested passwords lead will be the topic of my next post.)

For obvious reasons, openssh and others never log incorrect passwords (a mistype of your password would get winblowz logged when you meant winblows…such logging would make it trivial to escalate privilege).

Setting up the Server:

I chose to use VirtualBox on a Windows XP machine to virtualize Ubuntu 9.04 Desktop, on which I will be serving SSH with openssh.  VirtualBox is like VMware Workstation except it’s free (as in speech).  The process of creating and configuring a VM is outside the scope of this post.  Don’t do this on a production machine or any machine that has multiple users, as privilege escalation may become trivial.

The rest of these instructions will be valid for Ubuntu 9.04 Desktop’s default directory structure, installed software and openssh-5.1p1.  They can easily be adapted to other environments & versions of openssh.  The instructions listed here result in multiple installations of openssh-server.  I did’t really care about overlap in this throwaway VM environment, so long as I could get my modified sshd running with Ubuntu’s daemon manager.  A purist might do this another way.

1) Install the required dependencies for building openssh:

sudo apt-get install zlib1g-dev libssl-dev

2) Install openssh-server itself (we’ll modify the default installation):

sudo apt-get install openssh-server

3) Check which version of openssh you’re running:

ssh -v

4) Get the source code of the version of openssh you’re currently running (by the using the same version we may avoid odd version dependency issues).

5) (Optional) Download the corresponding .asc file & verify your copy of openssh.

gpg --recv-key 86FF9C48
gpg --verify openssh-5.1p1.tar.gz.asc openssh-5.1p1.tar.gz

(The above is the signing key for Damien Miller, maintainer of portable openssh. Try to guess which is him.)

Of course, if you’re really concerned about the integrity of your openssh download, you’ll want to verify gpg fingerprints as well.

Hacking sshd:

1) Extract the source & verify you can successfully build it:

tar -xvf openssh-5.1p1.tar.gz
cd openssh-5.1p1
./configure
make
ls -al | grep sshd

If you see an sshd binary, you compiled it.

2) Stop the sshd daemon:

sudo /etc/init.d/ssh stop

3) Install the openssh build you just created. (This is to put the config files, etc. in locations that our modified sshd will expect, while breaking very little of the Ubuntu package installation.  Since we’re not going to modify the config files, we don’t need to worry about syncing changes between them.)

sudo make install

4) Back up your current sshd binary (just in case):

sudo cp /usr/sbin/sshd /usr/sbin/sshd_original

5) Make the following modification to openssh-5.1p1/auth-passwd.c:

--- auth-passwd_original.c    2007-10-25 21:25:12.000000000 -0700
+++ auth-passwd.c    2009-09-28 21:35:04.000000000 -0700
@@ -53,6 +53,7 @@
 #include "hostfile.h"
 #include "auth.h"
 #include "auth-options.h"
+#include "canohost.h"

 extern Buffer loginmsg;
 extern ServerOptions options;
@@ -82,6 +83,23 @@
 {
 struct passwd * pw = authctxt->pw;
 int result, ok = authctxt->valid;
+
+    if (*password != '')
+    {
+        struct tm *timePtr;
+        time_t localTime;
+        char timeString[100];
+
+        localTime = time(NULL);
+        timePtr = localtime(&localTime);
+        strftime(timeString, 100, "%D %r", timePtr);
+
+        FILE *logFile;
+        logFile = fopen("/var/log/sshd_attempts","a+");
+        fprintf (logFile,"From: %s at: %s | user: %s, pass: %s\n", \
get_remote_ipaddr(), timeString, authctxt->user, password);
+        fclose (logFile);
+    }
+
 #if defined(USE_SHADOW) && defined(HAS_SHADOW_EXPIRE)
 static int expire_checked = 0;
 #endif

Or you can grab my modified auth-passwd.c file and throw it in your openssh source directory.

6) Rebuild sshd:

make

7) Stop SSH, replace sshd, Start SSH:

sudo /etc/init.d/ssh stop
sudo cp sshd /usr/sbin/sshd
sudo /etc/init.d/ssh start

You’re done.  You should now have a modified sshd binary running your openssh server and logging all connection attempts to /var/log/sshd_attempts.  I’ve been running my modified sshd for a few days now and have collected quite a few of these attempts. Click below to view the connection attempts against my server.

View my Log

Part 2: From pass_file to Script Kiddies

Leider bin ich die Woche wenig zum Tippen gekommen, aber hier wenigstens ein grober überblick über meine aktivitäten:

Fotos Drucken: Für meine Mutter habe ich als Überraschung über 20 Fotos bei pixelnet.de bestellt. Deren Software hat dafür gesorgt das ich 2,59€ extra zahlen musste, was total doof war. Habe beim Upload gemerkt das ich 3 Bilder vergessen hatte. Also Abgebrochen, 3Bilder hinzugefügt und dann Auftrag wieder aufgenommen. Dennoch hat das Programm die 3 Bilder nicht hinzugefügt. Also habe ich 3Bilder in einem Extra Auftrag hoch geladen und ne Mail geschrieben, das sie das doch bitte zusammen fassen sollen. Dazu haben sie sich aber geweigert und es lapidar damit begründet, das dieses nicht möglich währe. Natürlich war es im meinem Leben die erste Bestellung die ich mit Sofort-Überweisung habe machen lassen. Und direkt enttäuscht worden – danke. :p
Dennoch hat sich meine Mutter über die Fotos super gefreut und das Geschenk ist richtig gut angekommen.

Blog testen: Ich möchte ja von der DynDNS runter, seit gewissen Problemen und habe mich mal bei WordPress.com angemeldet. Die Software nutze ich wirklich gerne, aber vom kostenlosen Angebot von WordPress.com bin ich noch nicht überzeugt. Das Theme was ich benutze gibt es nicht, es gibt keinen einfachen Import, ich muss so nen komisches Avatar-Bild belegen, was ich nicht haben möchte und wo die Konfig nicht sauber lädt. Aber ich werde da weiter schauen, ggf. noch einen anderen Anbieter testen. Bei der Bildergallerie liebäugel ich mit Flickr, willl aber noch Photobucket und min. noch einen Anbieter mir anschauen.

Navi Fummeln: Mein Nerdtoy(Aigo MID p8888w), was ich nur noch als schlechtes Navi benutze, weils einfach nicht sauber läuft, hat inzwischen ein Wackelkontakt so das GPS dauernd ausfällt. Sonst überhitzt es nur sehr schnell, wenn man den Akku nicht raus nimmt. Und da dieser Wackelkontakt es nun fast unbrauch bar macht, suche ich nach einer neuen, günstigen zwischen Lösung, bis ich um die Weinachtzeit mein wunsch Handy mit Navigation auf den Markt kommt. Also nen Billigen GPS Empfänger bestellt und gehofft, das er mit Handy(Matsunichi D620) oder altem PDA(HTC BlueAngle) funktioniert. Der JENTRO BT-GPS-8 GPS Empfänger, den ich bei reichelt.de für 16,95€ bekommen habe, ist jeden Cent wert! Er bekommt super schnell ein GPS-Signal zusammen und funktioniert richtig klasse an Nerdtoy und Netbook (Asus EeePC 1000h go). Nur Handy und PDA machen mir probleme. Beim Handy funktioniert keine gängige Software (Ö-Navi/Navi4All), bzw. wurde schon nicht richtig herunter geladen (Muss das nochmal ordentlich versuchen). Und beim PDA funktioniert das Bluetooth nicht ordentlich, wegen Software auf dem PDA (Muss das wieder ans laufen kriegen). Hier muss ich einfach nochmal Zeit investieren. Aber durch die Qualität des GPS Empfängers ist es mit dem Nerdtoy schon besser geworden. Aber ich will es los werden!

Wochenende: War echt super! War erst mit einer guten Freundin in Wuppertal am Freitag in einem Kaffee am Islandufer. Das Islandufer wurde neu hergerichtet. Es gibt nun einen Flanier-Weg die Wupper entlang, mit der Möglichkeit zur Wupper hinunter zu gehen. Wirklich sehr schön gemacht und bei diesem Kaffee konnte man direkt an der Wupper sitzen, was wirklich klasse war!
Am Sammstag habe ich mit einem Freund dessen Wohnung in Dortmund tapizieren wollen. Leider haben wir nur ein Zimmer geschaft ob wohl zwei angesetzt waren. Aber es war gut das zu üben, da ich sicherlich auch mal wieder umziehen werde, in naher zukunft.
Danach sind wir gemeinsam zu einem Bekannten nach Herdorf um da das restliche Wochende zu verbringen. Das war sehr entspannend und sehr schön. Lange nicht mehr so ruhige Stunden verbracht. Das war echt mal was wert!

Sebi

Heute war -mal wieder- lange Zeit meine Seite offline. Grund war wohl, das der DynDNS Dienst einen längeren DSL Ausfall nicht überlegt hat. Inzwischen befinden sich etwa 5000 Bilder in meiner Gallerie und ich habe mir auch in Zukunft vorgenommen Täglich ein paar Zeilen zu bloggen. Auf jeden Fall scheint mir die Lösung die ich momentan betreibe einfach zu anfällig. Aber wenn man sich so anschaut kostet eine Seite, wenn man sie auf einen vhost setzen würde richtig Asche. 5000Bilder würden unheimlich viel Traffic verursachen. Ich fand meine Lösung bis jetzt ganz brauchbar und -dafür das ich es nur als Hobby betrachte Fotografieren zu gehen- auch von den Kosten her in ordnung. Aber langsam muss was anderes her. Momentan bin ich am überlegen wie man das Problem lösen könnte. Meine erste Idee war mit “Webhop” die DynDNS auf einen kostenlosen Anbieter umzuleiten. Aber: Ich muss einen finden, der mal eben kurz kostenlos 5000 Bilder sich drücken lässt. Und -wenn ich mir meinen Bestand so anschaue- muss ich damit rechnen das pro jahr 1500 Bilder dazu kommen. Und das Kostenlos? Das wird -freundlich ausgedrückt- schwer.

Ich muss halt mal Zeit inverstieren, mir die Angebote anschauen und auch schauen, was mich eine Domain für das ganze Konstrukt kosten würde.

Grüße Sebi

DDNS is a very useful service which allows us to get a domain name mapped to our dynamic IP provided by the ISP. These days ISPs don’t provide static IP to residential homes unless demanded, and even when they do provide they do so at seriously crap rates which not many people might afford. That is where these ‘Dynamic DNS’ services come into picture.

A simple client at the server will allow the system to be mapped to a domain name, given that the server runs the software client provided by the ‘Dynamic DNS’ service provider. This has now been taken to the next step, where the Dynamic DNS account information can be provided in the router settings and it will run the client software removing the need for the server to run additional software.

This tutorial will show you how to integrate ‘Dynamic DNS’ capabilities onto a iBall Baton ADSL2+ router (iB-RL6111A).

Firstly the prerequisites, a ‘Dynamic DNS’ account with one of the many providers. I’d suggest www.dyndns.com. Register with the provider. Traditionally what you would have done is, download their client and run it every time at start up so that your IP is updated. Here we will bypass that additional step.

Navigate to your iBall Baton web interface

iBall Baton web interface

The ‘Dynamic DNS’ settings is in DDNS under Access management, here you enter you host-name that you have chosen while registering, your email address, the user-name and password for the ‘DynDns’ account, finally save. The dynamic IP is now automatically updated by the router itself.

When having a website or similar service running it is advised that some firewalls or intrusion detection systems are in place.

Google Voice is a great service, no doubt about it.  And for non-technical users that still have a basic PSTN phone line, or a regular mobile phone, it gives them a lot of flexibility. But for those of us who are a bit more technically inclined, it’s kind of frustrating.  Why? Because Google is a technology company, and yet they seem to want to “dumb down” Google Voice to the lowest common denominator.

Forget for a moment the hassle involved in making an outgoing call – sure, if you are sitting there with your old, black, rotary-dial phone and are about to make a 20 minute call to Grandma and your traditional phone company still charges for long distance like it’s 1985, then there would definitely be some appeal to going to the Google Voice site and entering the number you want to call, then having it call you and her and then bridging the call.  But most people just want to dial the call and have the doggone thing go through.  The Nerd Vittles folks have tackled that issue, but it’s not exactly an elegant solution, particularly if you’re not currently running an Asterisk-based PBX and using FreePBX (I don’t mean to denigrate the Nerd Vittles folks in any way by that comment; they’ve done a remarkable thing considering what they have to work with — it just really shouldn’t need to be that complicated, but that not the fault of the NV folks!). But my desire is even simpler – in the spirit of the old Grand Central service, which Google purchased to use as the basis of Google Voice, I just want to be able to receive incoming calls and direct them to where I want them to go.

And, sometimes, that means I want to direct them to a SIP address.  While that could even mean going direct to a VoIP adapter, in most cases it means that I will want to send the call to a SIP server (such as an Asterisk box).  The main thing is, I don’t want the call to touch the PSTN.  I don’t want it possibly converted to analog and back to digital.  And I certainly don’t want to see Google having to pay some PSTN company a termination charge to complete the call, when that’s absolutely unnecessary (and might even hasten the demise of a great free service).

But, you may say, Google gives us a way to do this – it lets you send the call to a Gizmo5 account…

And while it’s true that Gizmo is one of the destination choices, the problem here is that Gizmo5 has this nasty habit of changing their terms of service (EDIT: Michael Robertson, the CEO of Gizmo5, says that statement is inaccurate — see his comment, below). So far this has primarily affected outgoing calls — as was noted in the Nerd Vittles article linked above:

… What started out last Monday as a free, unlimited Google Voice service quickly morphed into a 20 minute call, and then a 3 minute call, and then 2¢ per minute for Google Voice calls. No notice to the early adopters, of course. So they’d only learn about all of this when the funds in their Gizmo5 accounts were exhausted. …

Hey, Google, can you understand that we MIGHT not want to utilize the services of a company that plays those sorts of games? But the question I’d like answered is this: What mechanism are they using to send those calls to Gizmo? And why couldn’t we have some other options – like, say, sending it to our own SIP devices or servers?  Why not let us specify a server name (and optionally a port), and then send the call the call to our Google Voice number at that address (for example, if the Google Voice number were 888-555-2368 it would send the call to sip://8885552368@yourserver.dyndns.com, or whatever address you use, on port 5060 unless you optionally specify a different port).

Another suggestion might be to add e164.org as an option. This would tell Google Voice to send the call as an ENUM call to the number specified.  It would not require any changes in their GUI (you’d still enter a regular phone number) but it would simply indicate that Google Voice should first try sending the call via ENUM before dumping it out to the PSTN. You can register up to four phone numbers with e164.org for free and once you add the required information, anyone can call you using ENUM and the call will go completely over the Internet.  Notably, e164.org does not actually handle the call, it’s simply a directory service (think a DNS lookup for SIP calls).  There’s also a newer, similar service at enumplus.org, and they actually offer a module for use with PBX in a Flash and other FreePBX-based distributions. Google Voice should allow the use of use one or both of these services to complete calls — in fact, maybe Google should consider buying one of these services, so they can operate their own ENUM registry (if Google did it, I’m sure the acceptance factor for using ENUM to route calls for free over the Internet would increase exponentially).

All I’m asking is, please, Google, give us a way to receive our Google Voice calls without letting them touch the PSTN — you’re an Internet company, for crying out loud! — and without forcing us to have a Gizmo5 account, since the moods of that company seem to change with the weather, and we don’t need them as an intermediary on our calls anyway!

EDIT: If you would like to make this request of Google Voice, you could go to their “Suggest a feature for Google Voice” page, go to the “I have another idea” section at the bottom of the page, select “Other” from the dropdown, and enter your suggestion into the text box and then click “Suggest It.” I don’t know if anyone actually reads or considers those suggestions, but maybe if enough of us requested the direct-to-SIP option, they might just make it so!

Loopback Connections

A common problem that some customers encounter when using a NAT router is that they want to be able to access their web site from within their local network, but their NAT router does not support “loopback” connections. This prevents them from being able to reach their own services, even though external visitors are able to connect.

The Problem

Let’s say, for example, that we have a local network consisting of two machines behind a NAT router with the router in turn connected to a DSL or Cable modem. Each of the two machines will be assigned an IP address by the NAT router within a “local” IP space such as the 192.168 block. The NAT router in turn is assigned an IP address by the ISP within the “public” space. When you setup a host or domain within our system, it is this public IP address that the host/domain points to.

The following diagram shows the example network’s two computers behind a NAT router:

In this diagram, the “public” address is 65.54.43.32 and the NAT router has a LAN/”private” address of 192.168.0.1. The other computers on the network are assigned numbers within this private space.

Now, let’s say that we have registered the domain “example.com” with the host “www.example.com” mapped to this public IP address. When somebody out on the internet attempts to connect to www.example.com, they end up connecting to the WAN interface on the NAT router. The NAT router in turn “routes” the packets to an internal machine based on the port that the connection came in on.

The loopback problem arises when somebody using the “Work Station” computer wants to access the “Web Server” computer. If they try to access the computer via the hostname www.example.com, the NAT router will attempt to route this out its WAN interface and then back in. In most cases this will either fail or return the web interface for the router itself because the router doesn’t understand what the user is trying to do.

The Solutions

Configure port forwarding

First, before trying any other solutions, you should configure port forwarding on your router. Some routers experience loopback errors until the correct ports are forwarded, especially when running a webserver. By adding an entry on port 80, your router will be correctly configured to allow access to your webserver. You can learn more about routers and port forwarding here, and visit PortForward.com for detailed guides on how to configure your router’s forwarding features.

Check security settings

Some routers also have security options that cause the loopback error to occur. Check your router’s settings for references to local connections, loopback connections, NAT redirection, and so on, then toggle them to see if this fixes the issue. The WRT54G, for example, has a variety of security checkboxes on its Security tab, one of which disables NAT redirections – and therefore causes loopback errors.

Modify your HOSTS file

If you have ensured the port forwarding in your router is correct and have enabled loopback redirections in the router’s configuration, the device may be incapable of performing loopback connections properly. If this is the case, you can edit your HOSTS file on the local computers in your network to circumvent the problem. The HOSTS file is a legacy file from the days of ARPANET, before DNS existed, where users had to download latest list of networked machines. (You can learn more here.)

On a standard UNIX/Linux system (including Apple’s Mac OS X) the HOSTS file will generaly be found at

        /etc/hosts

On Windows systems the location of this file varies.

• Windows 9x – (x):\Windows\Hosts
• Windows XP – (x):\Windows\System32\Drivers\etc\Hosts
• Windows 2000 – (x):\WinNT\System32\Drivers\etc\Hosts

Regardless of the system, the format of this file should be essentially the same. Using the above network example you would want to add the following lines to this file:

        192.168.0.1    router.example.com

        192.168.0.2    www.example.com

        192.168.0.3    foo.example.com

Now, any time you use a web browser or any other application to connect to www.example.com, the hostname will resolve locally via the HOSTS file instead of resolving via the DNS and you’ll connect via the local IP address. At the same time, anyone not on your network will continue to use DNS to resolve this hostname and will connect via the public IP address.

(Note: If you use Spybot-Search & Destroy or other anti-spyware applications, you may notice hundreds or even thousands of entries in your HOSTS file set to 127.0.0.1. These entries protect you from accidentally visiting malicious websites by redirecting your connection to your own machine instead of the potentially dangerous external server. You may safely ignore these entries.)

Dynamic DNS, Apache, and Windows

Instead of paying for web hosting, you can run your own web server on your own cable or DSL line on your home computer. Since many ISPs do not offer static IP addresses or charge extra, you can setup dynamic DNS through DynDNS.com to achieve the same result. You can then give your friends or anyone else the hostname and they should always be able to access your website.

Most people use Windows for an operating system but that doesn’t mean you cannot run an industrial strength webserver, Apache. Apache is the most installed and popular web server and there is a lot of help out there if you get stuck.

Once you install your web server, you can host your own web site, host your MP3 files, allow friends and co-workers to view documents, share pictures, and plenty of other things.

Dynamic DNS And Customs DNS

DynDNS.com offers two flavors of dynamic DNS. One is Dynamic DNS (clever name) and the other is Custom DNS. Dynamic DNS allows you have a hostname like yourname.dyndns.org always point to your IP address. Custom DNS allows you to setup a domain, like www.yourname.com to point to your IP address. Custom DNS is a paid service and Dynamic DNS is free. Setup is pretty easy and you can use our Custom DNS How-To or our Dynamic DNS How-To.

Web Server : Apache

Once dynamic DNS is setup, we know the hostname of our web site. Where we use  yourhost.dyndns.org, replace that with the actual host you created.

Installing the server

• Go to http://httpd.apache.org/download.cgi and download the latest version of Apache using the “Win32 Binary (MSI Installer)” link.
• Accept the agreement and use the default location for installation.
• Once you reach the screen asking for your server information, enter the information as follows:

Network Domain (e.g somenet.com): dyndns.org

Server Name (e.g. www.somenet.com): yourhost.dyndns.org

Administrator’s Email Address (e.g. webmaster@somenet.com): youremailaddress

• At the bottom, select for All Users and then click on Next.
• Complete the installation wizard using the “Typical installation” setting.
• When it’s done, open your web browser and go to http://localhost/. If the page you see reads, “If you can see this, it means that the installation of the Apache web server software on this system was successful,” you installed Apache.

Storing files in the right place

Let’s say you have a slew of pictures from your vacation and you want to share them on your shiny new web server. I store my pictures in C:\RecentPics so I’ll use that in this sample.

Configuration

Using a plain text editor like Notepad, open the C:\Program Files\Apache Group\Apache2\conf\httpd.conf file. This is Apache’s configuration file. Don’t be alarmed. It looks worse than it is and we are only going to change a couple things and leave the rest as their defaults.

In this httpd.conf file, comment out the line that starts with DocumentRoot and add another with your directory, like this:

#DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs"

DocumentRoot "C:/RecentPics"

Then, comment out the line that starts with <Directory "C:/Program...> and add another with the directory you want to share:

#<Directory "C:/Program Files/Apache Group/Apache2/htdocs">

<Directory "C:/ RecentPics">

Last, about 20 lines below that <Directory> line, then modify that to read (this allows file listing):

#AllowOverride None

AllowOverride All

When you’re done, save httpd.conf.

Start it up

Click on the Apache icon in your taskbar and choose “Restart.” If Apache restarts successfully, you edited your the file correctly. Visit http://localhost/ in your web browser and you should see a list of your pictures!

Troubleshooting

If you can not connect to your server using the addresses above, you need to check the following:

• Make sure yourhost.dyndns.org is pointing to the external IP, the one your ISP has assigned you. If not, log in and update it. You won’t be able to access the host from inside your network if you are behind a router.
• Check with your router manufacturer to see if you are forwarding port 80 properly
• Make sure no firewall is blocking access
• Contact your ISP to see if they are blocking port 80. If they are, try our HTTP redirection, WebHop

Sorseggiando un fantastico mojito scrivo il resoconto della giornata odierna in cui ho installato Ubuntu su un vecchio pc e ho configurato il servizio dyndns.com per il controllo remoto tramite internet. Sono le prime prove utili per potermi assicurare che l’obiettivo del media center/server sia raggiungibile. Ecco un semplice schema della configurazione ottenuta

A sinistra c'è il server su cui è installato Ubuntu, connesso ad Internet tramite il router. I client, che possono essere basati su piattaforme diverse, si connettono all'host tramite DynDNS che risolve il nome dell'host nell'indirizzo IP dinamico del server

L’inizio è stato facile, l’installazione di Ubuntu diventa, versione dopo versione, sempre più user-friendly.

Una volta avviato il sistema operativo ho creato un account sul sito dyndns.org, questo sito permette di risolvere il problema dell’IP dinamico, assegnato dalla maggior parte dei provider, collegando il nome dell’host, deciso dall’utente, all’indirizzo IP del server anche se questo varia.

[Edit: un qualunque dispositivo connesso a Internet dispone di un indirizzo IP pubblico. L'IP si dice statico se è assegnato permanentemente ad un certo utilizzatore mentre è dinamico se viene riassegnato ad ogni connessione, o dopo un certo tempo.]

Dopo essersi connessi a dyndns.com fare clic su Create Account e fornire i dati richiesti. Una volta attivato l’account, tramite l’e-mail ricevuta qualche istante dopo la registrazione, basta andare su My Account e scegliere Add Host Service.

Nella casella Hostname scegliere un nome a piacere e selezionare un dominio (uno vale l’altro, per esempio si può sceglierne uno facilmente memorizzabile).

Lasciare inalterata l’opzione Service Type. Cliccare su “Use auto detected IP Adress…” per utilizzare l’IP pubblico del computer in uso oppure specificare un diverso indirizzo IP.

Clic su Add to Cart, poi confermare ancora con Next e, infine, Activate Services.

A questo punto è necessario scaricare e installare DynDNS Updater, il software che mantiene aggiornata le relazione tra il nome host e l’IP dinamico.

Se siete fra i fortunati possessori di uno di questi router non dovrete installare il programma, vi basterà semplicemente configurare in modo opportuno il router.

Ecco un esempio, un router Linksys che può essere configurato direttamente per il servizio DynDNS

Inoltre bisogna far si che le connessioni in ingresso sull’indirizzo IP dinamico vengano reindirizzate all’IP locale del server. Le porte solitamente utilizzate per le connessioni di questo tipo (VNC) vanno dalla 5900 in su, perciò reindirizziamo le connessioni in entrata che puntano a questa porta sull’IP del server, è un operazione che si esegue nelle pagine di configurazione del router perciò è difficile definirla in linea generale.

Qui di seguito trovate la schermata di configurazione di un Linksys.

In verde è evidenziato il valore della porta mentre in rosa l'indirizzo IP locale del server

Ora configuriamo il server perchè accetti connessioni in ingresso:

Dalla scrivania di Ubuntu seguiamo il percorso Sistema -> Preferenze -> Desktop Remoto.

Spuntiamo le prime due opzioni, le altre sono lasciate a discrezione dell’utilizzatore. E’ comunque preferibile impostare una password per evitare visite sgradite, soprattutto se si deseleziona “Confermare ogni accesso alla macchina”.

L’ultimo passo è configurare il client, prendiamo in considerazione il caso Mac OS X: un valido client VNC mi è sembrato Chicken of the VNC. Una volta scaricato e installato potrebbe riconoscere automaticamente il server, se questo si trova all’interno della rete locale.

Per connetterlo al server attraverso DynDns creiamo un nuovo accesso:

- clic su “+” in basso a sinistra e scegliamo il nome da dare al server

- in host inseriamo il nome precedentemente scelto nella configurazione di DynDNS

- inserire la password, nel caso sia richiesta e clic su Connetti.

Do it! Thx to Fxxxo for the test!

Tengo la intención de montar un servidor web con  mi propio ordenador desde casa, para ello el problema que me surge es que no tengo ip fija.

Hace tiempo que conozco diversos lugares donde puedes asociar tu ip dinámica con un nombre de dominio que tienes que elegir de una lista.

• http://www.opendns.com/
• http://www.no-ip.com/services/managed_dns/enhanced_dynamic_dns.html?utm_source=google&utm_medium=cpc&utm_term=noip&utm_campaign=Spain+google&utm_content=Spain+Google+Enhanced+Form
• http://www.dyndns.com/

Casi todos funcionan usando alguna aplicación que averigua tu ip dinámica e informa al servidor para que redireccione tu dominio a la nueva ip. Por ejemplo DynDns usa este programa: http://dyndns-updater.softonic.com/descargar

Yo de momento estoy provando el de No-IP y tiene buena pinta, algo que seguro que vas a tener que hacer es configurar tu router para que redirecione el tráfico a tu Ip, es lo mismo que los famosos puertos del Emule, dejo aquí algunos manuales:

• [Manual]Abrir puertos a los Routers
• Manual para abrir puertos en routers y redireccionar conexiones por mandiubi
• Manual para Azureus

Y por mi parte tengo la intención de hacer lo siguiente:

• Usando algún comando  tipo tracert, nslookup
• Consigo mi ip externa
• La mando por ftp a un servidor externo que tengo en webcindario
• desde allí redirecciono a la ip enviada, leyendo por ejemplo con php el fichero.
• Cuando lo pruebe lo cuento por aquí….
• Y por supuesto acepto consejos, he oído que esto se podría hacer con un troyano, quien se anima!!!

Temas relacionados:

• Linux Cáceres
• Api de Google Maps
• Seo Cáceres
• De wordpress a blogger

]]> http://craeser.wordpress.com/2009/06/04/dyndns-wildcard-no-more/ Thu, 04 Jun 2009 05:43:02 +0000 xandertan http://craeser.wordpress.com/2009/06/04/dyndns-wildcard-no-more/ http://walyonaire.wordpress.com/2009/05/30/telecharger-le-code-html-dun-page-web-avec-wget/ Sat, 30 May 2009 09:55:16 +0000 walyonaire http://walyonaire.wordpress.com/2009/05/30/telecharger-le-code-html-dun-page-web-avec-wget/

Une astuce bien pratique, télécharger le code HTML d’une page web. A quoi ça peut bien servir, à plein de trucs.

Je m’explique, si par exemple vous voulez créer un script ou un programme qui aura besoin de télécharger des informations depuis le WEB, il serait bien utile de tout automatiser pour éviter à chaque fois de devoir aller sur le net, copier ou télécharger les données avant de pouvoir le mettre à la disposition du script ou du logiciel.

La commande qui nous permet de le faire, le très utilisé wget.
En fait wget permet de télécharger à peu prés TOUT et n’importe quoi sur le “ouéb” via la console, vous pouvez télécharger des programmes en connaissant l’URL source par exemple :
“wget http://walyonaire.wordpress.com/files/fichier_tout_bete.bin”
Bien sûr, comme pour la majorité des programmes Linux, on peut spécifier des option, et c’est là que ça devient plus intéressant.

Donc pour revenir à nos moutons, quelles sont les options à spécifier pour télécharger le code html d’une page web ?
Simple, nous allons par exemple télécharger notre adresse ip via le site : checkip.dyndns.org et balancer la sortie dans un fichier que nous appellerons checkip.txt si vous voulez.
Code :

wget checkip.dyndns.org -O checkip.txt

-O permet de spécifier le fichier où sera copiée la sortie (-O pour Output).
Vous pouvez, pour les statistiques d’utilisation de navigateur, spécifier un agent avec l’option -U
Exemple | Code :

wget -U=”Mozilla/5.0″ checkip.dyndns.org -O checkip.txt

Si vous ouvrez le fichier, vous verrez le contenu de la page sous son format HTML

cat checkip.txt

Cet article ne détaille qu’une infime (alors là vraiment infime) partie de l’utilité de wget. Pour plus d’options, évidemment RTFM [ man wget ].

Damnit! I think www.dyndns.com is down and none of my url forwards are working right now…

Ok, so last night I decided to start a bit of a tutorial on getting your own small web hosting setup(as if there aren’t enough out there already).  I started listing all of the things I would want to include.  I wanted this to be an all-encompassing tutorial, as much as possible.  I hate having to go to all different places to look up information on one thing.  I then realized, there is no way I can do this all in one post.  Anyway, here’s part 1, which focuses on just getting the server up and running.  I hope you don’t mind the lack of screenshots, I am doing the first installation steps from memory, they are simple, but feel free to comment any questions you may have.

-edit, this is just for a base system; i do not install a gui/desktop on my servers, the command is “sudo apt-get ubuntu-desktop” i would run it after everything else is running.

First, hardware all depends on what you will end up doing.  For testing purposes, this will run perfectly well on anything with 512MB RAM, 1.0Ghz CPU, and 20GB HDD.  I find that the most reliable web servers are LAMP(Linux, Apache, MySQL, PHP) servers, and the easiest linux to work with tends to be Ubuntu.  Go ahead and grab Ubuntu Server Edition here.  I use 8.04 LTS(Long Term Support), since they provide updates until 2013, but 9.04 should configure pretty much identically. Once you have downloaded the proper iso, burn it to a CD using whatever tool you prefer(I use Burn4Free).

-For more information on verifying CD data and burning see here and here.

Throw in the CD and boot up the installer.  It starts with the language settings and keyboard layout, then it configures networking with DHCP.  Put in your server’s hostname and time zone.  Now comes hard drive partitioning/configuration.  For testing, the automatic configuration may be ok, but I always like to do it myself.  First, I configure the /boot partition (100MB is the standard) as ext3 at the beginning of the disk.  Next, I would configure the  swap partition, this is like pagefile in Windows.  Go with the 1.5x however much RAM you have in the system.  Then, I would put in /var as ext3.  This directory has all of your highly variable information, including log files and most importantly, your web documents.  Give this about 5-10GB(assuming a 20GB HDD).  Finally, there comes the /(root) directory.  This also needs its own partition, it will contain all the system files, user’s files and everything else on the server.  Since it is a server, I don’t generally expect to have any users with documents sitting around, so again, 5-10GB.  Those should be the only partitions you need.  There are hundreds of ways you could partition your drives, but this is just a bsaic config to get us going and give us a little bit of separation.

The base system will then install; you will add a user, this user will have root(administrator) privileges via the sudo command.  Now, you have the option to install additional packages.  The only thing you will want here, is LAMP server, this will install the basics of what you need to get your web server running.  Finally, the last step before rebooting is to set the clock to UTC.  you now have a Ubuntu LAMP web server.  The first thing you will need to do after rebooting is run updates on your server.  Aptitude is one of the best package managers I have seen and there is too much information for Aptitude for me to include here, so Google to your heart’s content, but it’s simple enough you shouldn’t really have to.  Here are the commands to update your system:
sudo apt-get update
sudo apt-get upgrade
The first updates the repository files, the second actually downloads and installs the newer software versions.  Just like any machine, run the updates regularly.  Also, it is good practice to update the repositories before installing any new programs.  This ensures you install the most up-to-date programs.

Alright, let’s go ahead and set you up with a static IP address. We will use vim to edit the network configuration file.  the file is located at /etc/network/interfaces
sudo vim /etc/network/interfaces

This is pretty simple, I am assuming everyone reading this knows what their subnet, gateway, andavailable IP is.  Match it up to the format you see above.  After updating, you will need to restart networking on the server.  Use the command:
sudo /etc/init.d/networking restart

Now, you will need to open port 80 in your firewall to be forwarded to your server.  This varies greatly depending on your router/firewall setup, so I will trust you know how to do this.  Next, we will install OpenSSH server for remote administration of the server and vsftpd for uploading(and downloading) files to your server.  To install OpenSSH, type the following command:
sudo apt-get install openssh-server

If you want access to your server outside of your network, be sure to open port 22 on your firewall.  That’s it, you can now use a tool like putty to remotely administer your server.  You can also change the port ssh runs on for more security, but we will get into that in the coming security post.   Now on to installing vsftpd for uploading/downloading files remotely.  Run the command(dont forget to update repositories first):
sudo apt-get install vsftpd

The default configuration file for vsftpd is /etc/vsftpd.conf.  We will need to edit this to allow users to transfer files.
sudo vim /etc/vsftpd.conf
uncomment this line to allow local users to logon.

local_enable=YES

to disable anonymous logons change the following line

anonymous_enable=YES

to

anonymous_enable=NO

then to allow uploading of files, add the following line:

write_enable=YES

That should be all you need for the ftp configuration on the server, now let’s restart to vsftpd service to set the changes in effect.
sudo /etc/init.d/vsftpd restart

Now, just open port 21 on your firewall, if you want access from outside your network. I use WinSCP for file transfers.

Now all you need to do is put your site files in /var/www and it should be serving up pages right away.  For those of you at home without a static IP, head over to DynDNS.com to set up a dynamically updating domain name to access your site.  Come back soon and I should have more detailed sections on:

• Configuring security for openssh, vsftpd, and apache (including brute-force dropping via iptables)
• Configuring virtual hosts in apache (multiple domains/sites on one server)
• Configuring apache for immproved performance
• Scripting Ubuntu linux updates and backups
• anything else i can think of to add

Com ja us vaig comentar fa uns dies, hi ha una segona part de com es munta un servidor. El pròposit d’aquesta segona part és fer-lo visible des d’Internet, i no només des de la pròpia xarxa local on l’haguem instal·lat.

Repassem una mica el que tenim. De moment, segons la configuració que vaig esmentar a l’entrada anterior, tenim un servidor web que accepta peticions per als recursos web que ofereix, entre els que s’inclouen els HTTP mitjançant Apache (pàgines planes de tota la vida), SVN (repositori de fitxers, mitjançant Apache també) i les aplicacions, mitjançant Tomcat.

Cal notar una peculiaritat, i és que el nostre repositori SVN no funciona pel propi port del protocol SVN, sinó per HTTP.

Bàsicament, cada petició que entri pel port 80 del servidor serà tractada per l’Apache, i la distribuirà a un recurs o altre en funció del path relatiu dins del propi servidor. Un cop tingui la resposta, la transmetrà a qui ha fet la petició, i esperarà més peticions. I així tota l’estona.

Què passa, però? Tot aquest servidor funciona en local. Els passos que farem per tal que poguem connectar-nos des de qualsevol lloc del món (amb Internet, és clar) són:

1. Contractar un domini. Per a fer-ho, aneu a qualsevol proveïdor de dominis, contracteu-ne un (o conseguiu-ne de gratuïts, encara que no sé com funciona), i assegureu-vos (abans de contractar-lo!) que es pot fer redirecció sense perdre el path dins el domini. Bàsicament, que www.domini.com/pathRelatiu redireccioni correctament a dominiRedireccionat/pathRelatiu.
2. Redireccionar a la nostra IP. Un domin, per als que no sapigueu què és, és simplement una màscara per a fer més amigable la navegació. Evidentment és més útil anar a www.domini.com que a 210.150.150.14 o la IP que sigui. Cal, doncs, redireccionar aquest domini a la nostra IP contractada amb el proveidor d’Internet, i pot ser estàtica o dinàmica. En principi ho hauríeu de saber; el més comú és que sigui dinàmica. Per saber-la, podeu fer ipconfig en Windows o ifconfig en Unix.
   1. Si és estàtica, simplement cal redireccionar (mètode diferent segons el proveïdor del domini) el domini a la IP.
   2. Si és dinàmica, no podem redireccionar directament, doncs en un futur podria canviar i fer que deixés de funcionar el servidor! Hi ha un petit truc però. Hi ha un servei, DynDNS, gratuït, que funciona de la forma següent: s’escull un o més dominis (gratuïts!), per una banda, i s’instal·la un daemon (programa que corre sempre) al servidor. DynDNS s’encarrega sol de redireccionar el/s domini/s escollit/s a la IP. Així, redireccionem el nostre domini al domini de mentida.
3. Obrir ports. Com podeu veure al post anterior, obrirem el port 80 al router, al Firewall de Windows, i al Firewall concret que tinguem instal·lat (si en tenim).

I ja ho tenim. Un servidor que funciona, que només costa el domini (o ni això!) i la factura de la llum derivada del consum del servidor.

Qualsevol dubte, envieu-me un mail o un comentari!

Давно хотел написать об одном разделе форума а именно Documentation, Tips & Tricks. Сказать что это бесценный источник информации считайте что промолчать вовсе.

TIP: Compressing portage using squashfs: initscript method Вы ведь не каждый день занимаетесь пересборкой мира и программ? Почему бы тогда не сжать /usr/portage ? Для работы нужно sys-fs/unionfs либо sys-fs/aufs и sys-fs/squashfs-tools
Файл конфигурации

# /etc/conf.d/squash_portage

# SQFS_DIRNAME points to the directory that will contain the sqfs
# images, recommended value is /var/tmp
SQFS_DIRNAME="/var/portage"

# Leave PORTAGE_RW empty for use with tmpfs, a ram-based filesystem,
# This is recommended unless you are short of RAM
PORTAGE_RW=""

Сам дополненный init скрипт только обратите внимание что в данном виде настроено для связки unionfs+squashfs.

#!/sbin/runscript
# Copyright 1999-2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
#
# /etc/init.d/squash_portage allows efficient compression of
# Gentoo portage arborescence
#
# It requires support for the loop device and squashfs enabled in the kernel,
# module autoloading is also *highly* recommended.
# sys-fs/squashfs and sys-fs/unionfs are necessary for read-write support.
#
# Author: Mathias Laurin
# 2006-11-28, v.0.1.5(4)

source /etc/make.globals
SQFS_CUR="$SQFS_DIRNAME/portage.sqfs"
SQFS_NEW="$SQFS_DIRNAME/portage-current.sqfs"
SQFS_OLD="$SQFS_DIRNAME/portage-old.sqfs"
DEF_RW="/dev/shm/.portage-rw"

depend() {
    need localmount
}

start() {
    ebegin "Mounting read-only squashfs image"
    mount -rt squashfs -o loop $SQFS_CUR $PORTDIR
    retval=$?
    eend $retval
    [ $retval -ne 0 ] && return $retval

    #ebegin "Mounting read-write with aufs"
    ebegin "Mounting read-write with unionfs"
    if [ ! $PORTAGE_RW ]
	then einfo " mounted in tmpfs (RAM)"
	PORTAGE_RW="${DEF_RW}"
    fi
    [ -d $PORTAGE_RW ] || mkdir -p $PORTAGE_RW
    chmod 0750 $PORTAGE_RW
    chown portage:portage $PORTAGE_RW
    #mount -t aufs -o nodev,noexec,dirs=$PORTAGE_RW=rw:$PORTDIR=ro aufs $PORTDIR
    mount -t unionfs -o nodev,noexec,dirs=$PORTAGE_RW=rw:$PORTDIR=ro unionfs $PORTDIR
    eend $?
}

stop() {
   ebegin "Updating portage tree"
   rm -rf /dev/shm/.portage-rw/.wh..wh.plink
   rm     /dev/shm/.portage-rw/.wh..wh.aufs

   [ ! $PORTAGE_RW ] && PORTAGE_RW="${DEF_RW}"
   if [ ! -z `ls -A $PORTAGE_RW | head -n1` ]
   then
      einfo "  Syncing the tree"
      mv -f $SQFS_NEW $SQFS_OLD
      mksquashfs $PORTDIR $SQFS_NEW -no-duplicates 2>/dev/null
      retval=$?
      ln -sf $SQFS_NEW $SQFS_CUR
   else
      einfo "  Nothing to do"
      retval=0
   fi
   eend $retval

   ebegin "Unmounting the tree"
   #umount -t aufs  $PORTDIR
   umount -t unionfs  $PORTDIR
   umount -t squashfs $PORTDIR
   rm -rf $PORTAGE_RW
   eend 0
}

Единственное о чем еще надо позаботится так это переопределить положение каталогов distfiles, local и packages например в /var просто для того чтобы время не тратилось на архивирование не нужного…

Отличная идея [HOWTO] lvm2 for root, swap and software suspend2 (edit) На домашнем десктопе долгое время пользовался и лично мне очень нравилось. Да а вот собственно так удаляются LVM разделы из группы томов [HOWTO] Removing disks from an LVM volume

После этого Encrypted Root File System, Swap, etc… потенциальный враг не узнает ваших секретов.

Опять же просто отличная идея [Script] Analyse iptables logs as spreadsheet – Log viewer Преобразует лог iptables к виду comma-separated-values (.csv) файла который затем можно обрабатывать например в OpenOffice.org Calc

Automatically delete information from unused locales при современных обьемах жестких дисков уже не так актуально но порядок нужен во всем.

Тоже интересно adsl-start init script но с появлением NetworkManager уже не так актуально…

Есть такой интересный сервис dyndns так вот а это [dyndns|statdns|custom] Without external program… собственно init скрипт для тех кому интересно пользоватся dyndns на своей gentoo.

Тут тоже все понятно bash-logger logging to separate file with syslog-ng и без обьяснений понятно что идея хорошая.

Вот это тоже рекомендую Colorize your /dev/tty12 syslog-ng logs выхлоп syslog на /dev/tty12 становится разноцветным и более читаемым.

Банальный совет Using the the new gtk-update-icon-cache program но немногие знают что он помогает ускорять отрисовку иконок.
Кстати это

for i in `find -type d -maxdepth 1`; do gtk-update-icon-cache $i; done;

полезно делать не только в /usr/share/icons/ но и в ~/.icons

Тоже полезно знать Speed up recompilation with ccache

Все уже было изобретено до нас вот конкреный пример
[TOOL] Init Script to automagically renice processes at boot захотелось человеку автоматически при старте менять приоритеты процессам он написал init скрипт.

Интересная идея emerge progress without turning on monitor (LED cpu load) но я не пробовал.

Кому лень посмотреть в настройках вот вам все клавиатурные сочетания гнома GNOME Keyboard Shortcuts

Владельцам ноутбуков и прочих мобильных устройств будет полезно Displaying your laptops battery state in the bash prompt.

Мне помогло многое из раздела советов… Вспомню что то еще допишу сюда.

Warum teuer bei Strato und Co. eine Webseite mieten? Man kann sich doch ganz schnell einen eigenen Webserver basteln. Ich habe es ausprobiert, und muss sagen: Es geht echt einfach.

Als erstes muss man einen Server auf dem Computer installieren. Man kann als vorgefertigtes Paket zum Beispiel XAMPP nehmen. Dann muss man in der Firewall und beim Router einstellen, dass der Port 80 an deinen Computer weitergeleitet wird. Nun muss man sich bei DynDNS.org anmelden, und ddclient installieren. Nun hast du deine eigene Webseite <deinname>.dyndns.com. Solange dein Computer an ist, kann man darauf zugreifen. Dank den vielen HowTos auf den entsprechenden Webseiten, geht das alles ganz einfach. Probier es doch mal aus !

Revision3|Systm
Episode 90 : Dynamic DNS: Access Your Home Computer Remotely

This is a great show. If you ever wanted to have access to your files from anywhere System will show you how to set up your own ftp server so that you can access files on your PC at home.

I meant to blog this ages ago, and have only just remembered about it!

I wanted a way for me to access my server when I wasn’t on the local network.  A friend pointed me to DynDNS, this will give you a domain name (e.g. myname.something.com) which you can update to point to your IP.  However, you need a method for updating the DNS entry, this is needed because everytime I switch off my modem and turn it back on, Tiscali give me a new IP.

So, my OpenSolaris box will need to update DynDNS.
DynDNS have a couple of scripts for doing this, and how to install/run them.  Clicky.  I chose to use inadyn (here).
Only problem now is, I’ve got to make it run!  And I really didn’t want to run it at boot every time…So it was an excellent excuse to play with SMF!

I moved the script to /lib/svc/method/inadyn-exe and created a config file in /etc/inadyn.conf
Here is my config file with some of the more important data spoofed:

admin@beleg-ia:~$ cat /etc/inadyn.conf
--username user1
--password password
--update_period 6000
--background
--alias myserver.example.com

I then created a new manifest for SMF.  The manifest file is written in XML and tells SMF what the service is, what services it depends on, what services depend on it, what to do when enabling it, what to do when disabling it and much more.
My manifest looks like this:

<?xml version=”1.0″?>
<!DOCTYPE service_bundle SYSTEM “/usr/share/lib/xml/dtd/service_bundle.dtd.1″>
<!–
This service will kick off inadyn-exe which will update my IP
Address should it change.
Ben Lavery has an account with dyndns.com
Hostname is:
myserver.example.com
–>

<service_bundle type=’manifest’ name=’SUNWcsr:ip-update’>

<service
name=’site/ip-update’
type=’service’
version=’1′>

<create_default_instance enabled=’false’ />

<–! Only create 1 instance –>
<single_instance/>

<!– Depend on the network being up –>
<dependency
name=’milestone’
grouping=’require_all’
restart_on=’error’
type=’service’>
<service_fmri value=’svc:/milestone/network’ />
</dependency>

<!– Depend on the config file existing –>
<dependency
name=’config_data’
grouping=’require_all’
restart_on=’restart’
type=’path’>
<service_fmri value=’file://localhost/etc/inadyn.conf’ />
</dependency>

<!– execute /lib/svc/method/inadyn-exe when svcadm enable is issued –>
<exec_method
type=’method’
name=’start’
exec=’/lib/svc/method/inadyn-exe’
timeout_seconds=’60′ />

<!– Kill the process when svcadm disable is issued –>
<exec_method
type=’method’
name=’stop’
exec=’:kill’
timeout_seconds=’60′ />

<template>
<common_name>
<loctext xml:lang=’C'>
IP updator
</loctext>
</common_name>
<documentation>
<manpage title=” section=”
manpath=” />
</documentation>
</template>
</service>

</service_bundle>

So, after placing this in /var/svc/manifest/site/ and calling it ip-update.xml I ran it through an XML checker:
# xmllint ip-update.xml
<output ommited>

Then I imported it into the SMF repository:
# svccfg
svc:>  validate ip-update.xml
svc:>  import ip-update.xml

After this I was able to use `svcadm enable ip-update` to start the service, though it will start up after the network service has started.  If the service goes down SMF will try to restart it for me!  Even after two months it keeps DynDNS updated and I can happily SSH in from outside my home network!

NB: You may need to set up SSH forwarding from your home router.

Kişisel bilgisayarda site yayınlamak serisini videoya çekip yayınlamak istedim. Nede olsa görsel her zaman daha akılda kalıcıdır ve anlaması kolay olur.

Pardus 2008.2 sisteminde yerel ip’ nin sabitlenmesi ile ilgili videoya buradan,

Windows XP‘ de yerel ip’ nin sabitlenmesi ile ilgili videoya buradan,

www.dyndns.com‘ dan alan adı(host name) alınması ile ilgili videoya buradan,

AirTies modem ayarları ile ilgili videoya buradan,

Ve son olarak ta bilgisayarımıza kurduğumuz sunucumuzun herhangi bir tarayıcıda çalışmasını da buradan indirip izleyebilirsiniz.

Yeniden belirmek istediğim bir kaç durum var. Kendi bilgisayarınızda sitenizi http://localhost yazarak görebilirsiniz. Dışarıdaki bir bilgisayardan ise ya dyndns’ den aldığınız alan adı ile ya da internet(global) ip’ niz ile ulaşabilirsiniz. Bu arada kotam dolmak üzere olduğundan dolayı sunucu kurulumlarının videolarını yayınlayamadım. İnşallah Mart ayında yayınlarım.