Free 2.0 usb port software for linux

PIC USB Framework is a USB application framework dedicated to Linux (on the host side) and to the PIC 18F4550 family of microcontrollers (on the device side).
PUF includes: a bootloader that can flash the PIC application through the USB, a PIC demo and its corresponding application on the host side, and docker, the host-side flash programming utility.
The PUF also contains gputils and sdcc as cross-building tools, and odyssey 0.4vasco as a parallel port PIC programmer.
Enhancements:
- sdcc optimization flags are now switched on by default.
- A component library (including a console mechanism and a small real time scheduler) has been added to help building user applications.
- Tools have been upgraded to automake 1.9.6, autoconf 2.59d, sdcc snapshot 4482, odyssey 0.5, and gputils 0.13.4.
- The applications size has been optimized.

C-Dogs SDL is a port of the old DOS arcade game C-Dogs to modern operating systems utilising the SDL Media Libraries. In theory C-Dogs SDL should be able to run on Windows, MacOS X, BeOS and the other systems supported by SDL.

Genererally, the more UNIX like a system is, the greater the chance of C-Dogs working (MacOS X and BeOS people, I mean you guys).

C-Dogs SDL was ported to SDL by Jeremy Chin and Lucas Martin-King, using Gentoo Linux as their development environment.

C-Dogs is an arcade shoot-em-up which lets players work alone and co-operativly during missions, and against each other in the "dogfight" deathmatch mode. The DOS version of C-Dogs came with several built in missions and dogfight maps, this version is no exception.

The author of the DOS version of C-Dogs was Ronny Wester. See the "official" homepage for more details. We would like to thank him for releasing the C-Dogs sources to the public.

tcpproxy project is a proxy (or tunnel or redirector) for TCP/IP protocols. In standalone mode it waits for incoming connections forwarding them to another machine or starting a local server program.
Several programs with this function or something similiar are around. However, tcpproxys design goal was to let it operate on some kind of firewall.
Main features:
- Extensive logging to syslog,
- Interface based configuration,
- can bind to a particular interface on a multi-homed host,
- sets environment variables before calling a local server program,
- support for external access control programs,
- can be started from inetd or run in standalone mode.
tcpproxy was created with a transparent TCP proxy in mind. When its used to start local server programs (e.g. an FTP server) it can however also work as "port multiplexer" since it requires different configurations for different interfaces (there are no defaults).
Interface based configuration
tcpproxys services are always bound to a certain interface. Suppose you have a multi-homed host (e.g. a firewall) with the IP numbers 192.168.0.1 (part of your LAN) and 10.11.12.13 (connected to the Internet). The configuration
port 119
interface 192.168.0.1
server news.provider.com
forwards then any connection made to your local interface on the NNTP port to the machine news.provider.com. The providers news server appears now to run on your firewall. Furthermore, if you for each port only a single interface where you want to have tcpproxys service, tcpproxy will not even bind to the others. For the example above this means that someone trying to connect to your external interface would only see a closed port.
Now suppose you want to use a second NNTP server from your LAN. You would first configure a second IP number on your internal interface, e.g. 192.168.0.2 and then reconfigure tcpproxy:
port 119
interface 192.168.0.1
server news.provider.com
interface 192.168.0.2
server news.freshmeat.com
Depending on the incoming interface of a client request the connection is forwarded to one of the servers.
In this case the firewalls external interface is opened on port 119 and a port scan would show that theres some kind of service. If however someone connects to the outer interface the connection is immediatly dropped, simply because tcpproxy isnt configured to handle request on the interface 10.11.12.13 and tcpproxy doesnt accept service defaults.
If you like you can extend this configuration to
port 119
interface 192.168.0.1
server news.provider.com
interface 192.168.0.2
server news.freshmeat.com
interface 10.11.12.13
exec /bin/date
for the scanners amusement. But you might also want to write a message to your systems syslog.
Access control
tcpproxy implements access control by calling external, user provided, script, the so called "access control programs" (or in short: acps). I implemented them because I wanted to be able to deny service usage based on anything I like, not just on the clients IP number or its name.

Bash Port Knocking is a set of scripts that use standard Linux tools to acheive a port knocking system. A Web page is used to open ports, and an email is sent every time the port knocking sequence is successfully made.
Main features:
- Uses custom scripts to begin firewall and ipmasquerade for multiple connections. This can be used as a gateway for ethernet provided Internet Connectivity in addition to supplying port knocking services.
- This script creates a web page that can be used for port knocking. This page can be used locally if the browser is using a public/anonymous proxy.
- This scripts emails the above created browser page to a specified email recipient each time the port knock sequence is successfully acheived.
- This script logs successful port knocks but denies knocks that hit a port designed in the initial scripts. This allows the script to be closed automatically if someone is hitting your computer repeatedly trying to automatically open the ports and allows you to close the ports if youve completed a log in or other desired action.
- In its current state it has run successfully for quite some time and been tested repeatedly with both anonymous proxy and remotely by the author for opening ssh.
- It allows the user to control the depth of the logs searched to function in a very low usage enviornment or a very high use enviornment as desired.
- It sorts the knocks by knocking address to prevent possible denial of service.

