ip stories

[Cisco] Auto Archive Configuration - Save Cisco Config Periodically

ipstories — Tue, 16 Sep 2008 10:03:14 +0000

Tired of saving your cisco configuration manually ?
And changes made very often & too lazy to back up.
This how to save your configuration automatically & periodically.
– Below sample save in weekly period.
– And save configuration weekly to disk2 of my Core Router.

But firstly check your IOS support or not (12.4 for e.g).
Here how to check :

Your-ROUTER(config)#archive

How to configure :

Core-1(config)#archive
Core-1(config-archive)#path disk2:config-backup
Core-1(config-archive)#time-period 604800
Core-1#dir disk2: (sample)
5 -rw- 3276 Sep 12 2008 10:14:02 +07:00 config-backup

Other options at archive level :

default              Set a command to its defaults
exit              Exit from archive configuration mode
log                   Logging commands
maximum        Maximum number of backup copies
no                    Negate a command or set its defaults
path                 Path for backups
rollback           Rollback parameters
time-period     Period of time in minutes to automatically archive the running-config
write-memory Enable automatic backup generation during write memory

a. rahman isnaini r.sutan

[DUN] Dial Up Network / VPDN Error 691

ipstories — Tue, 16 Sep 2008 09:11:10 +0000

error 691 : access was denied because the username and/or password was invalid on the domain

You may find error as below once dialing a private network or a number.
One of the reason what might caused this is : CHAP/PAP setting in your provider
Please ensure that your Provider Radius supports CHAP for PPP Authentication.

a. rahman isnaini r.sutan

[Media Player] K-Lite Mega Codec Video Renderer & Subtitle Error

ipstories — Mon, 15 Sep 2008 00:28:49 +0000

K-Lite Codec as one of most compatible video player that support many codecs compared to others media player.

First installation by default Video Renderer is set to Old Renderer which not allow you to load the subtitle correctly.
Here how to overcom this :

Change Playback output of Direct Show Video in View > Option tab setting.

a. rahman isnaini r.sutan

[IPv6] Implement Simple IPv6 Firewall in FreeBSD - IPFW

ipstories — Fri, 12 Sep 2008 06:02:10 +0000

[Old file]

Below some rules of implementing firewall in FreeBSD.
Using IPFW (please compile your kernel, if it’s not supported).
It’s easy as IPv4.

# Simple Firewall :

(allow network 2404:170::/32 to any host)
ip6fw add 100 allow all from 2404:170::/32 to any in via fxp0

(allow network 2001:dc6::/32 to any host)
ip6fw add 200 allow all from 2001:dc6::/32 to any in via fxp0

(allow all ipv6 to host 2404:170:ee02::10)
ip6fw add 300 allow all from :: to 2404:170:ee02:ee02::10 in via fxp0

(deny other all traffic).
ip6fw add 1000 deny all from any to any in via fxp0

a. rahman isnaini r.sutan

[Mobile Internet] Compete with Telkomsel Flash, INDOSAT launch “ISAT Eco”

ipstories — Wed, 10 Sep 2008 08:47:31 +0000

Since 1.5 GB Volume Based I’ve subscribed limited for 3 months “low rate” promotion.
And as well justifying 1.5 GB is pretty much againts my requirement.
Choosing INDOSAT Eco should fits what I need (POP3, SSH, Telnet, bit browsing).

-
ISAT Eco is Unlimited Product with speed of 256 Kbps till 2GB of volume achieved.
Exceeding this defined quota the speed will be adjusted to 64 kbps.
Not bad, 2 GB still pretty much quota I need to spent :).

Now I don’t have to worry for quota over limit & pay for that over usage.
Though I believed, I even couldn’t spent this 2GB in a month All I need to pay is Rp. 100.000 or with Tax will be Rp 110.000 (USD 110).

The Experience…
Even sometimes my bandwidth meter shows that it’s not really 256 kbps strictly allocated but burst a bit higher.

This just my test this morning [Sept, 15] I believe BTS-BSC-MSC in idle capacity due to everybody in a meeting or meet they boss for reports.

a. rahman isnaini r.sutan

[IPv6] Enabling IPv6 on IRC Server

ipstories — Tue, 09 Sep 2008 07:55:22 +0000

To enrich IPv6 application, this tells how to enable IPv6 on your IRC server.
Add host ipv6 address in file : /ircd/ircdV4/etc/ircd.conf (or anywhere you placed) & check running pid then kill -1 pid.

=========================

listen {
flags = hidden;
host = “202.159.33.34″;
port = 6667;
host = “2404:170:33::34″;
port = 6667;
};

=========================

PID TT STAT TIME COMMAND
527 ?? Ss 4660:21.87 bin/ircd

Issue :

