Milena-velba Vintage Erotic Archive

The Core (The Core)

Well, this movie really my kind of movie, great action and emotion and a lot of technology (including information technology, which is my favorite) Plausible from the point of view of science fiction, in fact some scientists think the Earth's magnetic field is becoming weaker and eventually lose him completely as happened to Mars, has even said that we are close to a magnetic field reversal.

I think there were more deaths than necessary and very stupid, especially the first one, of the commander, which I do not remember the name, he died for being a toad out there also should have been put everyone back into the ship when they saw the lava began to enter the pocket, the lava would have been responsible for destroying the crystals, including one that had stuck to the ship.

bothered me a little of that final all escape fictional teacher and commander, would have been better to let them die an honorable death, as the astronauts' Deep Impact.

I was the question of how to reinforce the last explosion, the guy just puts the core of the reactor by the pump and it does this if possible? ie, is more plutonium placed next to a nuclear bomb if it increases the power of the explosion but that plutonium is protected by layers of metal and also isolated the explosive core of a nuclear bomb?

Well, the movie entertained me and it had good graphics, I just think they spent a little fiction.

Uterine Prolapse Cartoon

Connect to Server Lineage II through an SSH tunnel

Well, first of all thank you very much to Manuel Gulick to read previous entries and interest in the matter and also for taking the time to write and reawakened my interest in this story of tunneling.

As you know these issues and had tried on the blog in these two entries: Jump

• Firewalls using OpenSSH
• Jump a proxy that requires authentication
For

just that I will not explain here the details of SSH server configuration and so on. I'll just concentrate on talking about the issue that remained outstanding which is the connection to the game server.

About This entry

This entry is a tutorial that aims in the most graphic possible to illustrate a way to connect to a server to play Lineage II and when you are behind a firewall that does not allow connection ports directly in running the game using an SSH tunnel.

To make use of this technique is to have a relay team outside the firewall that is configured to serve the SSH protocol to a port that is accessible to the computer that is inside the firewall. For more information on this subject read the entry: Jump Firewalls using OpenSSH

One more comment, this technique only works with servers that do not modify the client but altering the hosts file to make the connection. It may work with a server to alter the client but that is not covered in this guide

Preliminary

Well first of all, to use the technique I explain below the computer that is inside the firewall must have an address static IP, so if the computer is receiving an address by DHCP will to take note of the addresses that the DHCP delivery and then set these parameters in the configuration, then we will see how:

we on Start → Control Panel.

There, under "Network and Internet" you click on the link "View network status and network tasks"

and in the window that opens on the panel the left choose "Manage Network Connections"

will now see a window with the network connection that has our team, we are going to click the right mouse button on the use connection and select "Status" in the Start menu:

The sale opens select "Details"

Here we note the following: IPv4 Address IP, IPv4 subnet mask, default gateway IPv4, IPv4 DNS Servers. These data will need them later so that we write down there somewhere and then close all open windows. Server Information

Well, we will also need the server to which we will connect the following information:

• Address Authentication Server IP Address
• game server IP
• authentication server port (usually 2106)
• game server port (usually 7778)

This information can usually get the hosts file that Most alter servers. The hosts file is in C: \\ windows \\ system32 \\ drivers \\ etc

For this example we are going to connect to server L2TheGame , information from that server is:

• Authentication Server: 78.46.17.80
• Game server (Phoenix [500x]): 78.46.17.80
• authentication server port:
• 2106 game server port: 7778

Tip:

best for this technique of tunneling is to play the opening directly l2.exe Lineage II (which is in the system folder) to avoid pass through the nProtect server and l2patcher. This is what I recommend and this is how take this guide.

hosts file modification

first thing we do is modify the hosts file. The hosts file is in C: \\ windows \\ system32 \\ drivers \\ etc, as this is a system file for editing will have to run notepad with administrator privileges (Right Click → Run as administrator) and open the file.
In the file you will see three lines like these:

