From: huffo@ig.com.br
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing problem
Date: Wed, 07 Apr 2004 01:16:46 +0000 [thread overview]
Message-ID: <20040407012356.36E0D456B@outpost.ds9a.nl> (raw)
In-Reply-To: <marc-lartc-101530055025659@msgid-missing>
I installed gated to resolve my routing problem. It wa s a RIP problem.
Thanks a lot,
Mauricio.
Em 07 Apr 2004, Damion de Soto escreveu:
>Hi Pereira,
>> i have one firewall/gateway server with two interfaces and a routing
>> problem (?).
>>
>> eth0: external interface
>> eth1: internal interface. Both ip address are valid.
>> Anyone can help me to find where is the problem? I think it´s a routing
>> problem, but i don´t know where it is...
>
>Has your ISP placed routing entries for eth1 IP via eth0 IP ?
>Are they on the same subnets ?
>If you do a traceroute from the internet, you should see your hops hit eth0
>(and then if everything was working, hit eth1)
>
> > Of course. IP_FORWARDING is enable for a long time.
>I assume you've also turned it on in /proc/sys/net/ipv4/ip_forward ?
>
>--
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Damion de Soto - Software Engineer email: damion@snapgear.com
>SnapGear - A CyberGuard Company --- ph: +61 7 3435 2809
> | Custom Embedded Solutions fax: +61 7 3891 3630
> | and Security Appliances web: http://www.snapgear.com
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> --- Free Embedded Linux Distro at http://www.snapgear.org ---
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>----------
_________________________________________________________
Voce quer um iGMail protegido contra vírus e spams?
Clique aqui: http://www.igmailseguro.ig.com.br
Ofertas imperdíveis! Link: http://www.americanas.com.br/ig/
_______________________________________________
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-04-07 1:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 3:55 [LARTC] routing problem suresh
2002-03-05 17:28 ` Ard van Breemen
2002-03-06 6:44 ` suresh
2002-11-20 17:31 ` [LARTC] Routing problem Mauro Cerboni
2002-11-22 0:03 ` Jose Luis Domingo Lopez
2002-11-22 0:32 ` George J. Jahchan, Eng.
2002-12-17 16:53 ` [LARTC] ROUTING Problem Andre Lorenz
2003-09-05 16:12 ` [LARTC] Routing problem gaston
2003-09-07 23:03 ` Damion de Soto
2003-09-08 6:41 ` Ronny Aasen
2003-09-08 14:46 ` gaston
2003-09-09 13:59 ` gaston
2003-11-10 12:29 ` [LARTC] routing problem Meretei Balázs
2003-11-10 23:55 ` Damion de Soto
2003-11-11 4:22 ` Martin A. Brown
2004-04-06 11:09 ` [LARTC] Routing problem huffo
2004-04-06 12:28 ` huffo
2004-04-06 23:32 ` Damion de Soto
2004-04-07 1:16 ` huffo [this message]
2004-04-07 1:26 ` huffo
2006-12-12 13:07 ` [LARTC] Routing Problem Javier A Toledano
2006-12-13 15:05 ` Taylor, Grant
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=20040407012356.36E0D456B@outpost.ds9a.nl \
--to=huffo@ig.com.br \
--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.