From: Andrew Ross <aross@westnet.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing tables help
Date: Sun, 29 Aug 2004 01:47:26 +0000 [thread overview]
Message-ID: <1093744046.8515.9.camel@localhost> (raw)
In-Reply-To: <64538.81.227.16.211.1093726252.squirrel@web4.gate9.se>
On Sun, 2004-08-29 at 06:50, johan.lindqvist@apspektakel.com wrote:
> I'm wondering if I could get some help setting up the routing tables in my
> ionteranl system. I've read what I have found about this, but I'm not
> getting any wiser...
> This is my network at home:
>
> Internet <-- DSL modem <--- Internet router (192.168.0.1)
> <--- eth1 (192.168.0.99) Linux server eth0 (192.168.1.122)
> ---> Workstation (192.168.1.22)
> ---> Thin client (192.168.1.12)
> Ok, the internal network is working fine. The linux server has a live
> internet connection aswell as the thin client. It's the workstation that
> won't get in the game. All computers are running suse 9.1 The linux server
> is using the internet router as default gateway and DNS. How do I set up
> the workstation? There is no firewall setup, and there is no need for one
> since the internet router takes care of that.
Your workstation needs to have the Linux server configured as the
default gateway. The Linux server needs to be configured to forward
packets between eth1 and eth0.
The workstation appears to have a statically configured IP, so you
should be able to enter the default gateway (192.168.1.122) where-ever
you entered the IP (192.168.1.22).
May I ask why you are using this set up? If you aren't running a
firewall on the Linux machine, and the Internet router does NAT, I can't
see any need to sit the Linux server between the Internet router and the
workstation or client client.
Your network topology could be simplied if the Linux server,
workstation, and thin client were all connected to the Internet router.
That said, I would personally reccomend you keep your existing setup,
but move the firewall and NAT back to the Linux server - Linux will
generally be more configurable (and powerful) and a consumer-level
router.
Cheers
Andrew
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-08-29 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 20:50 [LARTC] routing tables help johan.lindqvist
2004-08-29 1:47 ` Andrew Ross [this message]
2004-08-29 2:26 ` Andrew Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1093744046.8515.9.camel@localhost \
--to=aross@westnet.com.au \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.