Free wan software for linux

WANem is a WAN Emulator, meant to provide real experience of Internet, during development and test on a LAN environment. Typically application developers develop applications on a LAN while the intended purpose for the same could be the client is accessing the application by WAN or even the internet.

WANem allows for the application development team to setup a transparent application gateway which can be made use to simulate WAN characteristics like Network delay, Packet loss, Packet corruption, Disconnections, Packet re-ordering, Jitter, etc.

WANem allows for WAN network characteristic emulation and thus allowing for applications to be tested in a realistic WAN environment before they are moved into production.

WANem is a combined development strategy where it hooks into the Linux kernel for performing network emulations and provides GUI to make it simple to use. Remastering of Knoppix Live CD makes it even more effective as it becomes platform independant.

strongSwan is an OpenSource IPsec implementation for the Linux operating system. strongSwan is based on the discontinued FreeS/WAN project and the X.509 patch which we developped over the last three years.
In order to have a stable IPsec platform to base our future extensions of the X.509 capability on, we decided to lauch the strongSwan project.
Main features:
- runs both on Linux 2.4 (KLIPS) and Linux 2.6 (native IPsec) kernels
- strong 3DES, AES, Serpent, Twofish, or Blowfish encryption
- Authentication based on X.509 certificates or preshared keys
- Powerful IPsec policies based on wildcards or intermediate CAs
- Retrieval and local caching of Certificate Revocation Lists via HTTP or LDAP
- Full support of the Online Certificate Status Protocol (OCSP, RCF 2560).
- Optional storage of RSA private keys on smartcards or USB crypto tokens
- Smartcard access via standardized PKCS #11 interface
- PKCS #11 proxy function offering RSA decryption services via whack
- NAT-Traversal (RFC 3947) and support of Virtual IPs and IKE Mode Config
- CA management (OCSP and CRL URIs, default LDAP server)
- Dead Peer Detection (DPD, RFC 3706)
- Group policies based on X.509 attribute certificates ( RFC 3281)
- Generation of default self-signed certificates during strongSwan setup
Whats New in 2.8.0 Stable Release:
- The implementation of the IKE Mode Config push mode allows interoperability with Cisco VPN gateways.
- By setting "modeconfig=push", strongSwan will wait for the peer to push down a virtual IP address that can be used within an IPsec tunnel.
- The default value of the new keyword is "modeconfig=pull".
- The command "ipsec statusall" now shows "DPD active" for all ISAKMP Security Associations that are under active Dead Peer Detection control.
Whats New in 4.0.7 Development Release:
- Extended authentication (XAUTH) in conjunction with IKE Main Mode authentication (RSA and PSK) is now possible with most VPN clients and gateways (e.g. Cisco, NCP, Shrew, etc.).
Whats New in 2.8.3 Stable Release:
- A bug in the computation of the SHA-512-HMAC function was fixed.
- The SHA-384 hash and HMAC functions were implemented.
- SHA-2 signatures are now supported in X.509 certificates.
- Automatic test vector-based self-tests of all hash functions (MD5, SHA-1, SHA-2) during pluto startup was introduced to increase the reliability of the software.

WANPIPE S-series is a family of intelligent multi-protocol WAN and ADSL adapters that support data transfer rates up to 8Mbps.
All WAN protocols supported by WANPIPE are implemented in firmware and run on the card. An advantage of an intelligent adapter is that it offloads the system CPU and improves stability.
By adding a Sangoma WAN/ADSL component to the Linux kernel, one can create a powerful multi-T1/ADSL router/firewall with proven reliability of Linux. Sangoma S-series cards support an optional on board T1/E1 CSU/DSU that eliminates all external components of a traditional routing solution: i.e. T1/E1 line can be directly connected to the card.
WANPIPE supports the following protocols, ATM, ADSL, Frame Relay, PPP, MULTILINK PPP, CHDLC, X25(API), BitStreaming (API), BiSync(API), and SDLC(API).
Furthermore, WANPIPE supports custom API development such as: Credit card verification, Voice-over IP, Satellite Comm. All device drivers are part of the standard Linux Kernel distribution.
Whats New in 3.1.3 Beta Development Release:
- Drivers can now work with 1, 2, 5, and 10ms chunk sizes.
- Numerous major bugs have been fixed, including issues with echo cancellation, DTMF synchronization, E1/CRC4 mode, and startup.

