WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tiny Core as a BASIC 4 port ROUTER ?  (Read 5559 times)

Offline mbzadegan

  • Newbie
  • *
  • Posts: 33
Tiny Core as a BASIC 4 port ROUTER ?
« on: August 29, 2010, 02:07:46 AM »
Hi,
Can any one guide me to convert my Tiny Core into Basic Router ( RIPv2 ) ?
i visited http://forum.tinycorelinux.net/index.php?topic=1219.0 but it does not told how i doing it !
is the solution only with IPTABLES ( for firewall ) ? ::)
« Last Edit: August 29, 2010, 04:42:59 AM by mbzadegan »

Offline andriscom

  • Newbie
  • *
  • Posts: 32
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #1 on: October 18, 2010, 10:10:46 AM »
I would also be interested in this.
Unfortunately I could not find any simple way to do it.
I'm a bit afraid doing this because my last 3 routers had some problems: They dropped my internet connection when I turned on QoS functionality and started massive torrent downloading. The router's CPU just couldn't handle the big traffic with QoS. Image just what would happen if you would use a torrent client on your router box which starts to hash the downloaded data, or you just copy some files via samba (gigabit) which would eat your CPU... I think we would face the same problems... dropping internet connection, dropping wireless clients, malfunctioning firewall, stopping dhcp functionality, lagging LAN connections etc :(


Here is a list of what is actually needed for router capability:
 - General routing function: RIPv2 etc... maybe with: iproute2.tcz
 - DHCP server: I haven't find any in the repo. And what about address reservation?
 - NAT functions: Should be done by the dhcp server? or by the firewall? I dunno...
 - PPPoE connection handling: Should be done with: pppd.tcz pppsetup.tcz
 - SPI Firewall: I don't really know what Stateful Packet Inspection is, and how to set iptables to work like that
 - Wireless AP: hostapd.tcz is fine for this task (I guess it's a lot of work to setup WEP/WPA/WPA2 and the other stuff correctly)
 - DynDns update client: inadyn or ddclient (none of them are in the repository)
 - Simple webserver to have a WebGUI: I vote for Cherokee, but I think there is no WebGUI available for configuring the general router stuff.
 Some logging: iptables, netstat, etc...

 Nice to have extras:  QoS functions,  traffic shaping by ethernet interface, torrent client, ftp server, samba server, printer sharing, mail server (a bit out of scope)

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #2 on: October 18, 2010, 10:31:09 AM »
udhcpd is in base plus there is a dhcpcd.tcz extension ;)
« Last Edit: October 18, 2010, 12:28:10 PM by tinypoodle »
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline SvOlli

  • Full Member
  • ***
  • Posts: 193
  • Linux Developer
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #3 on: October 18, 2010, 11:44:00 AM »
These are dhcp clients, not servers.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #4 on: October 18, 2010, 12:36:05 PM »
These are dhcp clients, not servers.

WRT dhcpcd you are right, I made an unfounded assumption without checking, my bad.   :-X

But udhcpd is a dhcp server, as opposed to udhcpc which is a client, both are included in TC base.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline SvOlli

  • Full Member
  • ***
  • Posts: 193
  • Linux Developer
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #5 on: October 18, 2010, 12:53:22 PM »
udhcpd is where I was misled. I was assuming that it was not configured into busybox for size vs. usefulness. A dhcp server is something that's very rarely needed, and from an architectural view should be run from an extension.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #6 on: October 18, 2010, 01:01:15 PM »
udhcpd is essential to tc-terminal-server which is in TC base (netboot).
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline andriscom

  • Newbie
  • *
  • Posts: 32
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #7 on: October 19, 2010, 05:23:30 AM »
Ok, dhcp server isn't the biggest problem.
What about the others?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10960
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #8 on: October 19, 2010, 05:28:45 AM »
Everything should be doable, but I don't think there's an extension for the RIP stuff.
The only barriers that can stop you are the ones you create yourself.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #9 on: October 19, 2010, 05:54:51 AM »
« Last Edit: October 19, 2010, 06:01:57 AM by tinypoodle »
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline andriscom

  • Newbie
  • *
  • Posts: 32
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #10 on: October 20, 2010, 12:53:35 AM »
Ok, so we need bridge-utils to act like a switch or router with the multiple ethernet interfaces. This was the thing that I was missing  :)

As for the web configuration interface: Webmin can be used:
http://www.webmin.com/index.html
(or you can just make your own WebGUI if you want to  ;))

As for the SPI firewall, you can configure iptables, here is a howto:
http://forums.pcper.com/showthread.php?t=432469
Or you can just use Configserver Security & Firewall scripts:
http://www.configserver.com/cp/csf.html

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Tiny Core as a BASIC 4 port ROUTER ?
« Reply #11 on: October 21, 2010, 02:51:43 PM »
Ok, so we need bridge-utils to act like a switch or router with the multiple ethernet interfaces. This was the thing that I was missing  :)

I had overlooked that there is an existing extension, my bad   :-\

http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/tcz/bridge-utils.tcz.info
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)