# The patch edited this three lines ... 78.46.17.80 l2authd.lineage2.com

84.246.123.71 l2patcher.lineage2.com
216.107.250.194 nProtect.lineage2.com

only modify the first line, add a # at the beginning and then add another line below it, the then file should look like this: # The patch

edited this three lines ...
# 78.46.17.80 l2authd.lineage2.com
127.0.0.1 l2authd.lineage2.com
84.246.123.71 l2patcher.lineage2.com
216.107.250.194 nProtect.lineage2.com

now prove that the decision DNS for l2authd.lineage2.com server has been changed to localhost (127.0.0.1), so we provide a console window and run: ping

l2authd.lineage2.com

To which the system should respond:

Pinging

l2authd.lineage2.com [127.0.0.1] with 32 bytes of data:

Reply from 127.0.0.1: bytes = 32 time \u0026lt;1ms TTL = 128
Reply from 127.0.0.1: bytes = 32 time \u0026lt;1ms
TTL = 128 Reply from 127.0.0.1: bytes = 32 time \u0026lt;1ms TTL = 128
Reply from 127.0.0.1: bytes = 32 time \u0026lt;1ms TTL = 128

Ping statistics for 127.0.0.1:
Packages: Sent = 4, Received = 4, Lost = 0
(0% loss), Approximate
return in milliseconds: Minimum = 0ms
, Maximum = 0ms, Average = 0ms

Configure the network card

Well, here comes the secret of this post and what differs from previous ones. We will set up a dual IP address in our network card, for this we go back to Start → Control Panel

selecting "View network status and network tasks" under the category "Network and Internet"

and again on the "Manage network connections"

again click the right mouse button on the connection and this time select "Properties" from the Start menu:

We at the list and select the "Internet protoclo version 4 (TCP/IPv4)" and you click on the Properties button

select "Use the following IP address "and you click on the button" Advanced ... "

Top

where it says "IP Addresses" We click "Add"

First add the normal IP address of the computer (which we noted in the "Preliminaries" above), we also introduce the subnet mask and we click OK. Then go back to click on the Add button and add another IP. In this case add the IP address of game server, for example to accompany 78.46.17.80 and subnet mask 255.255.255.0

Ok, now where it says "Default gateways" We click the Add button and add the default gateway of our connection (We scored in the "Trial") let windows handle the metric by which we selected the box

Now we click the DNS tab

then where it says "DNS server addresses in order of use" we click on "Add" and add the DNS servers of our connection:

We click "OK" on all open windows until we get back to the window where network connections appear. Before proceeding we must prove that we can still access the Internet, to make it open the browser and look for any website, if we can see, we are ready to move forward.

would also be good to verify that the network card was with both IP addresses. For that we open a console and run: ipconfig

and verify that the connection has two IP addresses:

Wireless LAN adapter Wireless Network Connection:

specific DNS Suffix for connection. . :
Link-local IPv6 Address. . . : Fe80:: thereof 389d: 74c8: 67ee:
f52c% 11 IPv4 Address. . . . . . . . . . . . . . :
78.46.17.80 Subnet Mask. . . . . . . . . . . . : 255.255.255.0 IPv4 Address
. . . . . . . . . . . . . . : 192.168.0.174 Subnet Mask
. . . . . . . . . . . . : 255.255.255.0 Default Gateway
. . . . . : 192.168.0.1

Create the tunnel

Well, now it was time to create the SSH tunnel that will make us jump the firewall. For this example we will use the Putty GUI that is but would like the normal SSH console.

Open

Putty:

For "Host Name (or IP Address)" write the IP address of the relay team (the team that is outside the firewall). If the relay team is serving on a port other than 22 (for example, 80 as discussed in previous entries) must specify that port in the box beside it.

Then in the tree on the left we Connection → SSH → Tunnels