root# kill -1 527
root#netstat -an | grep tcp6 | grep 6667

tcp6 0 0 2404:170:33::34.6667 *.* LISTEN

Here You go..

* Now talking in #indonet
weks
* BULEMASARO (~BULEMASAR@2404:170:253::26.) has joined #indonet
-
BULEMASARO is ~BULEMASAR@2404:170:253::26. * saRBeni
BULEMASARO on #indonet #root
BULEMASARO using indonet.id.allnetwork.org Indointernet Internet Service People
BULEMASARO actually using host 2404:170:253::26
BULEMASARO has been idle 1min 45secs, signed on Tue Sep 09 15:39:38
BULEMASARO End of /WHOIS list.

ervin a. taufik &
a. rahman isnaini r.sutan

[IPv6] Mikrotik Hotspot Not Working - IPv6 Installed on NIC

ipstories — Mon, 01 Sep 2008 09:17:52 +0000

Till now I don’t have a good solution for running IPv6 simultanously with Mikrotik Wireless Hotspot.
The condition :

- Your LAN has a dual stack IPv6 / IPv4 installed
- You have to connect to Mikrotik Hotspot Gateway Enabled
- Your first access is browsing and will be redirected to Mikrotik Login Page

The Issue :

No matter you LAN NIC UP/DOWN or we can say connected or not..
With IPv6/IPv4 Dual stack installed, Your Wifi status is Connected but You have error page “Address Not Found” while trying to browse to log in.

What I have done :

Uninstalling IPv6 on Your NIC will help much.
The redirected login page, will be nicely appear waiting for your to enter username & password It’s not happened on my another wifi network.

a. rahman isnaini r.sutan

[Cisco-Juniper] SSH from Cisco Router to Juniper OS

ipstories — Mon, 01 Sep 2008 08:19:44 +0000

Spending my time…
Trying to limit login from certain hosts include Cisco routers (OS Version Image : c7200-jk9o3s-mz.123-13.bin”) on a Juniper. The connection allowed is ssh.

Allowing cisco routers doesn’t seem to give a remote login successfully connected.

Cisco#ssh -l boss 192.168.1.145 [connection error:0]

Got this SSH log error on Juniper show log message tailed :

Sep 1 10:21:47 JunOS-GW sshd[38925]: Did not receive identification string from 192.168.1.146
Sep 1 10:21:47 JunOS-GW inetd[2541]: /usr/sbin/sshd[38925]: exit status 0xff00
Sep 1 10:22:15 JunOS-GW sshd[38926]: Did not receive identification string from 192.168.1.146
Sep 1 10:22:15 JunOS-GW inetd[2541]: /usr/sbin/sshd[38926]: exit status 0xff00
Sep 1 10:22:18 JunOS-GW sshd[38927]: Did not receive identification string from 192.168.1.146
Sep 1 10:22:18 JunOS-GW inetd[2541]: /usr/sbin/sshd[38927]: exit status 0xff00
Sep 1 10:22:23 JunOS-GW sshd[38928]: Did not receive identification string from 192.168.1.146
Sep 1 10:22:23 JunOS-GW inetd[2541]: /usr/sbin/sshd[38928]: exit status 0xff00
Sep 1 10:35:52 JunOS-GW sshd[39135]: Did not receive identification string from 192.168.1.146
Sep 1 10:35:52 JunOS-GW inetd[2541]: /usr/sbin/sshd[39135]: exit status 0xff00
Sep 1 10:36:03 JunOS-GW sshd[39136]: Did not receive identification string from 192.168.1.146
Sep 1 10:36:03 JunOS-GW inetd[2541]: /usr/sbin/sshd[39136]: exit status 0xff00
Sep 1 10:36:04 JunOS-GW sshd[39137]: Did not receive identification string from 192.168.1.146
Sep 1 10:36:04 JunOS-GW inetd[2541]: /usr/sbin/sshd[39137]: exit status 0xff00
Sep 1 10:36:05 JunOS-GW sshd[39138]: Did not receive identification string from 192.168.1.146
Sep 1 10:36:05 JunOS-GW inetd[2541]: /usr/sbin/sshd[39138]: exit status 0xff00

The symptom : Your outbound SSH on Cisco Router is version 1, while your juniper by default is version 2. Please add/enable ssh protocol-version 2 (v2) as well.. on your Juniper.

You@JunOS-GW# show
ssh {
root-login deny;
protocol-version [ v2 v1 ];
connection-limit 10;
}

[edit system services]

you@JunOS#set system services ssh protocol-version v1
you@JunOS#set system services ssh protocol-version v2
you@JunOS#set system services ssh protocol-version v1 v2 (nope sure this one :)) try it)

Then commit ! [Thanks to Ang Kah from Bangky.Net for Inspiring]

