http://www.wireshark.org

About Wireshark

Wireshark is the world's foremost network protocol analyzer, and is the de facto (and often de jure) standard across many industries and educational institutions.

Wireshark development thrives thanks to the contributions of networking experts across the globe. It is the continuation of a project that started in 1998.

Features

Wireshark has a rich feature set which includes the following:

• Deep inspection of hundreds of protocols, with more being added all the time
• Live capture and offline analysis
• Standard three-pane packet browser
• Multi-platform: Runs on Windows, Linux, OS X, Solaris, FreeBSD, NetBSD, and many others
• Captured network data can be browsed via a GUI, or via the TTY-mode TShark utility
• The most powerful display filters in the industry
• Rich VoIP analysis
• Read/write many different capture file formats: tcpdump (libpcap), Catapult DCT2000, Cisco Secure IDS iplog, Microsoft Network Monitor, Network General Sniffer® (compressed and uncompressed), Sniffer® Pro, and NetXray®, Network Instruments Observer, Novell LANalyzer, RADCOM WAN/LAN Analyzer, Shomiti/Finisar Surveyor, Tektronix K12xx, Visual Networks Visual UpTime, WildPackets EtherPeek/TokenPeek/AiroPeek, and many others
• Capture files compressed with gzip can be decompressed on the fly
• Live data can be read from Ethernet, IEEE 802.11, PPP/HDLC, ATM, Bluetooth, USB, Token Ring, Frame Relay, FDDI, and others (depending on your platfrom)
• Decryption support for many protocols, including IPsec, ISAKMP, Kerberos, SNMPv3, SSL/TLS, WEP, and WPA/WPA2
• Coloring rules can be applied to the packet list for quick, intuitive analysis
• Output can be exported to XML, PostScript®, CSV, or plain text

debian etch에 기본적으로 binutils2.17이 깔린데
그런데 이 버전에서 gcc-3.2.3을 이용해 systemc-2.1.v1을 컴파일 하고
컴파일 된 라이브러리를 이용해 systemc 어플리케이션을 컴파일 할 경우
"defined in discarded section" 블라블라 에러 메시지를 만날 수 있는데
이 문제는 binutils의 버전을 2.15로 낮추면 해결할 수 있다ㅠ

/etc/network/interfaces 를 다음과 같이 수정

iface eth0 inet static
address 192.168.0.111
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
hwaddress ether xx:xx:xx:xx:xx:xx
dns-nameservers 147.46.80.1

invalid-file

http://www.handcraftedsoftware.org/

FreeProxy Internet Suite V4.00 now available

FreeProxy Internet Suite V4.00 now available FreeProxy V4.00 has been renamed to the FreeProxy Internet Suite with the addition of full featured SMTP and POP server functionality. In addition to the current PROXY functions of HTTP, Socks etc, and in addition to the current Web server, SMTP and POP has been added. SMTP and POP will enable you to set up your own inbound and outbound mail system with local mail retrieval. Version 4.00 is currently available as an Alpha version as it has a lot of new functionality. Existing functionality will continue to exist. So potentially you can launch FIS to run a HTTP proxy, a Web Server, a POP server, a SMTP server (and others) all at the same time. I have tested the following FREE portals with FIS V4.00. Mambo, phpBB, Joomla and Drupal. All work perfectly with the web server and ISAPI plugin. There is now a howto in the KB explaining how to set up your own portal based on FIS. So FIS is a complete internet tool with both a good range of proxies and internet services.

Source: xxx.xxx.xxx.xxx:80 -- forwarded to -> 192.168.0.2:80

You can chhose any port on xxx.xxx.xxx.xxx it need not match the port we are forwarding to.

Source: xxx.xxx.xxx.xxx:8888 -- forwarded to -> 192.168.0.2:80

/sbin/iptables -t nat -A PREROUTING -p tcp -i eth0 -d xxx.xxx.xxx.xxx
--dport 8888 -j DNAT --to 192.168.0.2:80
/sbin/iptables -A FORWARD -p tcp -i eth0 -d 192.168.0.2 --dport 80 -j ACCEPT