primroses we make sure the checkbox "Local ports accepts connections from hosts Other" is checked and then under where it says Add new forwarded port we write the following:

Source port: 2106 Destination
: 78.46.17.80:2106

We look to "Local" and "Auto" are selected and we click on "Add"
In this step we just make the tunnel to the authentication server, so you should replace 78.46.17.80 with the IP address of the server's authentication server where you play.

then add the forwarding to the server of the game:

Source port: 7778 Destination
: 78.46.17.80:7778

We look to "Local" and "Auto" are selected and we click on "Add"

Al Putty finished window should look something well.

Note:

In the case of L2 Phoenix server TheGame both the authentication server and the server of the game are on the same machine (have the same IP), however for many Lineage II servers this is not true. Notice that you did the forwarding to the correct addresses or the connection fails.

Well, now I recommend you save the session of Putty for use whenever you want to play and if something fails to be able to correct errors without having to retype everything. In the tree on the left selects the first Item (Session) and where it says "Saved sessions" enter a name for the session, such as "L2" and then click "Save."
The next time you open Putty you can click on the entry in the list and click "Load" and Putty charged again all parameters (including the tunnels). Connect and test

Ok. It seems everything is ready to connect and have fun. Click the button "Open" from Putty to connect, Loge with a user name and a valid constraseña. Before starting

Lineage notice that Putty is ready to do the Port Forwarding. To do so open a console and run: ipconfig

-N-a-p tcp

should see two ports open on listening, the 2106 and 7778: TCP 0.0.0.0:2106 0.0.0.0:0

; LISTENING TCP 0.0.0.0:7778 0.0.0.0:0 LISTENING

If all goes well so far subtracted just open the client of Lineage II and connect and you should be able to play normal. Congratulations! Technical Details

I'll explain in a bit because it works above. As you've noticed that you use the Windows feature to allow more than one IP address on the same network card (although it could have done with two NICs if that feature is unavailable).

What we did was to put the IP address of game server in the network card with a subnet mask of 255.255.255.0 and that is where lies the secret of this matter

When a system is to establish a connection with another system the first thing is to do a binary AND between its own IP address and subnet mask, in our case:

078.046.017.80 255.255.255.0
---------------
78.46.17.0

Then take the direction which will connect and make a binary AND the subnet mask, in our case:

078,046. ---------------

017.80
78.46.17.0 255.255.255.0

If the two addresses resulting from previous operations are different, the system knows to try to send the connection request through the gateway to the destination address is on another network, most, if they are equal (which happens in this example) the system knows that the destination address is within your own network so it is not send the request through the gateway, but through the network local.

As we stated that our IP address is 78.46.17.80 when the request is sent through the local network the recipient is again our own network card.

So what we have done here is to trick the system in a way to send a request normally sent through the gateway back to our system and we have made Putty listen for incoming connections on port 7778 ( as if a Lineage II server running on the local machine)

What happens in short is:

1. Open Client Lineage and write our data access
Lineage
2. l2authd.lineage2.com resolves the address, as we have added an entry to the hosts file that says that address is 127.0.0.1 Lineage II sends an access request to localhost on port 2106
3. Putty is listening on port 2106 when he forwards the request using Putty relay team to the real server authentication Lineage II (the client does not notice the difference)
4. authentication happens and Lineage II The list of servers that the authentication server sent back.
5. select a server to connect
6. Lineage II in this case is not resolved any direction but to establish a direct connection to the server. Puts a request in which network the IP address of game server (for example 78.46.17.80)
7. Windows binary makes operation mentioned above and concluded that that address is within the local network. Puts the request and it returns back to the network card.
8. Putty is listening on port 7778 so that it receives the request and forwards with the help of the relay team to the real game server. Establishing the connection and Lineage II shows the characters that appear in our account.

While we play Putty, and SSH server running on the relay team will keep the connection permanently. Lineage II client will not notice Firewall difference and think that the connection is admitted to a port.