a. rahman isnaini r.sutan

[Juniper] Hacking Port SSH2 Juniper Real Log - Source 200.111.82.154

ipstories — Mon, 01 Sep 2008 03:56:00 +0000

I just found that one of JunOS-GW ssh opened in my network. This IP source 200.111.82.154 had been attempted many times by scanning many ports for trying to login via SSH.

Now is restricted.

Sep 1 02:00:02 JunOS-GW sshd[36977]: Failed password for abby from 200.111.82.154 port 59755 ssh2
Sep 1 02:00:02 JunOS-GW inetd[2541]: /usr/sbin/sshd[36977]: exit status 0xff00
Sep 1 02:00:06 JunOS-GW sshd[36982]: Failed password for tamara from 200.111.82.154 port 59986 ssh2
Sep 1 02:00:06 JunOS-GW inetd[2541]: /usr/sbin/sshd[36982]: exit status 0xff00
Sep 1 02:00:10 JunOS-GW sshd[36984]: Failed password for tasha from 200.111.82.154 port 60213 ssh2
Sep 1 02:00:10 JunOS-GW inetd[2541]: /usr/sbin/sshd[36984]: exit status 0xff00
Sep 1 02:00:13 JunOS-GW sshd[36987]: Failed password for theresa from 200.111.82.154 port 60446 ssh2
Sep 1 02:00:14 JunOS-GW inetd[2541]: /usr/sbin/sshd[36987]: exit status 0xff00
Sep 1 02:00:17 JunOS-GW sshd[36989]: Failed password for thomas from 200.111.82.154 port 60676 ssh2
Sep 1 02:00:18 JunOS-GW inetd[2541]: /usr/sbin/sshd[36989]: exit status 0xff00
Sep 1 02:00:21 JunOS-GW sshd[36991]: Failed password for tiffany from 200.111.82.154 port 60915 ssh2
Sep 1 02:00:21 JunOS-GW inetd[2541]: /usr/sbin/sshd[36991]: exit status 0xff00
Sep 1 02:00:25 JunOS-GW sshd[36993]: Failed password for timothy from 200.111.82.154 port 32917 ssh2
Sep 1 02:00:25 JunOS-GW inetd[2541]: /usr/sbin/sshd[36993]: exit status 0xff00
Sep 1 02:00:29 JunOS-GW sshd[36995]: Failed password for peaches from 200.111.82.154 port 33136 ssh2
Sep 1 02:00:29 JunOS-GW inetd[2541]: /usr/sbin/sshd[36995]: exit status 0xff00
Sep 1 02:00:33 JunOS-GW sshd[36997]: Failed password for peewee from 200.111.82.154 port 33384 ssh2
Sep 1 02:00:33 JunOS-GW inetd[2541]: /usr/sbin/sshd[36997]: exit status 0xff00
Sep 1 02:00:36 JunOS-GW sshd[36999]: Failed password for merlin from 200.111.82.154 port 33614 ssh2
Sep 1 02:00:37 JunOS-GW inetd[2541]: /usr/sbin/sshd[36999]: exit status 0xff00
Sep 1 02:00:40 JunOS-GW sshd[37001]: Failed password for kayla from 200.111.82.154 port 33826 ssh2
Sep 1 02:00:41 JunOS-GW inetd[2541]: /usr/sbin/sshd[37001]: exit status 0xff00
Sep 1 02:00:44 JunOS-GW sshd[37003]: Failed password for russ from 200.111.82.154 port 34084 ssh2
Sep 1 02:00:44 JunOS-GW inetd[2541]: /usr/sbin/sshd[37003]: exit status 0xff00
Sep 1 02:00:48 JunOS-GW sshd[37005]: Failed password for white from 200.111.82.154 port 34319 ssh2
Sep 1 02:00:48 JunOS-GW inetd[2541]: /usr/sbin/sshd[37005]: exit status 0xff00
Sep 1 02:00:52 JunOS-GW sshd[37007]: Failed password for danny from 200.111.82.154 port 34538 ssh2
Sep 1 02:00:52 JunOS-GW inetd[2541]: /usr/sbin/sshd[37007]: exit status 0xff00
Sep 1 02:00:55 JunOS-GW sshd[37009]: Failed password for filip from 200.111.82.154 port 34775 ssh2
Sep 1 02:00:56 JunOS-GW inetd[2541]: /usr/sbin/sshd[37009]: exit status 0xff00
Sep 1 02:00:59 JunOS-GW sshd[37011]: Failed password for stephanie from 200.111.82.154 port 35004 ssh2
Sep 1 02:01:00 JunOS-GW inetd[2541]: /usr/sbin/sshd[37011]: exit status 0xff00
Sep 1 02:01:03 JunOS-GW sshd[37013]: Failed password for nora from 200.111.82.154 port 35243 ssh2
Sep 1 02:01:04 JunOS-GW inetd[2541]: /usr/sbin/sshd[37013]: exit status 0xff00
Sep 1 02:01:07 JunOS-GW sshd[37018]: Failed password for bunny from 200.111.82.154 port 35483 ssh2
Sep 1 02:01:07 JunOS-GW inetd[2541]: /usr/sbin/sshd[37018]: exit status 0xff00
Sep 1 02:01:11 JunOS-GW sshd[37020]: Failed password for boss from 200.111.82.154 port 35705 ssh2
Sep 1 02:01:11 JunOS-GW inetd[2541]: /usr/sbin/sshd[37020]: exit status 0xff00
Sep 1 02:01:15 JunOS-GW sshd[37022]: Failed password for center from 200.111.82.154 port 35938 ssh2
Sep 1 02:01:15 JunOS-GW inetd[2541]: /usr/sbin/sshd[37022]: exit status 0xff00
Sep 1 02:01:18 JunOS-GW sshd[37024]: Failed password for danny from 200.111.82.154 port 36179 ssh2
Sep 1 02:01:19 JunOS-GW inetd[2541]: /usr/sbin/sshd[37024]: exit status 0xff00
Sep 1 02:01:22 JunOS-GW sshd[37026]: Failed password for drive from 200.111.82.154 port 36405 ssh2
Sep 1 02:01:23 JunOS-GW inetd[2541]: /usr/sbin/sshd[37026]: exit status 0xff00
Sep 1 02:01:26 JunOS-GW sshd[37028]: Failed password for jukebox from 200.111.82.154 port 36639 ssh2
Sep 1 02:01:27 JunOS-GW inetd[2541]: /usr/sbin/sshd[37028]: exit status 0xff00
Sep 1 02:01:30 JunOS-GW sshd[37030]: Failed password for julie from 200.111.82.154 port 36867 ssh2
Sep 1 02:01:30 JunOS-GW inetd[2541]: /usr/sbin/sshd[37030]: exit status 0xff00
Sep 1 02:01:34 JunOS-GW sshd[37032]: Failed password for kramer from 200.111.82.154 port 37100 ssh2
Sep 1 02:01:34 JunOS-GW inetd[2541]: /usr/sbin/sshd[37032]: exit status 0xff00
Sep 1 02:01:38 JunOS-GW sshd[37034]: Failed password for webster from 200.111.82.154 port 37338 ssh2
Sep 1 02:01:38 JunOS-GW inetd[2541]: /usr/sbin/sshd[37034]: exit status 0xff00
Sep 1 02:01:41 JunOS-GW sshd[37036]: Failed password for cycle from 200.111.82.154 port 37551 ssh2
Sep 1 02:01:42 JunOS-GW inetd[2541]: /usr/sbin/sshd[37036]: exit status 0xff00
Sep 1 02:01:45 JunOS-GW sshd[37038]: Failed password for doctor from 200.111.82.154 port 37799 ssh2
Sep 1 02:01:46 JunOS-GW inetd[2541]: /usr/sbin/sshd[37038]: exit status 0xff00
Sep 1 02:01:49 JunOS-GW sshd[37040]: Failed password for paul from 200.111.82.154 port 38034 ssh2
Sep 1 02:01:49 JunOS-GW inetd[2541]: /usr/sbin/sshd[37040]: exit status 0xff00
Sep 1 02:01:53 JunOS-GW sshd[37042]: Failed password for silver from 200.111.82.154 port 38249 ssh2
Sep 1 02:01:53 JunOS-GW inetd[2541]: /usr/sbin/sshd[37042]: exit status 0xff00
Sep 1 02:01:57 JunOS-GW sshd[37044]: Failed password for bull from 200.111.82.154 port 48277 ssh2
Sep 1 02:01:57 JunOS-GW inetd[2541]: /usr/sbin/sshd[37044]: exit status 0xff00
Sep 1 02:02:01 JunOS-GW sshd[37046]: Failed password for play from 200.111.82.154 port 48527 ssh2
Sep 1 02:02:01 JunOS-GW inetd[2541]: /usr/sbin/sshd[37046]: exit status 0xff00
Sep 1 02:02:04 JunOS-GW sshd[37048]: Failed password for smith from 200.111.82.154 port 48740 ssh2
Sep 1 02:02:05 JunOS-GW inetd[2541]: /usr/sbin/sshd[37048]: exit status 0xff00
Sep 1 02:02:08 JunOS-GW sshd[37050]: Failed password for brian from 200.111.82.154 port 48976 ssh2
Sep 1 02:02:09 JunOS-GW inetd[2541]: /usr/sbin/sshd[37050]: exit status 0xff00
Sep 1 02:02:12 JunOS-GW sshd[37052]: Failed password for spencer from 200.111.82.154 port 49211 ssh2
Sep 1 02:02:13 JunOS-GW inetd[2541]: /usr/sbin/sshd[37052]: exit status 0xff00
Sep 1 02:02:16 JunOS-GW sshd[37054]: Failed password for elly from 200.111.82.154 port 49441 ssh2
Sep 1 02:02:16 JunOS-GW inetd[2541]: /usr/sbin/sshd[37054]: exit status 0xff00
Sep 1 02:02:20 JunOS-GW sshd[37056]: Failed password for hall from 200.111.82.154 port 49670 ssh2
Sep 1 02:02:20 JunOS-GW inetd[2541]: /usr/sbin/sshd[37056]: exit status 0xff00
Sep 1 02:02:23 JunOS-GW sshd[37058]: Failed password for arnold from 200.111.82.154 port 49899 ssh2
Sep 1 02:02:24 JunOS-GW inetd[2541]: /usr/sbin/sshd[37058]: exit status 0xff00
Sep 1 02:02:27 JunOS-GW sshd[37060]: Failed password for j3t from 200.111.82.154 port 50144 ssh2
Sep 1 02:02:28 JunOS-GW inetd[2541]: /usr/sbin/sshd[37060]: exit status 0xff00
Sep 1 02:02:31 JunOS-GW sshd[37062]: Failed password for jet from 200.111.82.154 port 50360 ssh2
Sep 1 02:02:32 JunOS-GW inetd[2541]: /usr/sbin/sshd[37062]: exit status 0xff00
Sep 1 02:02:35 JunOS-GW sshd[37064]: Failed password for bank from 200.111.82.154 port 50588 ssh2
Sep 1 02:02:35 JunOS-GW inetd[2541]: /usr/sbin/sshd[37064]: exit status 0xff00
Sep 1 02:02:39 JunOS-GW sshd[37066]: Failed password for one from 200.111.82.154 port 50831 ssh2
Sep 1 02:02:39 JunOS-GW inetd[2541]: /usr/sbin/sshd[37066]: exit status 0xff00
Sep 1 02:02:43 JunOS-GW sshd[37068]: Failed password for davis from 200.111.82.154 port 51061 ssh2
Sep 1 02:02:43 JunOS-GW inetd[2541]: /usr/sbin/sshd[37068]: exit status 0xff00
Sep 1 02:02:47 JunOS-GW sshd[37070]: Failed password for sharp from 200.111.82.154 port 51296 ssh2
Sep 1 02:02:47 JunOS-GW inetd[2541]: /usr/sbin/sshd[37070]: exit status 0xff00
Sep 1 02:02:50 JunOS-GW sshd[37072]: Failed password for union from 200.111.82.154 port 51518 ssh2
Sep 1 02:02:51 JunOS-GW inetd[2541]: /usr/sbin/sshd[37072]: exit status 0xff00
Sep 1 02:02:54 JunOS-GW sshd[37074]: Failed password for gregory from 200.111.82.154 port 51754 ssh2
Sep 1 02:02:55 JunOS-GW inetd[2541]: /usr/sbin/sshd[37074]: exit status 0xff00
Sep 1 02:02:58 JunOS-GW sshd[37076]: Failed password for jack from 200.111.82.154 port 51988 ssh2
Sep 1 02:02:59 JunOS-GW inetd[2541]: /usr/sbin/sshd[37076]: exit status 0xff00
Sep 1 02:03:02 JunOS-GW sshd[37078]: Failed password for james from 200.111.82.154 port 52225 ssh2
Sep 1 02:03:02 JunOS-GW inetd[2541]: /usr/sbin/sshd[37078]: exit status 0xff00
Sep 1 02:03:06 JunOS-GW sshd[37080]: Failed password for mike from 200.111.82.154 port 52438 ssh2
Sep 1 02:03:06 JunOS-GW inetd[2541]: /usr/sbin/sshd[37080]: exit status 0xff00
Sep 1 02:03:09 JunOS-GW sshd[37082]: Failed password for bash from 200.111.82.154 port 52678 ssh2
Sep 1 02:03:10 JunOS-GW inetd[2541]: /usr/sbin/sshd[37082]: exit status 0xff00
Sep 1 02:03:13 JunOS-GW sshd[37084]: Failed password for leon from 200.111.82.154 port 52902 ssh2
Sep 1 02:03:14 JunOS-GW inetd[2541]: /usr/sbin/sshd[37084]: exit status 0xff00
Sep 1 02:03:17 JunOS-GW sshd[37086]: Failed password for banner from 200.111.82.154 port 53123 ssh2
Sep 1 02:03:18 JunOS-GW inetd[2541]: /usr/sbin/sshd[37086]: exit status 0xff00
Sep 1 02:03:21 JunOS-GW sshd[37088]: Failed password for admin2 from 200.111.82.154 port 53367 ssh2
Sep 1 02:03:21 JunOS-GW inetd[2541]: /usr/sbin/sshd[37088]: exit status 0xff00
Sep 1 02:03:25 JunOS-GW sshd[37090]: Failed password for mich from 200.111.82.154 port 53597 ssh2
Sep 1 02:03:25 JunOS-GW inetd[2541]: /usr/sbin/sshd[37090]: exit status 0xff00
Sep 1 02:03:29 JunOS-GW sshd[37092]: Failed password for denise from 200.111.82.154 port 53829 ssh2
Sep 1 02:03:29 JunOS-GW inetd[2541]: /usr/sbin/sshd[37092]: exit status 0xff00
Sep 1 02:03:33 JunOS-GW sshd[37094]: Failed password for xbox from 200.111.82.154 port 54059 ssh2
Sep 1 02:03:33 JunOS-GW inetd[2541]: /usr/sbin/sshd[37094]: exit status 0xff00
Sep 1 02:03:36 JunOS-GW sshd[37096]: Failed password for pgsql from 200.111.82.154 port 54288 ssh2
Sep 1 02:03:37 JunOS-GW inetd[2541]: /usr/sbin/sshd[37096]: exit status 0xff00
Sep 1 02:03:40 JunOS-GW sshd[37098]: Failed password for julie from 200.111.82.154 port 54508 ssh2
Sep 1 02:03:41 JunOS-GW inetd[2541]: /usr/sbin/sshd[37098]: exit status 0xff00
Sep 1 02:03:44 JunOS-GW sshd[37100]: Failed password for drive from 200.111.82.154 port 54735 ssh2
Sep 1 02:03:44 JunOS-GW inetd[2541]: /usr/sbin/sshd[37100]: exit status 0xff00
Sep 1 02:03:48 JunOS-GW sshd[37102]: Failed password for cycle from 200.111.82.154 port 54984 ssh2
Sep 1 02:03:48 JunOS-GW inetd[2541]: /usr/sbin/sshd[37102]: exit status 0xff00
Sep 1 02:03:52 JunOS-GW sshd[37104]: Failed password for carol from 200.111.82.154 port 55197 ssh2
Sep 1 02:03:52 JunOS-GW inetd[2541]: /usr/sbin/sshd[37104]: exit status 0xff00
Sep 1 02:03:56 JunOS-GW sshd[37106]: Failed password for cesar from 200.111.82.154 port 55447 ssh2
Sep 1 02:03:56 JunOS-GW inetd[2541]: /usr/sbin/sshd[37106]: exit status 0xff00
Sep 1 02:03:59 JunOS-GW sshd[37108]: Failed password for clark from 200.111.82.154 port 55672 ssh2
Sep 1 02:04:00 JunOS-GW inetd[2541]: /usr/sbin/sshd[37108]: exit status 0xff00
Sep 1 02:04:03 JunOS-GW sshd[37110]: Failed password for clinton from 200.111.82.154 port 55893 ssh2
Sep 1 02:04:04 JunOS-GW inetd[2541]: /usr/sbin/sshd[37110]: exit status 0xff00
Sep 1 02:04:07 JunOS-GW sshd[37112]: Failed password for kayla from 200.111.82.154 port 56117 ssh2
Sep 1 02:04:07 JunOS-GW inetd[2541]: /usr/sbin/sshd[37112]: exit status 0xff00
Sep 1 02:04:11 JunOS-GW sshd[37114]: Failed password for russ from 200.111.82.154 port 56359 ssh2
Sep 1 02:04:11 JunOS-GW inetd[2541]: /usr/sbin/sshd[37114]: exit status 0xff00
Sep 1 02:04:15 JunOS-GW sshd[37116]: Failed password for white from 200.111.82.154 port 56579 ssh2
Sep 1 02:04:15 JunOS-GW inetd[2541]: /usr/sbin/sshd[37116]: exit status 0xff00
Sep 1 02:04:18 JunOS-GW sshd[37118]: Failed password for danny from 200.111.82.154 port 56811 ssh2
Sep 1 02:04:19 JunOS-GW inetd[2541]: /usr/sbin/sshd[37118]: exit status 0xff00
Sep 1 02:04:22 JunOS-GW sshd[37120]: Failed password for filip from 200.111.82.154 port 57063 ssh2
Sep 1 02:04:23 JunOS-GW inetd[2541]: /usr/sbin/sshd[37120]: exit status 0xff00
Sep 1 02:04:26 JunOS-GW sshd[37122]: Failed password for stephanie from 200.111.82.154 port 57282 ssh2
Sep 1 02:04:27 JunOS-GW inetd[2541]: /usr/sbin/sshd[37122]: exit status 0xff00
Sep 1 02:04:30 JunOS-GW sshd[37124]: Failed password for wwwdata from 200.111.82.154 port 57504 ssh2
Sep 1 02:04:30 JunOS-GW inetd[2541]: /usr/sbin/sshd[37124]: exit status 0xff00
Sep 1 02:04:34 JunOS-GW sshd[37126]: Failed password for admin from 200.111.82.154 port 57748 ssh2
Sep 1 02:04:34 JunOS-GW inetd[2541]: /usr/sbin/sshd[37126]: exit status 0xff00
Sep 1 02:04:38 JunOS-GW sshd[37128]: Failed password for admin from 200.111.82.154 port 57970 ssh2
Sep 1 02:04:38 JunOS-GW inetd[2541]: /usr/sbin/sshd[37128]: exit status 0xff00
Sep 1 02:04:41 JunOS-GW sshd[37130]: Failed password for admin from 200.111.82.154 port 58202 ssh2
Sep 1 02:04:42 JunOS-GW inetd[2541]: /usr/sbin/sshd[37130]: exit status 0xff00
Sep 1 02:04:45 JunOS-GW sshd[37132]: Failed password for admin from 200.111.82.154 port 58438 ssh2
Sep 1 02:04:46 JunOS-GW inetd[2541]: /usr/sbin/sshd[37132]: exit status 0xff00
Sep 1 02:04:49 JunOS-GW sshd[37134]: Failed password for admin from 200.111.82.154 port 58663 ssh2
Sep 1 02:04:49 JunOS-GW inetd[2541]: /usr/sbin/sshd[37134]: exit status 0xff00
Sep 1 02:04:53 JunOS-GW sshd[37136]: Failed password for admin from 200.111.82.154 port 58907 ssh2
Sep 1 02:04:53 JunOS-GW inetd[2541]: /usr/sbin/sshd[37136]: exit status 0xff00
Sep 1 02:04:57 JunOS-GW sshd[37138]: Failed password for admin from 200.111.82.154 port 59121 ssh2
Sep 1 02:04:57 JunOS-GW inetd[2541]: /usr/sbin/sshd[37138]: exit status 0xff00
Sep 1 02:05:00 JunOS-GW sshd[37140]: Failed password for admin from 200.111.82.154 port 59359 ssh2
Sep 1 02:05:01 JunOS-GW inetd[2541]: /usr/sbin/sshd[37140]: exit status 0xff00
Sep 1 02:05:04 JunOS-GW sshd[37142]: Failed password for admin from 200.111.82.154 port 59606 ssh2
Sep 1 02:05:05 JunOS-GW inetd[2541]: /usr/sbin/sshd[37142]: exit status 0xff00
Sep 1 02:05:08 JunOS-GW sshd[37144]: Failed password for admin from 200.111.82.154 port 59814 ssh2
Sep 1 02:05:09 JunOS-GW inetd[2541]: /usr/sbin/sshd[37144]: exit status 0xff00
Sep 1 02:05:12 JunOS-GW sshd[37146]: Failed password for admin from 200.111.82.154 port 60053 ssh2
Sep 1 02:05:12 JunOS-GW inetd[2541]: /usr/sbin/sshd[37146]: exit status 0xff00
Sep 1 02:05:16 JunOS-GW sshd[37148]: Failed password for admin from 200.111.82.154 port 60282 ssh2
Sep 1 02:05:16 JunOS-GW inetd[2541]: /usr/sbin/sshd[37148]: exit status 0xff00
Sep 1 02:05:20 JunOS-GW sshd[37150]: Failed password for admin from 200.111.82.154 port 60512 ssh2
Sep 1 02:05:20 JunOS-GW inetd[2541]: /usr/sbin/sshd[37150]: exit status 0xff00
Sep 1 02:05:23 JunOS-GW sshd[37152]: Failed password for admin from 200.111.82.154 port 60748 ssh2
Sep 1 02:05:24 JunOS-GW inetd[2541]: /usr/sbin/sshd[37152]: exit status 0xff00
Sep 1 02:05:27 JunOS-GW sshd[37154]: Failed password for admin from 200.111.82.154 port 60982 ssh2
Sep 1 02:05:28 JunOS-GW inetd[2541]: /usr/sbin/sshd[37154]: exit status 0xff00
Sep 1 02:05:33 JunOS-GW sshd[37156]: Failed password for admin from 200.111.82.154 port 32981 ssh2
Sep 1 02:05:34 JunOS-GW inetd[2541]: /usr/sbin/sshd[37156]: exit status 0xff00
Sep 1 02:05:37 JunOS-GW sshd[37158]: Failed password for george from 200.111.82.154 port 33361 ssh2
Sep 1 02:05:38 JunOS-GW inetd[2541]: /usr/sbin/sshd[37158]: exit status 0xff00
Sep 1 02:05:41 JunOS-GW sshd[37160]: Failed password for michael from 200.111.82.154 port 33590 ssh2
Sep 1 02:05:41 JunOS-GW inetd[2541]: /usr/sbin/sshd[37160]: exit status 0xff00
Sep 1 02:05:45 JunOS-GW sshd[37162]: Failed password for matilda from 200.111.82.154 port 33811 ssh2
Sep 1 02:05:45 JunOS-GW inetd[2541]: /usr/sbin/sshd[37162]: exit status 0xff00
Sep 1 02:05:49 JunOS-GW sshd[37164]: Failed password for john from 200.111.82.154 port 34032 ssh2
Sep 1 02:05:49 JunOS-GW inetd[2541]: /usr/sbin/sshd[37164]: exit status 0xff00
Sep 1 02:05:52 JunOS-GW sshd[37166]: Failed password for kevin from 200.111.82.154 port 34274 ssh2
Sep 1 02:05:53 JunOS-GW inetd[2541]: /usr/sbin/sshd[37166]: exit status 0xff00
Sep 1 02:05:56 JunOS-GW sshd[37168]: Failed password for hacker from 200.111.82.154 port 34500 ssh2
Sep 1 02:05:57 JunOS-GW inetd[2541]: /usr/sbin/sshd[37168]: exit status 0xff00
Sep 1 02:06:00 JunOS-GW sshd[37170]: Failed password for daniel from 200.111.82.154 port 34724 ssh2
Sep 1 02:06:00 JunOS-GW inetd[2541]: /usr/sbin/sshd[37170]: exit status 0xff00
Sep 1 02:06:04 JunOS-GW sshd[37172]: Failed password for david from 200.111.82.154 port 34970 ssh2
Sep 1 02:06:04 JunOS-GW inetd[2541]: /usr/sbin/sshd[37172]: exit status 0xff00
Sep 1 02:06:08 JunOS-GW sshd[37174]: Failed password for nathan from 200.111.82.154 port 35195 ssh2
Sep 1 02:06:08 JunOS-GW inetd[2541]: /usr/sbin/sshd[37174]: exit status 0xff00
Sep 1 02:06:11 JunOS-GW sshd[37176]: Failed password for mihai from 200.111.82.154 port 35427 ssh2
Sep 1 02:06:12 JunOS-GW inetd[2541]: /usr/sbin/sshd[37176]: exit status 0xff00
Sep 1 02:06:15 JunOS-GW sshd[37178]: Failed password for internet from 200.111.82.154 port 35659 ssh2
Sep 1 02:06:16 JunOS-GW inetd[2541]: /usr/sbin/sshd[37178]: exit status 0xff00
Sep 1 05:16:48 JunOS-GW sshd[37207]: fatal: Timeout before authentication for 202.53.247.238
Sep 1 05:16:48 JunOS-GW inetd[2541]: /usr/sbin/sshd[37207]: exit status 0xff00

