APLawrence - Information and Resources for Unix and Linux Systems, Bloggers and the self-employed
RSS Feeds Get APLawrence.com by RSS











(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Home > News Posts > gateway on one nic routing ––>Re: Must I have a NIC onthe same network as a router for an SCO gateway?
Printer Friendly Version




News Group Posts

gateway on one nic routing


Somebody is always looking for a way to save money, but sometimes (as Jeff chronicled here) desperation is the source of odd configurations.

Keep this in mind should you find yourself in similar straits: it's midnight, the second nic is dead.. of course you DO need to get the other gateway connected to the same physical lan too - which might not be quite as easy.


From: Jeff Liebermann <jeffl@comix.santa-cruz.ca.us>
Newsgroups: comp.unix.sco.misc
Subject: Re: Must I have a NIC on the same network as a router for an SCO gateway?
Date: Sat, 24 Jun 2000 09:00:57 -0700
Message-ID: <bjl9ls8ts1efe5agssro8l810tmimnh402@4ax.com> 

On Sat, 24 Jun 2000 00:47:35 GMT, Robert Side <rside@aiinc.ca> wrote:
>You can add
>a second NIC and the SCO box can route between the two networks. Or
>you should be able to alias a second IP for your NIC and route that
>way (I think???, Never done it!). Either way, make sure you turn on
>IP forwarding.

I've built a single NIC router using Linux for entertainment value and
in desperation.  (i.e. the 2nd NIC was blown, it was 3am, no spare NIC
within 25 miles, buying time, desperate, etc).  It does work.  Every
packet that is suppose to go through the router gets repeated again,
effectively doubling traffic on the network segment.  I vaguely recall
that someones arp command will complain that a single MAC address has
two IP's although that's perfectly legal for multi-homed systems.  I
had to disarm "arpwatch" to get it to cease complaining.

In some other newsgroups I tend to lurk, the issues and questions
surrounding do-it-thyself routers is common.  Invariably someone
suggests doing it with a single NIC.  From my reading and limited
experience, it does work, and only downside is the doubling of
traffic.  Of course, for an internal firewall/gateway, it's completely
useless because any workstation could point the IP stack directly at
the external router and instantly bypass the single NIC firewall.

Yeah, I guess one could save $20 and build a gateway/router/firewall
with a single NIC.  However, I don't think that what he wants.

Also, there's some web page describing how to build a firewall using
an old MacIntosh.  Since some of these only allowed a single NIC card,
it's also done this way.  (I don't recall if it's a hardware or MacOS
limitiation).

>If I am wrong with my assumption or with any of my guesses, you didn't
>supply enough info.

Assumption, the mother of all screwups.

I don't understand why he would need a 2nd gateway (to where?) when he
already has a router/gateway/firewall going somewhere.  Some clues as
to the topology and EXACTLY what one is trying to accomplish, would be
most helpful.


-- 
Jeff Liebermann   jeffl@comix.santa-cruz.ca.us
150 Felker St #D  Santa Cruz CA  95060
831-421-6491 pager   831-429-1240 fax
http://www.cruzio.com/~jeffl/sco/   SCO stuff


If this page was useful to you, please click to help others find it:  

Your +1's can help friends, contacts, and others on the web find the best stuff when they search.

Comments?




More Articles by



Click here to add your comments



Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.


My Troubleshooting E-Book will show you how to solve tough problems on Linux and Unix systems!


book graphic unix and linux troubleshooting guide


 I sell and support
 Kerio Mail server
pavatar.jpg

This post tagged:

       - Networking
       - TCP/IP
       - Troubleshooting




Unix/Linux Consultants

Skills Tests

Guest Post Here