Re: Linux router howto - not just NAT

From: Terence Parker (terence_at_parker.com.hk)
Date: 12/24/03


Date: 23 Dec 2003 20:07:45 -0800

Thanks again for all the replies.

I have now managed to solve my problem, albeit with a completelty
different approach. Actually it's probably my fault - I assumed this
would be an 'iptables' issue and asked the wrong question right from
the beginning. I didn't realise myself that I was doing the equivalent
of looking for vegetables in a computer mall.

The answer to my woes : bridging.

Basically, I have two incoming Internet connections from two different
ISP's - one providing me a block of 3 IP addresses, the other a block
of 12. The incoming wires can be connected directly to a
computer/server (as it is now), with the real IP's assigned (actually,
two servers: one for each line). Workstations connect through NAT
through either of these servers. The problem is that there is no way
for me to assign real IP's to anything else since there is only one
incoming line.

Presumably, I could have connected both incoming lines into a switch -
and then designated that switch a 'real ip' switch. Then anything
plugged into that switch can use a real IP. That would have been much
easier - should I just have done that? Would there be any
disadvantages to having done that?

Instead, I have a computer with three NIC's and have plugged in both
of those incoming ISP connections, as well as another connection to
the above said switch. Using bridging tools, I have bridged the three
connections together and output it back out to the switch. Considering
that bridges are entirely transparent - presumably this is exactly the
same as I could have achieved above? Except now i'm un-necessarily
wasting more electricity!!

But anyways, at least now everyone should be clear on what it was that
I was going on about.

Thanks again,

Terence

> Cool, but what is your physical line type ? An ethernet connexion ? a
> lesaed line (G707, ...) ? ... Do you have an ADSL modem ? ...
>
> Depending on this, you should have a card on your computer with the
> corresponding physical interface.
>
> Next you ISP should "route" theses IPs to your Linux router, and so you
> should have your router ip address, that you will set to your linux box.
>
> Then you can fill your linux routing table with the other ips :
>
> - use the "route add ..." command to add route entries
> - set the ip of the "internal" servers with the ips.

--snip--



Relevant Pages

  • Re: scavenging opto-isolators
    ... you mention are two values of resistor. ... The "0" you noticed for jumper ... Black bodies with more than two connections (two on one side, ... When referring to pin function on a switch, ...
    (sci.electronics.misc)
  • Re: PC takes 40 attempts to start ????
    ... cold metal contracts and connections are poor. ... (Takes a lot of pushing in to eventually catch the power to turn on. ... Incidentally, if it is the 2 dollar switch, then one can ... Available Physical Memory 320.47 MB ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: On network (and otherwise) cabling a house...
    ... and also allow for landline phone connections ... to be carried on cat5e). ... you could even have a small low voltage cable to a switch and back. ... maybe plug some of the incoming cat5e cables into the ...
    (comp.sys.acorn.networking)
  • Re: Help needed connecting switch to network
    ... wired and wireless connections. ... the Netgear unit depending on the location I need to connect from. ... switch then the switch into the Netgear unit. ... You plug the switch into a LAN port on the router, with no cross over cable, just a plain cable like you use to connect a wire computer to a LAN port on the router. ...
    (alt.internet.wireless)
  • Re: DUN to connect to my home PC?
    ... It is called "Incoming Connections." ... Jeffrey Randow (Windows Networking & Smart Display MVP) ... Remote Networking Technology Support Site - ...
    (microsoft.public.windowsxp.work_remotely)