PORT FORWARDING - with IPTABLES while using BASTILLE firewall Background on network setup I have my home network setup as described here. So my linux gateway server is the only one visible to the internet, while all other machines are in an internal subnet with DHCP assigned IP's not visible to the outside internet, but can access the outside net using Iptables based Network Address Translation (NAT). Why you need portforwarding So in this setup if I want to run a public service like httpd, not on the gateway server ( where it is visible to outside ) but on an internal machine ( which is not visible outside ) how do I make it availble to the outside internet. To make the above scenario of exposing and internal machine's service to outside we need to use port forwarding on the gateway server. Which is assigning a port on the gateway to accept all connections and forward it to the internal machines port where the service is listening to. Let xxx.xxx.xxx.xxx be the IP address of the gateway server connected to the cable modem and 192.168.0.2 , the IP address of the internal machine. And say we want to run a web server ( httpd ) on 192,168.0.2 on port 80 which should be avaialble to the outside internet. We can forward the port 80 on xxx.xxx.xxx.xxx to port 80 of 192.168.0.2 Source: xxx.xxx.xxx.xxx:80 -- forwarded to -> 192.168.0.2:80 You can chhose any port on xxx.xxx.xxx.xxx it need not match the port we are forwarding to. Source: xxx.xxx.xxx.xxx:8888 -- forwarded to -> 192.168.0.2:80 Port Forwarding using Iptables Since I have been using 2.4 kernel, I use iptables for firewall and NAT. So these are the Iptable rules required for port forwarding xxx.xxx.xxx.xxx:8888 to 192.168.0.2:80 . /sbin/iptables -t nat -A PREROUTING -p tcp -i eth0 -d xxx.xxx.xxx.xxx --dport 8888 -j DNAT --to 192.168.0.2:80 /sbin/iptables -A FORWARD -p tcp -i eth0 -d 192.168.0.2 --dport 80 -j ACCEPT How to add custom rules to Bastille firewall Since I trust Bastille firwall script to generate the correct iptable scripts for my server, I wanted to keep those scripts but add these custom port forwarding rules to supplement/extend it. But the version of Bastille on my machine ( 1.2.0 ) does not support port forwarding, and does not had a way of adding custom scripts to it. Posting the question to Bastille mailing list generated these prompt responses from Peter Watkins, core developer of Bastille. ( See the complete thread ) Following Peter's advice I upgraded Bastille to the latest version, without any problem. The new version regenerated all the scripts with my old rules intact. And with the new Bastill in place and working fine doing all the firewall filteringa nd NAT. I made the following changes to add a supplemental script, portforward.sh ( get the script ) for my custom port forwarding rules. Created the directories for supplemetal script. ( as explained in the comments at portforward.sh ) /etc/Bastille/firewall.d/pre-chain-split.d/ Created portforward.sh with working portforwarding rules, following the sample script from Peter. [ Please note: The ipchains rules in portforward.sh are untested. I have left it there from Peter's sample script for completeness. ] In portforward.sh all you have to do is specify the portforwarding source and destination IP addresses and ports with the ethernet interface name ( "eth0" if you have only one interface ) and the protocol type ( "tcp" in this case ). IP_FORWARDS="eth0-xxx.xxx.xxx.xxx-8888-tcp-192.168.0.2-80" Also you can have multiple port forwaring specified like: IP_FORWARDS="eth0-xxx.xxx.xxx.xxx-8888-tcp-192.168.0.2-80 eth0-xxx.xxx.xxx.xxx-2222-tcp-192.168.0.2-22" This will be parsed and stored into varibles down the script and used in the following Iptable calls to generate the rules. [ NOTE: The rules need to be on a single continuous line, I have broken it down to two lines for readability ] ${IPTABLES} -t nat -A PREROUTING -p $fw_inproto -i $fw_iface -d $fw_inaddr --dport $fw_inport -j DNAT --to $fw_outaddr:$fw_outport ${IPTABLES} -A FORWARD -p $fw_inproto -i $fw_iface -d $fw_outaddr --dport $fw_outport -j ACCEPT Which will translate to. /sbin/iptables -t nat -A PREROUTING -p tcp -i eth0 -d xxx.xxx.xxx.xxx --dport 8888 -j DNAT --to 192.168.0.2:80 /sbin/iptables -A FORWARD -p tcp -i eth0 -d 192.168.0.2 --dport 80 -j ACCEPT Now we can restart Bastille scripts to make this rules effective. #/etc/rc.d/init.d/bastille-firewall start Verify the rules by listing them. # iptables -t nat -L Chain PREROUTING (policy ACCEPT) target prot opt source destination DNAT tcp -- anywhere xxx.xxx.xxx.xxxtcp dpt:ddi-tcp-1 to:192.168.0.2:80 Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE all -- 192.168.0.0/16 anywhere MASQUERADE all -- 192.168.0.0/16 anywhere MASQUERADE all -- 192.168.0.0/16 anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination # [ where "ddi-tcp-1", I assume corresponds to port 8888 ] Verify the port forwaring works by connecting to the port from a machine outside the network. Notes on this setup The above rules work fine when you access from outside, but if you try to access the same port xxx.xxx.xxx.xxx:8888 from an internal machine, it will not work. But from the internal network you dont need the forwarding, since you can directly access the machine 192.168.0.2:80.

HACKORAMA SELECT PAGE STYLE 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 WEBLOG CODE ART PHOTOS POEMS DESIGN KISHAN DEEPA ABOUT CONTACT MALAYALAM RECIPES PC GAMES RESUME PATENTS PAPERS RSS/XML GREETINGS iPOD