Note that there may be extra lag:

Remember that SSH connections are encrypted, so your computer must encrypt the data before sending the team, washed and then this in turn must decrypt it to send the game server you are adding an additional node to the connection. All this can cause extra lag so the experience will never be the same as you would with a direct connection.

Internet Disconnection Letter

Create a Web radio station Icecast 2 and Ices 2 in Ubuntu

Well, this little tutorial will show how to create a Web radio station in Ubuntu icecast2 as a server using emission and ices2 as a source for the server. Although this can be done in any linux distribution I recommend a ubuntu. I did it with kubuntu 9.10 (karmic). Install the packages

Well, the first is to install the packages that will be needed for the station. If you prefer to use a graphical package manager like synaptic or adept no problem, leave it here anyway console code to do so. Packages that need are icecast2 and ices2

$ sudo apt-get install icecast2 ices2

Set Prepare

Icecast station

First prepare icecast. Icecast uses a xml configuration where all the parameters of the station as well as some files to the web interface, some default files are installed with the packages, you have to make a copy of them in the user directory that should not be run as root icecast .

First create a directory structure to house files and registry settings icecast, being in our home run: mkdir

$
$ cd icecast icecast
$ mkdir conf $
mkdir logs

we copy the default configuration file to the folder icecast we created. in kubuntu that file is / etc/icecast2/icecast.xml If the file is not there then you can use the find command to find this:

$ find /-name "icecast.xml"

Note: in some distributions of linux system folders are protected, users can not access them (even to read) if this is your case use sudo when the system tells you that you can not read files cd

$
conf cp $ / etc/icecast2/icecast.xml icecast.xml
$ sudo chown user : group

Since

icecast.xml that the file belongs to root chown we used to do that we now belong to us. Eye here! where I placed user and group must put your username and group respectively, usually ubuntu is the same group name to the username in my case, for example, both my username and my group are called sergio so the command would be: sudo chown sergio: sergio icecast.xml

We do not modify the configuration file before copying the folders that the icecast used for web interface. These folders are usually located in / usr/share/icecast2 but if not there remember that you can use the find command to locate them.

$ cd .. $
cp-r-L / $
web usr/share/icecast2/web cp-r-L / usr/share/icecast2/admin admin
$ sudo chown-R user: group admin
$ sudo chown-R user: group web

Remember to replace user and group for your username and group respectively.

Ok, now if we set up icecast to modify this configuration file that we copied:

$ cd conf $ kate icecast.xml

kate

If you can use gedit or other editor but try if possible to use an editor that will highlight the code to make you easier to locate the lines.

Well, let's go edit the lines in the order they appear in the file, so stay tuned.

\u0026lt;clients> 10 \u0026lt;/ clients>

This line sets the maximum number of clients (players) that can connect to your station. Usually this is adjusted according to the amount of bandwidth that is available for broadcast. A reasonable value is 50. If you wait more than 50 clients maybe this tutorial is not for you.

\u0026lt;source-password> hackme \u0026lt;/ source-password>

In this line by placing the password to the sources (in our case the ices2) will use to login to the server and send the music. It is recommended to change the default password to prevent someone else can give to your server.

\u0026lt;relay-password> hackme \u0026lt;/ relay-password>

In our case we will not use relays but you must change this password for security.

\u0026lt;admin-user> admin \u0026lt;/ admin-user>
\u0026lt;admin-password> hackme \u0026lt;/ admin-password>

This is the user name and password logearte used in the web administration module Icecast. I recommend you change both the username and password for security.

\u0026lt;hostname> localhost \u0026lt;/ hostname>

If your station is mounted on a server that you access with a domain that you purchased here put the name of the domain, miradio.org eg. If you're building a test server localhost you enough to leave.

\u0026lt;port> 8000 \u0026lt;/ port>

This is the port that will emit. Usually no need to change the port unless you have firewall restrictions or something.

