To share what I've learned !

cisco if the interface type is point to point we don't need to assign ip address related to RFC 1812 2.2.7 section : Related to this if the interface type is P2P we can assign same ip address to two interfaces. Serial1/0 192.168.1.1 YES manual up up Serial1/1 192.168.1.1 YES manual up up Ok if i ping 192.168.1.2 where it will go ? lets explore it .. Basic diagram R2 (s1/0)--<(s1/1) R1 (s1/0)>--(s1/0) R3 -- LO 192.168.6.1/32 R1#show ip route 192.168.1.2 Routing entry for 192.168.1.0/30 Known via "connected", distance 0, metric 0 (connected, via interface) Routing Descriptor Blocks: * directly connected, via Serial1/0 Route metric is 0, traffic share count is 1 directly connected, via Serial1/1 Route metric is 0, traffic share count is 1 so basically load sharing :) further more , R1#show ip cef 192.168.6.1 192.168.6.1/32 nexthop 192.168.1.2 Serial1/0 nexthop 1

This vulnerability basically WebDav can be access like ftp server if you know the username & Password. since Xampp places the default username & password the user doesn't restrict the access to xampp directory after the xampp installtion attackers can places their files & execute remotely. they can use your PC to DDoS their targets. Quite a strange my machine generating 80Mbps traffic towards one of the host. as usual i searched through process explore (sysinternal ) for any unwanted process + tcp connection, Nothing suspicious.But Anti-Virus logs points out http.exe trying to access IRC ports http.exe is xammp apache server process. 1/21/2011 10:02:23 AM Blocked by port blocking rule X:\xampplite\apache\bin\httpd.exe Anti-virus Standard Protection:Prevent IRC communication 173.192.66.130:6666 1/21/2011 10:35:45 AM Blocked by port blocking rule X:\xampplite\apache\bin\httpd.exe Anti-virus Standard Protection:Prevent IRC communication 199.27.134.100:6668 1/21/2011 10