Nest provides a secure IP VPN cryptographically protected packet tunnel.
Nest is a secure IP VPN tunnel for FreeBSD. It connects two LANs over an insecure WAN.
Nest works on the IP packet level. Its features include packet authentication and integrity checking (with 96-bit SHA1-derived HMAC), packet encryption (with Blowfish and 160-bit key CBC mode), replay protection, adjustable packet queuing, and compression.
The VPN traffic appears on the WAN as a bidirectional stream of IP packets or as a unidirectional ICMP request/response stream. The latter case allows the establishment of VPN tunnels through certain firewalls.
Main features:
- Authentication/Integrity
- Encryption
- Replay protection
- Queueing/Compression
- ICMP stream (new in version 3)
- IP masquerading (new in version 3)
Enhancements:
- A #define to make the program silent was added. A
- bootable FreeBSD floppy containing the software is now also available for download.

IP Bandwidth Watchdog (ipband) is a pcap based IP traffic monitor. It tallies per-subnet traffic and bandwidth usage and starts detailed logging if specified threshold for the specific subnet is exceeded. If traffic has been high for a certain period of time, the report for that subnet is generated which can be appended to a file or e-mailed. When bandwidth usage drops below the threshold, detailed logging for the subnet is stopped and memory is freed.

This utility could be handy in a limited bandwidth WAN environment (frame relay, ISDN etc. circuits) to pinpoint offending traffic source if certain links become saturated to the point where legitimate packets start getting dropped.

It also can be used to monitor internet connection when specifying the range of local ip addresses (to avoid firing reports about non-local networks).

m0n0wall is a project aimed at creating a complete, embedded firewall software package that, when used together with an embedded PC, provides all the important features of commercial firewall boxes (including ease of use) at a fraction of the price (free software).
m0n0wall is based on a bare-bones version of FreeBSD, along with a web server, PHP and a few other utilities. The entire system configuration of m0n0wall is stored in one single XML text file to keep things transparent.
m0n0wall is probably the first UNIX system that has its boot-time configuration done with PHP, rather than the usual shell scripts, and that has the entire system configuration stored in XML format.
Main features:
- web interface (supports SSL)
- serial console interface for recovery
- set LAN IP address
- reset password
- restore factory defaults
- reboot system
- wireless support (access point with PRISM-II/2.5/3 cards, BSS/IBSS with other cards including Cisco)
- captive portal
- 802.1Q VLAN support
- stateful packet filtering
- block/pass rules
- logging
- NAT/PAT (including 1:1)
- DHCP client, PPPoE, PPTP and Telstra BigPond Cable support on the WAN interface
- IPsec VPN tunnels (IKE; with support for hardware crypto cards and mobile clients)
- PPTP VPN (with RADIUS server support)
- static routes
- DHCP server
- caching DNS forwarder
- DynDNS client
- SNMP agent
- traffic shaper
- SVG-based traffic grapher
- firmware upgrade through the web browser
- Wake on LAN client
- configuration backup/restore
- host/network aliases
Enhancements:
- added voucher support to captive portal (mwiget); wireless LAN improvements; allow dashes in alias names; added hidden option to disable auto-generation of PPTP rules on WAN; fixed ATA hard disk spin down feature; ipfilter TCP window scaling bug fix; synced with changes from 1.23 branch; increased mfsroot size to 14 MB (from 13 MB); updated base system to FreeBSD 6.2-RELEASE-p6; updated PHP to 4.4.7, ipsec-tools to 0.6.7, isc-dhcpd to 3.0.5, Dnsmasq to 2.39; added kernel patch for fragment bug in ipfilter; modified kernel patch to handle ipnat+dummynet in ip_input....

SMSLink project implements a client/server gateway to the SMS protocol (short messages on the mobile phones).
It requires the use of dedicated hardware (a serial GSM module).
Both SMS emission and reception are supported, either in text-mode or in PDU-mode.
It also includes an SMS to eMail gateway module.
The server runs under Linux and FreeBSD and supports interactive mode via telnet.
The command-line client already exists for Linux, FreeBSD, Solaris, HP-UX, and Win32.
A basic Web interface is also provided.
Main features:
- The use of TCP/IP sockets for communication between client and server means that the application is network-aware from the start and that deploying it over a WAN (or across the internet) is a piece of cake. Expanding it as well, since writing additional clients for it is possible on any platform supporting sockets. Various ports of the client to Win32 are now available.
- The server process has a command-line interface connected to the socket, making it possible to use it interactively from a telnet session (only line mode telnet supported at the present time - see server/BUGS and server/TODO in the sources directory). This feature is of enormous help when troubleshooting or debugging.
- The command-line interface is backed by a parser written in lex and yacc (flex/bison, actually), which makes the language relatively easy to extend.
- The server was built from the start with the idea of multiple GSM modules in mind. Adding a line to two configuration files (and connecting the hardware, of course) is all there is to using two modules instead of one. The number of modules supported by the server is limited by the hardware only.
- The choice to use specific hardware (the serial GSM module), although limiting the general-purpose use of this application, allows for some very usefull features, the most prominant one being the ability to receive SMS messages as well as send them. This feature is now implemented (as of version 0.41b). Once downloaded from the GSM module, those messages can either be stored in an inbox file or fed through an external program or script, or both.
- By sitting straight on the GSM network, the use of the GSM module offers an advantage that far outweighs its cost : provider independance. The ability to send and receive SMS might be limited in some way or another by the level of your subscription, but all providers should offer a standard way of doing it. No "provider-specific driver" is required in this case. Whats more, all SMS routing aspects are being taken care of by the GSM network itself. Caution is advisable when choosing the provider though, as some of them might place some restrictions on routing to and/or from outside networks (e.g. Mobistar and Itineris*) or lack the implementation of some advanced features of the SMS protocol such as "point-to-point SMS" or "SMS-back" (e.g. Proximus through the UCP interface*).
- As of version 0.48b, initial support for PDU mode and the creation of a "driver-like" capability table for the GSM modules means that most module brands on the market could be supported with little effort. This "driver" approach also garanties that youll be able to mix and match different brands and models of modules on the same server with no problem. Support for PDU mode also opens up a new batch of options, like setting the validity period for a message, potential support for non-standard alphabet, binary content delivery to the mobile phone (logos, tunes, etc. ?) and more.
- A full-fledged access control mechanism allows you to specify precisely which client machine or subnet should be allowed to connect and which shouldnt. The access control is IP-based (as opposed to user-based) and defaults to "deny" for increased security. When the situation doesnt require any access control, the whole thing can be easily disabled by the administrator.

libpicinfo is a library to read image information.
libpicinfo is a C++ library for reading auxiliary information from images. it currently supports TIFF, JPEG and Canon RAW files (CR2).
Main features:
- intuitive C++ usage
- supports EXIF 2.2 specification
- supports TIFF files
- supports JPEG files (with/without JFIF header)
- supports RAW formats of digital cameras (currently Canon CR2 only)
- no library dependency other than C++ standard library
- fast startup time
- fast lookup of tags
Installation:
Under *nix(-like) environments, the standard autotools method works:
./configure
make
make install
The name of library will be libpicinfo. It can be link with -lpicinfo in the gcc command line.
If you are a autotools wizard and thinks my usage of autotools sucks, you are more than welcomed to submit a patch.
Enhancements:
- Fixed compilation in MSVC 7.1
- Fixed Rational constructor dominator=1 bug.