Tiny Core Linux
Tiny Core Base => Micro Core => Topic started by: beerstein on March 22, 2012, 06:13:31 AM
-
Hi:
Has somebody configured TCL as a router?
F.I. PC using 2NICs - one NIC DHCP and connected to the DSL router (192.168.0.1) the other NIC connected to another LAN but configured as fixed IP (192.168.1.1) Or do I just need to config a bridge from 192.168.0.X to 192.168.1.X?
I did a search on "router(s)" within this forum and there was no result.
-
Split the topic.
-
Hi beerstein
It sounds like you are trying to connect a second LAN with a different block of IP addresses to an existing
DSL router. I think a bridge is what you are looking for.
-
Hi: Yes - this correct - can I configure the TCL machine to act like bridge?
-
Hi beerstein
On second thoughts, I'm not so sure a bridge will work. Here's something you can try.
Your router is set to 192.168.0.1. On the second network (192.168.1.xxx) try changing the NICs route and
default gateway to 192.168.0.1 (or should that be 192.168.1.1?).
-
If the sole purpose if the pc will be to route from lan to lan, I would say use another distro designed for that purpose.
I had used coyotelinux (coyotelinux.com) some years ago with success.
--holiday42
-
You can use TC as a bridge, see bridge-utils.tcz.
-
You can use TC as a bridge, see bridge-utils.tcz.
Bridiging means interconnection of ethernet ports to form a LAN hub/switch. Ports in a bridge do not have own IP address, it is just a LAN switch.
First specify for what purpose you are intending the two ports system wise. Do you want to share a LAN connection (in such case you need NAT), etc.
-
Thanks for your help. I would like to access PCs from within one network from PCs of the second network without
changing IP addresses and adress distribution methods. (fixed and DHCP)
In that particular case a TCL 3.8.4 PC is connected to the internet via its eth0 (on DHCP range 192.168.0.XX) to the router and the internet.
eth1 of this same computer is set at 192.168.1.1 and connected to a hub which is connected to some other Pcs within this adress range (192.168.1.XX)
Now - what I would like to do is to connect from PCs within one network to PCs belonging to the other network.
-
Use route command to route 192.168.1.xx to eth1. man page is a good starting point:
http://linux.about.com/od/commands/l/blcmdl8_route.htm
-
Hi beerstein
So you want the 192.168.0.xx PCs to be able to talk to the 192.168.1.xx PCs?
-
Hi Rich: Yes - only once in a while - otherwise I would regroup all PCs into one network (192.168.0.XX)