Catux-USB is a distribution created by CaTuX, an association of GNU/Linuxs users from the central area of Catalonia.

This distribution is not just one more, but it has a distinguishing feature: it can be executed from any Pendrive (or any USB storage device, even the low capacity ones.

Once it has been executed and the hardware detected, you will have a totally normal distribution, based on Debian through Knoppix and ready to do all the apt-get you want.

USB Pen Drive Linux is portable Linux compilation that is based purely on Debian Linux. The project can be installed to a portable hard drive, USB flash pen drive or even an ipod or other portable device.

USB Linux installation enables you to install a portable Linux operating system on a flash drive no larger than your thumb. This portable Linux version can then be run from any computer that can boot from a flash device.

This process allows you to bring your operating system, desktop, applications, files, e-mail, personal settings, favorites and more with you. It’s like having your own personal operating system you can carry in your pocket. On this site, we provide many simplified portable Linux flash drive tutorials.

hping is a command-line oriented TCP/IP packet assembler/analyzer. The interface is inspired to the ping(8) unix command, but hping isnt only able to send ICMP echo requests.
It supports TCP, UDP, ICMP and RAW-IP protocols, has a traceroute mode, the ability to send files between a covered channel, and many other features.
Main features:
- Firewall testing
- Advanced port scanning
- Network testing, using different protocols, TOS, fragmentation
- Manual path MTU discovery
- Advanced traceroute, under all the supported protocols
- Remote OS fingerprinting
- Remote uptime guessing
- TCP/IP stacks auditing
- hping can also be useful to students that are learning TCP/IP.
Enhancements:
- Fixed a problem with the checksum code. Some packet was generated with the wrong checksum! Please upgrade to rc3 ASAP.
- Scan mode. You can use hping as a low-level automated TCP port scanner. An example of output follows

NAT and blocking all but Port 22 is a simple iptables firewall script.

Sample:

# Internal and External Devices
dev_world=ppp0
dev_int=eth0

# Firewall IP
addr_int=192.168.1.1

# Internal Net
net_int=192.168.1.0/24

###################################################
# Load Modules
insmod ip_tables
insmod ip_conntrack
insmod ip_conntrack_ftp
insmod ipt_state
insmod iptable_nat
insmod ipt_MASQUERADE

###################################################
# Delete all Rules in Filtertable
iptables -F

###################################################
# Define new chains
iptables -N BLOCK
iptables -N EXT-INT
iptables -N INT-EXT
iptables -N ICMP-DENY
iptables -N INT-IF
iptables -N EXT-IF

###################################################

iptables -A BLOCK -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A BLOCK -m state --state NEW -i ! $dev_world -j ACCEPT
iptables -A BLOCK -j DROP

iptables -A INPUT -j BLOCK
iptables -A FORWARD -j BLOCK

###################################################
# Point to chains
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -i $dev_int -s $net_int -j INT-IF
iptables -A INPUT -d ! $addr_int -i $dev_world -s ! $net_int -j EXT-IF
iptables -A INPUT -j DROP

iptables -A FORWARD -d ! $net_int -i $dev_world -s $net_int -j INT-EXT
iptables -A FORWARD -d $net_int -i $dev_int -s ! $net_int -j EXT-INT
iptables -A FORWARD -j DROP

iptables -A OUTPUT -j ACCEPT

###################################################
# Chain Rules
iptables -A EXT-INT -j DROP

iptables -A EXT-IF -i ! $dev_world -j DROP
iptables -A EXT-IF -p tcp --dport 22 -j ACCEPT
iptables -A EXT-IF -p tcp --dport 5901 -j ACCEPT
iptables -A EXT-IF -p tcp --dport 1024: -j ACCEPT
iptables -A EXT-IF -p udp --dport 1024: -j ACCEPT
iptables -A EXT-IF -j DROP

iptables -A INT-IF -j ACCEPT

###################################################
# NAT Rules
# Standard Routing
iptables -A POSTROUTING -t nat -o $dev_world -j MASQUERADE -s $net_int

# Port Forwarding
#iptables -A PREROUTING -t nat -p tcp -d 192.168.1.1 --dport 5901 --to 192.168.1.2:5901 -j DNAT

##################################################
# Enable IP-Forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward)