routers woodworking
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 249
Diet-Router 0.3
Diet-Router provides a singe floppy DSL router. more>>
Diet-Router provides a singe floppy DSL router.
Diet-Router is a Linux router that is small enough to fit on a single floppy disk. It focuses more on security than on functionality.
Diet-Router is a Linux router built with the dietlibc. It is small enough to fit on a single floppy disk. You may think that there are several other Linux routers, which come with more features and you are right. I build this router package more with the view on security than of functionality. So this project differs a lot from most other router or mini-Linux projects.
Main features:
- I use a 2.4.x kernel to have the great features of net-filter.
- I patch some net-filter extensions to have even more filter functions.
- I harden the kernel with the grsecurity kernel patch.
- Kernel modules are disabled.
- By default root login is disabled - even on the console.
How does it work:
First of all, all programs are linked statically. This is the main idea of this system. No libraries are needed. It uses busybox and tinylogin, two typical multi-call-binaries for small systems. The iptables, iptables-restore and iptables-save commands have been made a multi-call binary by me. The pppd and pppoe programs have only been patched to compile with the dietlibc. The minit and od_syslog are really small programs, from people with much more knowledge of programming than me. So, special thanks to Felix von Leitner, Olaf Drefs and all the dietlibc/libowfat programmers.
Enhancements:
- Updated dietlibc, libowfat, dropbear, ppp, kernel and grsecurity to recent
- versions.
- Added new packages dhcp server (udhcpd) and vi (e3).
- The build system has been completely rewritten and documented.
- It supports multiple downloads, a simple interface for package building/setup and target file descriptions including file owner and permissions.
- Some simple checks for build requirements are implementet.
- The setup is now able to configure mutiple network interfaces and also mproxy, udhcpd and dnscache can be configured for eachnetwork interface.
- All packages have at least two internet sources.
- Support for disc based target systems has been added.
<<lessDiet-Router is a Linux router that is small enough to fit on a single floppy disk. It focuses more on security than on functionality.
Diet-Router is a Linux router built with the dietlibc. It is small enough to fit on a single floppy disk. You may think that there are several other Linux routers, which come with more features and you are right. I build this router package more with the view on security than of functionality. So this project differs a lot from most other router or mini-Linux projects.
Main features:
- I use a 2.4.x kernel to have the great features of net-filter.
- I patch some net-filter extensions to have even more filter functions.
- I harden the kernel with the grsecurity kernel patch.
- Kernel modules are disabled.
- By default root login is disabled - even on the console.
How does it work:
First of all, all programs are linked statically. This is the main idea of this system. No libraries are needed. It uses busybox and tinylogin, two typical multi-call-binaries for small systems. The iptables, iptables-restore and iptables-save commands have been made a multi-call binary by me. The pppd and pppoe programs have only been patched to compile with the dietlibc. The minit and od_syslog are really small programs, from people with much more knowledge of programming than me. So, special thanks to Felix von Leitner, Olaf Drefs and all the dietlibc/libowfat programmers.
Enhancements:
- Updated dietlibc, libowfat, dropbear, ppp, kernel and grsecurity to recent
- versions.
- Added new packages dhcp server (udhcpd) and vi (e3).
- The build system has been completely rewritten and documented.
- It supports multiple downloads, a simple interface for package building/setup and target file descriptions including file owner and permissions.
- Some simple checks for build requirements are implementet.
- The setup is now able to configure mutiple network interfaces and also mproxy, udhcpd and dnscache can be configured for eachnetwork interface.
- All packages have at least two internet sources.
- Support for disc based target systems has been added.
Download (0.12MB)
Added: 2007-03-02 License: GPL (GNU General Public License) Price:
973 downloads
SMCRoute 0.92
SMCRoute is a command line tool to manipulate the multicast routes of the Linux kernel. more>>
SMCRoute is a command line tool to manipulate the multicast routes of the Linux kernel. It can be used as an alternative to dynamic multicast routers like mrouted in situations where static multicast routes should be maintained and/or IGMP doesnt exist properly implemented
Enhancements:
- fixed the mroute: pending queue full, dropping entries error
- Smcroute 0.90 didnt care about the IGMP messages delivered to the UDP socket that establish the MC-Router API. After some time the queue for the sockets filled up and the pending queue full message was send from the kernel. To my knowledge this didnt affect smcroute or the operating system.
- version 0.92 reads the ICMP messages now from the UDP socket and logs them to syslog with daemon/debug
- smcroute does no further processing of this messages
- increased the number of supported interfaces The 16 interface limit of version 0.90 (interfaces as listed with ifconfig) was to small, especially when alias interfaces where defined.
- up to 40 interfaces are no recognized by smcroute - this does not change the number of virtual interfaces supported by the kernel (32)
- not all interfaces recognized by smcroute (40) results in a virtual interface of the kernel (32)
<<lessEnhancements:
- fixed the mroute: pending queue full, dropping entries error
- Smcroute 0.90 didnt care about the IGMP messages delivered to the UDP socket that establish the MC-Router API. After some time the queue for the sockets filled up and the pending queue full message was send from the kernel. To my knowledge this didnt affect smcroute or the operating system.
- version 0.92 reads the ICMP messages now from the UDP socket and logs them to syslog with daemon/debug
- smcroute does no further processing of this messages
- increased the number of supported interfaces The 16 interface limit of version 0.90 (interfaces as listed with ifconfig) was to small, especially when alias interfaces where defined.
- up to 40 interfaces are no recognized by smcroute - this does not change the number of virtual interfaces supported by the kernel (32)
- not all interfaces recognized by smcroute (40) results in a virtual interface of the kernel (32)
Download (0.039MB)
Added: 2006-07-12 License: GPL (GNU General Public License) Price:
1202 downloads
Cisco Monitoring Tool 0.3
Cimon is Perl program wich monitors the load (memory and CPU) on Cisco routers using SNMP. more>>
Cimon is Perl program wich monitors the load (memory and CPU) on Cisco routers using SNMP, and generates graphics with statistics using rrdtool. Its good for information about your routers health.
It monitors and displays the cpu 5 minutes utilization in percents and free+used Processor memory. The I/O memory(usualy 2 MB) or Fast on high end routers is being monitored too, but there isnt graphic for it. Cimon is good source for information about your routers health. From version 0.2 cimon can do ip accounting using the cisco ip accounting feature.
The logfiles that it generates as the rrd files needed for the graphics are fully compatible with those produced by sasacct (SASs accounting statistics). So you can use its cgi interface also its posibility to generate graphics on demand or on a user defined interval (via crontab and -g option).
<<lessIt monitors and displays the cpu 5 minutes utilization in percents and free+used Processor memory. The I/O memory(usualy 2 MB) or Fast on high end routers is being monitored too, but there isnt graphic for it. Cimon is good source for information about your routers health. From version 0.2 cimon can do ip accounting using the cisco ip accounting feature.
The logfiles that it generates as the rrd files needed for the graphics are fully compatible with those produced by sasacct (SASs accounting statistics). So you can use its cgi interface also its posibility to generate graphics on demand or on a user defined interval (via crontab and -g option).
Download (0.007MB)
Added: 2006-06-29 License: BSD License Price:
1227 downloads
Net::BGP::Router 0.04
Net::BGP::Router is a BGP Router based on Net::BGP. more>>
Net::BGP::Router is a BGP Router based on Net::BGP.
SYNOPSIS
use Net::BGP::Router;
# Constructor
$router = new Net::BGP::Router(
Name => My very own router!,
Policy => new Net::BGP::Policy
);
# Accessor Methods
$router->add_peer($peer,both,$acl);
$router->remove_peer($peer,both);
$router->set_policy($policy);
$router->set_policy($peer,in,$acl);
__top
This module implement a BGP router. It uses Net::BGP objects for the BGP sessions and a Net::BGP::RIB object to store the routes. Policy are handled using a Net::BGP::Policy object.
<<lessSYNOPSIS
use Net::BGP::Router;
# Constructor
$router = new Net::BGP::Router(
Name => My very own router!,
Policy => new Net::BGP::Policy
);
# Accessor Methods
$router->add_peer($peer,both,$acl);
$router->remove_peer($peer,both);
$router->set_policy($policy);
$router->set_policy($peer,in,$acl);
__top
This module implement a BGP router. It uses Net::BGP objects for the BGP sessions and a Net::BGP::RIB object to store the routes. Policy are handled using a Net::BGP::Policy object.
Download (0.010MB)
Added: 2006-07-27 License: Perl Artistic License Price:
1189 downloads
IP accounter 1.01
IP accounter application measures and graphs traffic for IPv4 and IPv6 netfilter-based routers. more>>
IP accounter application measures and graphs traffic for IPv4 and IPv6 netfilter-based routers. Input data is accounted using several abstraction layers (routers, hosts, flows), and IPv6 traffic accounting may be mixed with IPv4.
Enhancements:
- The WEB frontend is still unavailable. There were some minor dificulties running ipaccounter. Still the main issue is when mysql server crashes. The traffic info is then lost until someone fixes it. Therefore it is advised to use some net watching software like Nagios. For further feature enchancements see the ChangeLog. 2006-09-02 by Ondra Ipaccounter-1.0 was released. Only WEB frontend is unavailable at the moment. The accounter is run on one machine. Namely maximus.spi-net.org. There were no fault ancountered so far, but its running only for one week.
<<lessEnhancements:
- The WEB frontend is still unavailable. There were some minor dificulties running ipaccounter. Still the main issue is when mysql server crashes. The traffic info is then lost until someone fixes it. Therefore it is advised to use some net watching software like Nagios. For further feature enchancements see the ChangeLog. 2006-09-02 by Ondra Ipaccounter-1.0 was released. Only WEB frontend is unavailable at the moment. The accounter is run on one machine. Namely maximus.spi-net.org. There were no fault ancountered so far, but its running only for one week.
Download (0.13MB)
Added: 2007-08-10 License: GPL (GNU General Public License) Price:
806 downloads
Cutter 1.03
Cutter is an TCP/IP Connection cutting on Linux Firewalls and Routers. more>>
Cutter is an TCP/IP Connection cutting on Linux Firewalls and Routers.
Cutter is an open source program that uses the FIN-ACK-RST packet technique described above to abort TCP/IP connections routed over the firewall or router on which it is run. It can be called using one of the following four syntaxes.
cutter ip-address
Example: "cutter 10.10.0.45"
Cuts all connections passing through the firewall between any ports on the specified ip-address (either a "private" or "public" address) and any other hosts. This can be used to close down all incoming connections to a particular server, all outgoing connections from a particular client or all outgoing connections to a server.
cutter ip-address port
Example: "cutter 200.1.2.3 80"
Cuts all connections to or from the specified ip-address/port pair. This allows the user to be a little more specific than the previous example and allows targetting of specific services on specific hosts.
cutter ip-address-1 port-1 ip-address-2
Example "cutter 200.1.2.3 22 10.10.0.45"
Cuts all connections between ip-address-2 and ip-address-1/port-1. This allows the user to cut connections between a specified "client" and a particular service on a specified host. Our example closes host 10.10.0.45s SSH connection to server 200.1.2.3.
cutter ip-address-1 port-1 ip-address-2 port-2
Example: "cutter 200.1.2.3 22 10.10.0.45 32451"
Cuts the specific connection between the two ip/port number pairs given.
IMPORTANT WARNING
Cutter has been designed for use as a administrators tool for Linux firewalls. Its use (as is, or modified) for any other purpose is not sanctioned by the author. So - do not use this tool as a parachute, or to dry your cat, chill meat, answer your phone, drive you car, teach your kids to read or attack other peoples computer systems or networks.
This software has been designed for "legal" and "appropriate" use by network security administrators and the like. It has been written as part of a larger Linux firewall project, targetting at controlling traffic from peer-to-peer software such as Kazaa, iMesh and others into and out of a private network. It is not designed as a tool for malicious use and the author in no way sanctions such use.
Users of the software should be aware that its actions are easily detectable using a number of readily available network monitoring tools, and it makes no attempt to disguise its actions. Malicious use of "cutter" could result in a jail sentance in a number of countries around the world.
<<lessCutter is an open source program that uses the FIN-ACK-RST packet technique described above to abort TCP/IP connections routed over the firewall or router on which it is run. It can be called using one of the following four syntaxes.
cutter ip-address
Example: "cutter 10.10.0.45"
Cuts all connections passing through the firewall between any ports on the specified ip-address (either a "private" or "public" address) and any other hosts. This can be used to close down all incoming connections to a particular server, all outgoing connections from a particular client or all outgoing connections to a server.
cutter ip-address port
Example: "cutter 200.1.2.3 80"
Cuts all connections to or from the specified ip-address/port pair. This allows the user to be a little more specific than the previous example and allows targetting of specific services on specific hosts.
cutter ip-address-1 port-1 ip-address-2
Example "cutter 200.1.2.3 22 10.10.0.45"
Cuts all connections between ip-address-2 and ip-address-1/port-1. This allows the user to cut connections between a specified "client" and a particular service on a specified host. Our example closes host 10.10.0.45s SSH connection to server 200.1.2.3.
cutter ip-address-1 port-1 ip-address-2 port-2
Example: "cutter 200.1.2.3 22 10.10.0.45 32451"
Cuts the specific connection between the two ip/port number pairs given.
IMPORTANT WARNING
Cutter has been designed for use as a administrators tool for Linux firewalls. Its use (as is, or modified) for any other purpose is not sanctioned by the author. So - do not use this tool as a parachute, or to dry your cat, chill meat, answer your phone, drive you car, teach your kids to read or attack other peoples computer systems or networks.
This software has been designed for "legal" and "appropriate" use by network security administrators and the like. It has been written as part of a larger Linux firewall project, targetting at controlling traffic from peer-to-peer software such as Kazaa, iMesh and others into and out of a private network. It is not designed as a tool for malicious use and the author in no way sanctions such use.
Users of the software should be aware that its actions are easily detectable using a number of readily available network monitoring tools, and it makes no attempt to disguise its actions. Malicious use of "cutter" could result in a jail sentance in a number of countries around the world.
Download (0.013MB)
Added: 2005-12-14 License: GPL (GNU General Public License) Price:
1557 downloads
Linux LiveCD Router 2.0.24
Linux LiveCD Router is a Linux distribution designed to share a broadband connection over WiFi. more>>
Linux LiveCD Router project allows you to share and firewall your broadband connection and use WIFI.
You can use DSL, ADSL, Cable Modem, T1, Fixed IPs, Dial-Up, WIFI, build you own Access Point and more.
Main features:
- Share and Firewall your broadband or dedicated Internet connection
- Includes Firewall Shorewall and Masquerading (NAT)
- Does not require any installation. It is a LiveCD, your computer simply boots straight from the CD. Does not require a hard disk
- Supports DSL, Cablemodem, Fixed IP and Dial-Up
- Traffic Control, QoS
- DHCP Client and Server
- Remote SSH administration
- Includes DNS Cache to accelerate surfing
- Includes SNMP Monitoring, MRTG graphical statistics
- Use standard and low cost computer, networking and wifi hardware (also USB)
- Can use multiple ethernet and wifi 802.11a/b/g cards. Supports PCI, USB and PCMCIA cards (can replace external Access Points!)
- Linux Software compatible with Windows and Mac Networks
<<lessYou can use DSL, ADSL, Cable Modem, T1, Fixed IPs, Dial-Up, WIFI, build you own Access Point and more.
Main features:
- Share and Firewall your broadband or dedicated Internet connection
- Includes Firewall Shorewall and Masquerading (NAT)
- Does not require any installation. It is a LiveCD, your computer simply boots straight from the CD. Does not require a hard disk
- Supports DSL, Cablemodem, Fixed IP and Dial-Up
- Traffic Control, QoS
- DHCP Client and Server
- Remote SSH administration
- Includes DNS Cache to accelerate surfing
- Includes SNMP Monitoring, MRTG graphical statistics
- Use standard and low cost computer, networking and wifi hardware (also USB)
- Can use multiple ethernet and wifi 802.11a/b/g cards. Supports PCI, USB and PCMCIA cards (can replace external Access Points!)
- Linux Software compatible with Windows and Mac Networks
Download (MB)
Added: 2007-06-20 License: GPL (GNU General Public License) Price:
888 downloads
Other version of Linux LiveCD Router
Linux LiveCD Router Documentation package contains documentation for ... LiveCD Router. Linux LiveCD Router allows you to share and firewall your broadband connectionLicense:GPL (GNU General Public License)
SIP Express Router 0.9.6
SIP Express Router is a very fast and flexible SIP (RFC3261) server. more>>
SIP Express Router (ser) is a high-performance, configurable, free SIP ( RFC3261 ) server .
SER features an application-server interface, presence support, SMS gateway, SIMPLE2Jabber gateway, RADIUS/syslog accounting and authorization, server status monitoring, FCP security, etc. Web-based user provisioning, serweb, available.
Its performance allows it to deal with operational burdens, such as broken network components, attacks, power-up reboots and rapidly growing user population.
SERs configuration ability meets needs of a whole range of scenarios including small-office use, enterprise PBX replacements and carrier services.
Main features:
- accounting
- digest authentication
- CPL scripts
- ENUM support
- instant messaging
- MySQL support
- PostgreSQL support
- a presence agent
- Radius authentication and accounting
- Diameter authentication
- record routing
- SMS gateway
- Jabber gateway
- NAT traversal support transaction module
- registrar
- user location
SER has been extensively and successfuly tested with many SIP products from other vendors (Microsoft, Cisco, Mitel, snom, Pingtel, Siemens, and many others). It has been powering our SIP services continuously for more than two years.
<<lessSER features an application-server interface, presence support, SMS gateway, SIMPLE2Jabber gateway, RADIUS/syslog accounting and authorization, server status monitoring, FCP security, etc. Web-based user provisioning, serweb, available.
Its performance allows it to deal with operational burdens, such as broken network components, attacks, power-up reboots and rapidly growing user population.
SERs configuration ability meets needs of a whole range of scenarios including small-office use, enterprise PBX replacements and carrier services.
Main features:
- accounting
- digest authentication
- CPL scripts
- ENUM support
- instant messaging
- MySQL support
- PostgreSQL support
- a presence agent
- Radius authentication and accounting
- Diameter authentication
- record routing
- SMS gateway
- Jabber gateway
- NAT traversal support transaction module
- registrar
- user location
SER has been extensively and successfuly tested with many SIP products from other vendors (Microsoft, Cisco, Mitel, snom, Pingtel, Siemens, and many others). It has been powering our SIP services continuously for more than two years.
Download (2.0MB)
Added: 2006-01-11 License: GPL (GNU General Public License) Price:
1393 downloads
Network Leak Finder 0.1a
Netleak is a collection of small perlscripts that detects connectivity between network segments. more>>
Netleak is a collection of small perlscripts that detects connectivity between network segments. It is mostly useful to detect "leaks" in large organizations that have private networks physically separated from the Internet.
Imagine some large corporation which has an internal development LAN were all sorts of sensitive information is flowing around. This corporation would likely have some very strict rules as to how its employees access the internet or other partner branches in order to
protect its information. For the systemadinistrator this is a daunting task - as the corporate LAN grows keeping track of all the routes through the network becomes extremely difficult. Some routers might simply have been forgotten over time or an employee might have gone wise and connected his own adsl-router or something alike.
Network Leak Finder tries to detect this in a centralized manner by sending out spoofed packets into the internal network and if any packets finds a way onto the external network, a "leak" has been detected. As an anology it works the same way you would find a hole in
a bucket: fill it with water and see if anything leaks.
In most scenarios the external network would be the Internet since everybody should be afraid of what their corporate LANs are leaking to it!
<<lessImagine some large corporation which has an internal development LAN were all sorts of sensitive information is flowing around. This corporation would likely have some very strict rules as to how its employees access the internet or other partner branches in order to
protect its information. For the systemadinistrator this is a daunting task - as the corporate LAN grows keeping track of all the routes through the network becomes extremely difficult. Some routers might simply have been forgotten over time or an employee might have gone wise and connected his own adsl-router or something alike.
Network Leak Finder tries to detect this in a centralized manner by sending out spoofed packets into the internal network and if any packets finds a way onto the external network, a "leak" has been detected. As an anology it works the same way you would find a hole in
a bucket: fill it with water and see if anything leaks.
In most scenarios the external network would be the Internet since everybody should be afraid of what their corporate LANs are leaking to it!
Download (0.018MB)
Added: 2006-07-01 License: GPL (GNU General Public License) Price:
1214 downloads
Prometheus QoS 0.7
Prometheus QoS is an ISP-oriented tool for easy manipulation of the IP traffic shaping and sharing features of the Linux kernel. more>>
QoS (or Quality-of-service) is traffic shaper replacement for Internet Service Providers (ISP). Dump your vintage hard-wired routers/shapers (C|sco, etc.) in favour of powerful open source and free solution !
Prometheus QoS generates multiple nested HTB tc classes with various rate and ceil values, and implements optional daily traffic quotas and data transfer statistics (as HTML). It is compatible with NAT, both asymetrical and symetrical, yet still provides good two-way shaping and prioritizing, both upload and download.
Prometheus QoS was written in C<<less
Prometheus QoS generates multiple nested HTB tc classes with various rate and ceil values, and implements optional daily traffic quotas and data transfer statistics (as HTML). It is compatible with NAT, both asymetrical and symetrical, yet still provides good two-way shaping and prioritizing, both upload and download.
Prometheus QoS was written in C<<less
Download (0.042MB)
Added: 2007-02-20 License: GPL (GNU General Public License) Price:
997 downloads
mrouted 3.9 Beta 3
mrouted project is a DVMRP multicast routing daemon. more>>
mrouted project is a DVMRP multicast routing daemon.
mrouted is an implementation of the DVMRP multicast routing protocol. It turns a UNIX workstation into a DVMRP multicast router with tunnel support, in order to cross non-multicast-aware routers.
Enhancements:
- IGMP could report membership in local-only groups (i.e. 224.0.0.X)
- IGMP could get confused by hearing its own new membership reports, thus a router would never perform fast leave.
- IGMP could reset timers for the wrong interface.
- mrouted put a bogus value in the maximum timeout field of IGMPv2 query packets.
- Non-querier mrouters would respond to IGMP leave messages
- mrouted was not performing fast leave properly
- If the last member goes away on a transit network, the upstream router would stop forwarding even if there are downstream members.
- Kernel hash function improved
- Eliminated possibility of panic(): timeout in cache maintenance
- Reordered resource allocation when sending upcall to handle failure properly
- some endian-ness bugs squashed in mrouted, probably more to go.
- Multicast traceroute could send a reply on a disabled interface.
<<lessmrouted is an implementation of the DVMRP multicast routing protocol. It turns a UNIX workstation into a DVMRP multicast router with tunnel support, in order to cross non-multicast-aware routers.
Enhancements:
- IGMP could report membership in local-only groups (i.e. 224.0.0.X)
- IGMP could get confused by hearing its own new membership reports, thus a router would never perform fast leave.
- IGMP could reset timers for the wrong interface.
- mrouted put a bogus value in the maximum timeout field of IGMPv2 query packets.
- Non-querier mrouters would respond to IGMP leave messages
- mrouted was not performing fast leave properly
- If the last member goes away on a transit network, the upstream router would stop forwarding even if there are downstream members.
- Kernel hash function improved
- Eliminated possibility of panic(): timeout in cache maintenance
- Reordered resource allocation when sending upcall to handle failure properly
- some endian-ness bugs squashed in mrouted, probably more to go.
- Multicast traceroute could send a reply on a disabled interface.
Download (0.10MB)
Added: 2007-03-12 License: Freely Distributable Price:
982 downloads
ROSInfo 1.13
ROSInfo is a simple tool for monitoring signal levels, traffic, and network latency of x86 machines. more>>
ROSInfo is a simple tool for monitoring signal levels, traffic, and network latency of x86 machines, RouterBoards, and other devices running Mikrotik RouterOS.
The project was designed to be used with Mikrotik RouterOS 2.9 and is being developed and tested on a large network with many Mikrotik routers.
Currently supported and tested are all versions of Mikrotik RouterOS 2.9.
<<lessThe project was designed to be used with Mikrotik RouterOS 2.9 and is being developed and tested on a large network with many Mikrotik routers.
Currently supported and tested are all versions of Mikrotik RouterOS 2.9.
Download (0.074MB)
Added: 2006-12-08 License: GPL (GNU General Public License) Price:
1081 downloads
BitWise Routing Server 1.7
BitWise Routing Server allows multiple PCs behind a router to make direct connections. more>>
BitWise Routing Server allows multiple PCs behind a router to make direct connections.
The BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.
As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.
The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).
The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.
The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.
Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.
In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.
If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.
Setting up the physical router
The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.
The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).
Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.
Configuring BitWise to use the Routing Server
In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).
Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.
Registration with the Routing Server
Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.
It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.
Using the Routing Server
Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.
The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.
<<lessThe BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.
As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.
The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).
The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.
The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.
Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.
In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.
If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.
Setting up the physical router
The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.
The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).
Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.
Configuring BitWise to use the Routing Server
In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).
Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.
Registration with the Routing Server
Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.
It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.
Using the Routing Server
Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.
The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.
Download (1.0MB)
Added: 2006-03-02 License: Freeware Price:
1331 downloads
Network Device Change Control 3.10
Network Device Change Control (NDCC) is a system that monitors and records changes to the configurations of network equipment. more>>
Network Device Change Control (NDCC) is a system that monitors and records changes to the configurations of network equipment.
Network Device Change Control can store configuration snapshots for any text-based configs. It has been used to store configurations from Unix and Linux systems, Cisco routers, switches, load balancers, and firewalls, Foundry, NetScreen, Juniper, NetScaler, and others.
It only took a while to realize that router changes should be tracked. I rewrote the system to give a current and once-back system of configurations. Since I was using diff, I decided to leave the diff information in the system. Those diffs were emailed to a group so everyone knew when something was changed, along with what was changed.
Some time later, a bank needed to track configuration files, and the system was upgraded for use within a database. The first implementation was using perl as a CGI script against a PostgreSQL database. The company wanted many changes made for their auditing needs and most of those changes enhanced NDCC. Upgrades to their environment moved things to PHP and MySQL, and the system was rewritten for that environment and the old perl code has since been lost.
<<lessNetwork Device Change Control can store configuration snapshots for any text-based configs. It has been used to store configurations from Unix and Linux systems, Cisco routers, switches, load balancers, and firewalls, Foundry, NetScreen, Juniper, NetScaler, and others.
It only took a while to realize that router changes should be tracked. I rewrote the system to give a current and once-back system of configurations. Since I was using diff, I decided to leave the diff information in the system. Those diffs were emailed to a group so everyone knew when something was changed, along with what was changed.
Some time later, a bank needed to track configuration files, and the system was upgraded for use within a database. The first implementation was using perl as a CGI script against a PostgreSQL database. The company wanted many changes made for their auditing needs and most of those changes enhanced NDCC. Upgrades to their environment moved things to PHP and MySQL, and the system was rewritten for that environment and the old perl code has since been lost.
Download (0.046MB)
Added: 2006-08-09 License: GPL (GNU General Public License) Price:
1177 downloads
Jimsim Network Simulator 1.1
Jimsim is an application that emulates several routers connected via virutal networks. more>>
Jimsim Network Simulator project can emulate several routers connected via virutal networks. You can connect to the routers with your own favorite telnet program.
Connecting to the Virtual Routers
Use your favorite telnet program to connect to each of the virtual routers. For example:
For router 1 type:
C:>telnet localhost 10000
For router 2 type:
C:>telnet localhost 10001
For router 3 type:
C:>telnet localhost 10002
Network Layout
Currently the network is configured like this:
access-list [1-99] [permit/deny] [ ip wildcard-mask | host a.b.c.d | any ]
ip acccess-list [standard] [name]
ip access-group
show access-list
show ip interface
show ip interface brief
debug interface
encapsulation [hdlc,ppp] (serial interfaces only)
bandwidth
clock rate (serial interfaces)
interface loopback0
User commands:
?
enable
exit
ping ip
show cdp
show cdp neigh
show cdp neigh detail
show interface
show interface e0,eth0,etc
show ip route
show version
Enable commands:
clear counters
clear counters interface
config terminal
copy running startup
copy startup running
debug all
debug ip routing
debug ip eigrp
debug cdp
disable
exit
reload
show run
show startup
show ip eigrp neighbors
show ip eigrp topology
traceroute ip
undebug all
undebug ip routing
undebug ip eigrp
undebug cdp
Config commands:
cdp run
enable password password
end
hostname
banner motd delimiter
banner exec delimiter
banner login delimiter
ip route network netmask dest
interface e0,eth0,etc
bandwidth value
ip address addr netmask
description
cdp enable
shutdown
line con0, console0, console 0
login
login local
password passwd
router eigrp number
network a.b.c.d
service password-encryption
user username password password
Version restrictions:
- The EIGRP support is very basic. Just the network command for now. (Neighbors dont expire.) You can disable EIGRP with "no router eigrp process_id"
- The routing table isnt 100% correct. It doesnt summarize subnets. Nor does it understand multiple routes to the same destination. This will be fixed in the next version.
- Traceroute seems to count extra hops. Its counting each remote interface on a router as a hop. So, when you traceroute from router1 to router3, it counts router2 twice (once for 192.168.1.2 and 10.1.1.1)
<<lessConnecting to the Virtual Routers
Use your favorite telnet program to connect to each of the virtual routers. For example:
For router 1 type:
C:>telnet localhost 10000
For router 2 type:
C:>telnet localhost 10001
For router 3 type:
C:>telnet localhost 10002
Network Layout
Currently the network is configured like this:
access-list [1-99] [permit/deny] [ ip wildcard-mask | host a.b.c.d | any ]
ip acccess-list [standard] [name]
ip access-group
show access-list
show ip interface
show ip interface brief
debug interface
encapsulation [hdlc,ppp] (serial interfaces only)
bandwidth
clock rate (serial interfaces)
interface loopback0
User commands:
?
enable
exit
ping ip
show cdp
show cdp neigh
show cdp neigh detail
show interface
show interface e0,eth0,etc
show ip route
show version
Enable commands:
clear counters
clear counters interface
config terminal
copy running startup
copy startup running
debug all
debug ip routing
debug ip eigrp
debug cdp
disable
exit
reload
show run
show startup
show ip eigrp neighbors
show ip eigrp topology
traceroute ip
undebug all
undebug ip routing
undebug ip eigrp
undebug cdp
Config commands:
cdp run
enable password password
end
hostname
banner motd delimiter
banner exec delimiter
banner login delimiter
ip route network netmask dest
interface e0,eth0,etc
bandwidth value
ip address addr netmask
description
cdp enable
shutdown
line con0, console0, console 0
login
login local
password passwd
router eigrp number
network a.b.c.d
service password-encryption
user username password password
Version restrictions:
- The EIGRP support is very basic. Just the network command for now. (Neighbors dont expire.) You can disable EIGRP with "no router eigrp process_id"
- The routing table isnt 100% correct. It doesnt summarize subnets. Nor does it understand multiple routes to the same destination. This will be fixed in the next version.
- Traceroute seems to count extra hops. Its counting each remote interface on a router as a hop. So, when you traceroute from router1 to router3, it counts router2 twice (once for 192.168.1.2 and 10.1.1.1)
Download (0.65MB)
Added: 2006-03-08 License: Free for non-commercial use Price:
1325 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above routers woodworking search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
