All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] NEWBIE Linux Routing Problem?
Date: Tue, 27 May 2003 16:10:19 +0000	[thread overview]
Message-ID: <marc-lartc-105413871806030@msgid-missing> (raw)

On Thursday 29 May 2003 02:23, Karotu Tannang wrote:
> Hi All !
>
> I've been running into some minor problems with a linux box we installed as
> a Domain.
>
> The linux server serves two networks as follows:
>         192.168.1.0/25 on eth0
>         192.168.128/25 on eth1
>
> The good thing is that all machines on both networks can SEE each other
> including 'pinging' each other.
>
> After installing an Win 95 Internet Gateway on 192.168.1.2 ... only
> machines in the 192.168.1.0/25 network can use it to connect to the
> internet but not the ones in the 192.168.1.128/25 network.
>
> I've also done some reading on lartc.org but couldn't get any help... or
> maybe its just too complicated for me :( but I've included some info from
> our server as a result of my readings which I thought would be helpful..
>
> ip route list table main
> 192.168.1.0/25 dev eth0 scope link
> 192.168.1.128/25 dev eth0 scope link
> 127.0.0.0/8 dev lo scope link
>
> ip route table local
> local 192.168.1.1 dev eth0 proto kernel scope host src 192.168.1.1
> broadcast 192.168.1.0 dev eth0 proto kernel scope link src 192.168.1.1
> broadcast 127.255.255.0 dev  lo proto kernel scope link src 127.0.0.1
> local 192.168.1.129 dev eth1 proto kernel scope host src 192.168.1.129
> broadcast 192.168.1.128 dev eth1 proto kernel scope link src 192.168.1.129
> broadcast 192.168.1.255 dev eth1 proto kernel scope link src 192.168.1.129
> broadcast 192.168.1.127 dev eth0 proto kernel scope link src 192.168.1.1
> local 127.0.0.1 dev lo proto kernel scope host 127.0.0.1
> local 127.0.0.0/8 dev lo proto kernel scope host 127.0.0.1
>
> If anyone could kindly offer me some pointers on how to get the other
> network to connect to the internet via the Internet Gateway, I would be
> very grateful.
This is maybe a stupid answer, but have the enabled forwarding int he kernel ?
echo "1" > /proc/sys/net/ipv4/ip_forward

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-05-27 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 16:10 Stef Coene [this message]
2003-05-28  6:05 ` [LARTC] NEWBIE Linux Routing Problem? Karotu Tannang

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=marc-lartc-105413871806030@msgid-missing \
    --to=stef.coene@docum.org \
    --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.