[Notebook] Windows XP Installation Toshiba Satellite M200 SATA Error

ipstories — Fri, 29 Aug 2008 12:01:32 +0000

Windows XP Installation on this pretty sensitive notebook is pretty much complicated.
“Setup did not find any hard disk drives installed on your computer” … will be the famous problem found when starting the installation & Thanks to HowToGeek site & People who inspired this.

It’s SATA will not recognized by Windows XP if the SATA driver doesn’t exist along with CD Installation.

Here the steps (use another PC to create this customize Windows XP Installation CD):

A. SATA Driver
==============
1. Download Toshiba M200 SATA Driver at Here… at HP.Com ? Yes ! 2. Run & Install on any directory you want

B. Embedding & Customizing Process
==================================
1. Download & Install Nlite
2. Insert Windows XP Installation CD
3. Run Nlite & Point the CD Drive once you asked for browse the “Locating the Windows Installation”.
4. Click OK & Define a directory (for sure create a new directory) for the Windows XP soruce file to be copied
5. Click OK & Next, a screen with will appear.
6. Choose [Integrate] Driver & [Create] Bootable ISO
7. Next & Till the screen “Insert” Button appear
8. Click & Choose Single Driver
9. Point to Directory where previous *.inf SATA Driver installed

Next please follow How to Geek Site for complete snapshot & better look.
I’m just suggesting installing your SATA driver first before creating Windows XP CD Installation with embedded SATA Driver..

Thanks to Koh Ery Anggara as well.

a. rahman isnaini r.sutan