Beyond the Sky

Nowadays I am so lazy to blog at here, I usually post up examples at LBE. But for this incident I have to put here.

DON'T UPGRADE TO EDGY IF YOU FEEL COMFORTABLE TO DAPPER.

If anythings goes correctly you have no problem, if you make a mistake, you are dead meat! I screw up when upgrade. Ya one thing, never go and sleep and leave the installation goes. I left my online upgrade running and I sleep yesterday night. When I wake up and so excited, I type my password on screensaver and log in to a new instant of desktop instead of login back to the current login.

I didn't realized that my GUI upgrade program is still not complete, refers to toydi, the upgrader will ask you series of question whether to replace all the stuff or not. That is so idiot, sure i wanna upgrade and replace... haih!

Then I restart my fresh edgy, its gone. the kernel and many configurations are not setup completely. Anyway install fresh edgy is fun! while installing edgy, you still can online in the live cd environment. What kind of installation allow you to do that? Windows never allow you to do that!

Okay fresh install done in a short while, now i am buzying install the programs i need to use, And i discover more stupid stuff such as I need to install vim-full, firefox flash plugin problem etc.

Now its time for me to explain a bit of 2% of my iptables knowledge. You may wanna log the connections that trying to access you but failed. You must put the log before the reject rules:

-A RH-Firewall-1-INPUT -m state --state NEW -j LOG --log-level warning --log-prefix "BLOCK "
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited

It is very important to remember that, the rules will be read from top to down, if a connection is been accepted or rejected in the middle of the rules, rules below it will be ignore. That means if you put your log rule after reject rule, log action will not be take place. On the other hand, if you place infront of accept rule, you will log all the connection whether it success or failed.

I also wanna log down ssh connection, so i add ssh log rule infront of ssh accept rule

-A RH-Firewall-1-INPUT -p tcp --dport 22 -j LOG --log-level warning --log-prefix "SSH "
-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT

--log-level is used for me to indicate that the particular log must be recorded into another file by setting syslog.conf , will discuss later.

--log-prefix is used to inject wording infront of the log records, the purpose is to differenciate between block connection and ssh connection.

/etc/syslog.conf is a configuration file for log system daemon. All logging basically controls by syslogd, to manipulate which log goes to which file, we need to modified /etc/syslog.conf. I am not going to illustrate too much on what is syslog, you can always read up with "man syslog.conf"

The iptables log will goes to kern category of syslog, therefore to direct all iptables log to /var/log/iptables, edit /etc/syslog.conf with adding line bellow at somewhere:

kern.warning /var/log/iptables

For me I wounldn't like to dirty my /var/log/messages which it used to log all the system messages, so i modified the messages part into this:

*.=info;*.=notice;*.=warn;\
        auth,authpriv.none;\
        cron,daemon.none;\
        mail,news.none;\
        !kern.warning           -/var/log/messages

I add in the line "!kern.warning", to indicate syslogd don't write the log of kern with level warning to messages.

After that, do 2 fin action and you are done.

/etc/syslogd restart
/etc/iptables restart

Refers to http://my.opera.com/mysurface/blog/show.dml/289865 if you couldn't find iptables under /etc/init.d

p.s. : I donno why when I type dmesg, iptables log is still display. I tot dmesg reads from messages, it seems that I am wrong.

Disclamer: I do not take responsibily on the code above to be a right way, I just share my experience on iptables, do it at your own risk.

When I install firefox manually to breezy ubuntu is version 1.5.0.1. But after i upgraded to dapper, firefox tag with dapper is more latest. I realized that after upgrade to dapper, firefox still remains 1.5.0.1, actually the real case is new firefox is been install with different name. For my case it is

/usr/bin/mozilla-firefox.ubuntu

And I also realized that /usr/bin/firefox is just a symlink to /opt/firefox, which I manually install last time. To get the latest firefox, the steps are easy.

Maintain the old link to my manually installed firefox.

sudo mv /usr/bin/{firefox,firefox.old}

Create a symlink to link a new firefox

sudo ln -s /usr/bin/{mozilla-firefox.ubuntu,firefox}

Okay, double click the firefox and guess what, my bookmark is still remain to same, version changed., ap