\u0026lt;logdir> / home / user / icecast / logs \u0026lt;/ logdir>
\u0026lt;webroot> / home / user / icecast / web \u0026lt;/ webroot>
\u0026lt;AdminRoot> / home / User / icecast / admin \u0026lt;/ AdminRoot>

These three lines tell the icecast to store your records, where the files panel and web interface where the files panel web interface management . Here I have placed the routes that would use you too if you followed the tutorial, remember to change user by username.

Ok, in theory everything is ready to run Icecast. Now to try it. Running Icecast

Well, now prove that everything is working, run this command: $

icecast2-c icecast.xml

If the console does not throw any error then Icecast is already running, now will check the logs and web interface to see that everything is going well.

note: The console will block the Icecast NOT go to the console or you will close down the server, leave it there, open, open another console window or tab to make the steps that follow.

While in our home run: $

cd cd icecast
$ logs
$ cat error.log

You should see something like this:

[05/22/2010 13:08:33 ] INFO main / main Icecast
2.3.2 server started [22/05/2010 13:08:33] INFO yp / yp_update_thread YP update thread started
[22/05/2010 13:08:33] INFO connection / SSL capability get_ssl_certificate

not does not matter if the log is somewhat different, in reality what matters is that there are no errors and you see the line that says server started

now see the server status through the web interface. To do this on a browser go to http://localhost:8000/ address this we must make a server status page. Remember to enter the administration section you should enter the user name and password you specified in \u0026lt;admin-user> \u0026lt;/ admin-user> and \u0026lt;admin-password> \u0026lt;/ admin-password>

Ices

Prepare Well you already have a server running and ready to accept connections, however you still can not listen to music, basically because you have not told Icecast that play music. It's actually a bit more complicated, see:

Icecast streaming server is the charge of accepting requests entratentes and distribute the medium to the listeners that are connected but do not know anything about music or playlists, it handles the program which is called source (source). There are several different sources for Icecast including the most basic is the Ices developed by the same people who developed the Icecast but you can also use different sources if you prefer, such as VLC Player can act as a source for Icecast .

For this tutorial we will use as source for Ices and Icecast is easy and quick to configure. As with the Icecast create a directory structure in the home to organize files. Esanda in the home run: mkdir

$
$ cd ices ices
$ mkdir conf $
mkdir mkdir playlists
$ logs

Now copy the default configuration file for use with Ices playlists. Remember if you can not find the file to your command to locate find.

$ cd conf cp
$ / usr/share/doc/ices2/examples/ices-playlist.xml ices.xml
$ kate ices.xml

Now edit the configuration file Ices. Remember that we will in the order in which the lines appear in the file so pay close attention to keep going.

\u0026lt;logpath> / home / user / ices / logs \u0026lt;/ logpath>

This line tells Ices to save log files. Remember to replace user with your username.

\u0026lt;name> Example stream name \u0026lt;/ name>
\u0026lt;Genre> Example genre \u0026lt;/ genre>
\u0026lt;descriptione> A short description of your stream \u0026lt; / description>

These three lines contain the metadata of the station. It would be a good idea filled them with the correct data as the name of your station, gender and description. \u0026lt;param

name= "file" > / home / user / ices / playlists / PLAYLIST.TXT \u0026lt;/ param>

This line tells the Ices where find the playlist file. Later I will tell you how to create the playlist. Remember to replace user with your username

\u0026lt;param name= "random" > 0 \u0026lt;/ param>

This line tells the Ices if you play the playlist in sequence or randomly. Set it up to you the value you want. If you put in 1 Ices random entries will be playing

\u0026lt;param name= "once" > 0 \u0026lt;/ param>

This parameter tells whether to play Ices Playlist only once or be touched countless times. If you leave the value to 1 Ices will play the playlist once and when done close the connection to the server and end making the station can no longer hear more. If you plan to leave the station running all day for people to connect anytime you should set the value to 0 so that the cycle indefinitely Ices playlist.

\u0026lt;hostname> localhost \u0026lt;/ hostname>
\u0026lt;port> 8000 \u0026lt;/ port>
\u0026lt;password> hackme \u0026lt;/ password>
\u0026lt; mount> / example1.ogg \u0026lt;/ mount>

This is the server information. Here we put the information Icecast server through which we will issue. This information must match the information we had already set in the icecast.xml. in \u0026lt;password> \u0026lt;/ password> put the password we had put into the label \u0026lt;source-password> \u0026lt;/ source-password> of icecast.xml

\u0026lt;mount> In , \u0026lt;/ mount> we choose the mount point you want to broadcast. The mount point will be the end of the URL you use to listen to the station so it should not be exmaple1.ogg could give listen.ogg place or maybe something more descriptive but should not contain spaces and MUST end in. ogg because it is the codec used to Icecast and Ices issue if not put the. ogg some players will be left hanging without doing anything when trying to listen to the station.

\u0026lt;nominal-bitrate> 64000 \u0026lt;/ nominal-bitrate>

Is the last configuration, but an important one. Defines the bit rate at which issue your station. The higher the bit rate best audio quality but more bandwidth you need to keep all listeners connected. If you put more speed in bits that can support your channel to the number of listeners you expect the audience began to experience cuts in music or worse spontaneous disconnections.

If you are not sure that leaves the bitrate to use default bitrate is 64 kbps is a good quality for him. Ogg at least for most applications. To learn more about how to calculate the bandwidth you need to read the box below, but saltalo.

Calculating the bandwidth

If you're not sure how to know how many listeners can support your channel or what the maximum bitrate you can use without your listeners experience problems this section will give you some light on this subject:

Concurrent band width

The bandwidth is the extent of concurrent channel you need to broadcast. It is calculated as follows:

cb = b * n Where

cb is the bandwidth concurrently (in kbps), b is the bitrate that issue (kbps) and n the number of listeners who expect to be connected simultaneously. For example, if you're going to broadcast at 128kbps, and expect 50 simultaneous listeners: cw = 128kbps * 50 = 6400 kbps. So they need a channel of 6.4 mbps to support 50 simultaneous listeners at 128kbps if you emit

Traffic Limit

Some servers impose a limit on monthly traffic and when you go above or begin to charge most are either not let you cast more for the rest of the month. To see if your monthly limit is sufficient to support the station can be calculated as:

tb = b * n * at * 30 Where

tb is the total bandwidth of the month (in kbits ) b is the bitrate to be issued (in kbps), n is the average number of listeners per day and waiting at is the average amount of time that a listener will be connected to the day (in seconds).

So if issued at 128kbps, wait 50 listeners daily and each will be connected on average 5 hours a day listening to the station will have:

tb = 128 * 50 * 18000 * 30 = 402.33 GB

You will need a monthly traffic limit of at least 400 GB

Ok, you're ready to set Ices, now to create the playlist.

Create Playlist

The Playlist is just a file where each line is the path to a file. ogg, eg

/ home / user / music / anime / yui - rolling star.ogg
/ home / user / music / anime / boa - every heart.ogg
/ home / user / music / anime / gumi - catch you catch me.ogg
/ home / user / music / anime / porn graffiti - melissa.ogg

may be a bit cumbersome to create the list hand so you can use the find command to expedite the work, for example: $

find / home / user /-name "*. ogg"> PLAYLIST.TXT

This command will write to a file called PLAYLIST.TXT all. ogg find the folder / home / user / recalls again replace user your username. Ices Run

As you have prepared your playlist (which you have saved in / home / user / ices / playlists / PLAYLIST.TXT) you can start the ices. To do this you do the following while in your home: $

cd cd ices
$ conf $ ices2 ices.xml

Ok, if all goes well the console should display error messages, if so, the ices already running and sending data to Icecast media. Again, the console will be locked NO close the console or come down to Ices open another console window or tab to the next steps.

We will verify the status of Ices, for it, from our home:

$ cd cd ices
$ logs
$ ices.log

cat should see something like this:

[22/05/2010 18:20:55] INFO ices-core/main started Ices 2.0.1 ...
[22/05/2010 18:20:55] INFO Requested
signals/signal_usr1_handler Metadata update [22/05/2010 18:20:55] INFO playlist-basic/playlist_basic_get_next_filename Loading playlist from file "/ home / sergio / ices / playlists / PLAYLIST.TXT "
[22/05/2010 18:20:55] DBUG playlist-basic/shuffle Has-been shuffled
Playlist [22/05/2010 18:20:55] INFO playlist-builtin/playlist_read Currently playing "/ home / sergio / Music / J-Music / YUI / From Me To You/11.ogg"
[ 5/22/2010 18:20:55] INFO stream / ices_instance_stream Connected to server: localhost: 8000/yui.ogg
[22/05/2010 18:20:55] DBUG Reencoded / reencode_page Reinitialising Reencoded for new logical stream
[22/05/2010 18:20:55] INFO encode / Encoder initialising in VBR encode_initialise mode: 2 channels, 44100 Hz, nominal

128000 Basically what you should look for is a line like [22/05/2010 18: 20:55] INFO playlist-builtin/playlist_read Currently playing "/ home / sergio / Music / J-Music / YUI / From To me You/11.ogg " that tells you Ices read and began broadcasting one of the files you put in the playlist.

can also check the status of the server from the web interface going to http : / / localhost: 8000 there is to receive the mount point you configured with the metadata that you placed in the file.

Play Station

Ok, finally the moment you have been waiting for. Listen to the music the station broadcasts. You can do this, for example with VLC Player:

Middle menu select Open Network Stream, in the box type in the address: http://localhost:8000/ Mount.ogg ( mount.ogg replaces the mount point you've placed in \u0026lt;mount> \u0026lt;/ mount> ices.xml on file) and then click the Play button.

If all goes well the music you listen to radio broadcasts. Cards! Stop

issue Ok. I will tell you how to stop the broadcast. Remember when we open consoles Ices and Icecast well, for you simply stop issuing press CTRL + C on the console to stop the programs. The best practice, of course, is that the first stop and then Ices Icecast because if you do it the other way round Ices unexpectedly lose connection to the server which is not recommended.

as not to block the console

is possible to run Icecast and Ices without the console is locked. To do this you run the commands by adding an ampersand (&) at the end as well:

$ icecast2-c icecast.xml &
$ ices2 ices.xml &

In doing so the system will respond with something like this:

[1] 2923

That number is the pid (process id) of Icecast is number identifies the process in the system and the need to stop the issue later. If you lose number or the station has been broadcasting for a long time and I do not remember you can retrieve it using the command: $

ps ax does not kill him forcibly. When you do see that the system responds with something like this: [1] + Done icecast2-c icecast.xml

So you know that the process is complete. Useful tools

Mp3 to ogg

When setting up a radio station with Icecast and Ices one of the first questions that arises is: How do I convert an Mp3 to ogg? The answer is very simple for our comfort, to convert a mp3 to ogg on Linux just a console command but first make sure you have installed these packages if you do not already have:

$

sudo apt-get install mpg321 vorbis-tools Now to convert to mp3 ogg:
music.mp3

$ mpg321-w - huge people moving around the city:

because of the mess that they put together could not go to my Astronomy class. Damn, Bogotá has the worst urban service buses are dirty, unsafe, they do what they want, stop where they please and still complain. And besides all make stupid stoppages that disrupt the normal order around the city.

Nothing, hopefully not to yield to their demands, before they put more taxes to pay for what they did today, that there was chaos in the city now has no excuse. Learn to provide good service and then if Complain.