* [LARTC] Simplest Routing Question EVER
@ 2001-03-02 22:05 Fei
2001-03-02 22:24 ` bert
` (5 more replies)
0 siblings, 6 replies; 7+ messages in thread
From: Fei @ 2001-03-02 22:05 UTC (permalink / raw)
To: lartc
<PRE>This must be the easiest question ever, but I've been stumped for
days. I can't seem to get my Linux box to route traffic through
to my Win box. What I have is:
T1 Gateway : 100.0.0.1
eth1 (Connected to gateway) : 100.0.0.2
eth2 (Connected to Win) : 100.0.0.3
Win box : 100.0.0.202
(eth0 is connected to DSL, but that doesn't matter for now)
for the rules, I have:
0: from all lookup local
32766: from all lookup main
32767: from all lookup 253
for the routes I have:
100.0.0.202 dev eth2 proto kernel scope link src 100.0.0.3
100.0.0.1 dev eth1 proto kernel scope link src 100.0.0.2
127.0.0.1 dev lo scope link
default via 100.0.0.1 dev eth1
All I'm trying to do is to get the Windows machine to be able to
use the Internet. I've read everything I could find, but I can't
seem to get it to work. I've tried 'echo 1 > /proc/sys/net/ipv4/ip_forward',
flushing the cache, reading the adv routing howto over and over,
but I can't seem to get this to work. Any sugestions?
Thanks,
Fei Lung
$ chown flung universe
====================================
Easy and free access to your email anywhere! <A HREF="http://www.starten.net/mail">http://www.starten.net/mail</A>
====================================
</PRE>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [LARTC] Simplest Routing Question EVER
2001-03-02 22:05 [LARTC] Simplest Routing Question EVER Fei
@ 2001-03-02 22:24 ` bert
2001-03-02 22:40 ` Fei
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: bert @ 2001-03-02 22:24 UTC (permalink / raw)
To: lartc
<PRE>On Fri, Mar 02, 2001 at 05:05:50PM -0500, Fei Lung wrote:
><i> This must be the easiest question ever, but I've been stumped for
</I>><i> days. I can't seem to get my Linux box to route traffic through
</I>><i> to my Win box. What I have is:
</I>
The problem is that your Windows box doesn't have a publically routable IP
address, probably. Search with google.com on 'rusty three line guide
masquerading' - this will allow your windows box to roam the internet using
the IP address of your gateway.
If you *do* have routable IP addresses for yuur subnet, your gateway needs
to know where to send data intended for your subnet. IP is very much a
two-way thing.
Regards,
bert
--
<A HREF="http://www.PowerDNS.com">http://www.PowerDNS.com</A> Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</PRE>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [LARTC] Simplest Routing Question EVER
2001-03-02 22:05 [LARTC] Simplest Routing Question EVER Fei
2001-03-02 22:24 ` bert
@ 2001-03-02 22:40 ` Fei
2001-03-03 0:46 ` Mike
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Fei @ 2001-03-02 22:40 UTC (permalink / raw)
To: lartc
<PRE>My Windows box does have a publicly routable IP address. Actually,
I have a /24 subnet and I aws just using the windows box to test
with before I take the network down to install the machine as a router.
In the future, after I get this working, I will add a DSL line
to it, but first, I need to get the forwarding working.
Thanks,
Fei Lung
At Friday, 2 March 2001, bert hubert <<A HREF="mailto:ahu@ds9a.nl">ahu@ds9a.nl</A>> wrote:
><i>On Fri, Mar 02, 2001 at 05:05:50PM -0500, Fei Lung wrote:
</I>>><i> This must be the easiest question ever, but I've been stumped for
</I>>><i> days. I can't seem to get my Linux box to route traffic through
</I>>><i> to my Win box. What I have is:
</I>><i>
</I>><i>The problem is that your Windows box doesn't have a publically routable
</I>IP
><i>address, probably. Search with google.com on 'rusty three line guide
</I>><i>masquerading' - this will allow your windows box to roam the internet
</I>using
><i>the IP address of your gateway.
</I>><i>
</I>><i>If you *do* have routable IP addresses for yuur subnet, your gateway
</I>needs
><i>to know where to send data intended for your subnet. IP is very much a
</I>><i>two-way thing.
</I>><i>
</I>><i>Regards,
</I>><i>
</I>><i>bert
</I>><i>
</I>><i>--
</I>><i><A HREF="http://www.PowerDNS.com">http://www.PowerDNS.com</A> Versatile DNS Services
</I>><i>Trilab The Technology People
</I>><i>'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</I>><i>
</I>
====================================
Easy and free access to your email anywhere! <A HREF="http://www.starten.net/mail">http://www.starten.net/mail</A>
====================================
</PRE>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [LARTC] Simplest Routing Question EVER
2001-03-02 22:05 [LARTC] Simplest Routing Question EVER Fei
2001-03-02 22:24 ` bert
2001-03-02 22:40 ` Fei
@ 2001-03-03 0:46 ` Mike
2001-03-03 1:57 ` Fei
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Mike @ 2001-03-03 0:46 UTC (permalink / raw)
To: lartc
<PRE>Fei Lung wrote:
><i>
</I>><i> This must be the easiest question ever, but I've been stumped for
</I>><i> days. I can't seem to get my Linux box to route traffic through
</I>><i> to my Win box. What I have is:
</I>><i>
</I>><i> T1 Gateway : 100.0.0.1
</I>><i> eth1 (Connected to gateway) : 100.0.0.2
</I>><i> eth2 (Connected to Win) : 100.0.0.3
</I>><i> Win box : 100.0.0.202
</I>><i> (eth0 is connected to DSL, but that doesn't matter for now)
</I>><i>
</I>><i> for the rules, I have:
</I>><i> 0: from all lookup local
</I>><i> 32766: from all lookup main
</I>><i> 32767: from all lookup 253
</I>><i>
</I>><i> for the routes I have:
</I>><i> 100.0.0.202 dev eth2 proto kernel scope link src 100.0.0.3
</I>><i> 100.0.0.1 dev eth1 proto kernel scope link src 100.0.0.2
</I>><i> 127.0.0.1 dev lo scope link
</I>><i> default via 100.0.0.1 dev eth1
</I>><i>
</I>><i> All I'm trying to do is to get the Windows machine to be able to
</I>><i> use the Internet. I've read everything I could find, but I can't
</I>><i> seem to get it to work. I've tried 'echo 1 > /proc/sys/net/ipv4/ip_forward',
</I>><i> flushing the cache, reading the adv routing howto over and over,
</I>><i> but I can't seem to get this to work. Any sugestions?
</I>><i>
</I>><i> Thanks,
</I>><i> Fei Lung
</I>does your win box have your linux box set as it's default gw? can you get any
packets through?
What does `ipchains -L forward` say? does it default to "accept"?
Please give more info, and details on what tests have been tried and failed.
Mike
</PRE>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [LARTC] Simplest Routing Question EVER
2001-03-02 22:05 [LARTC] Simplest Routing Question EVER Fei
` (2 preceding siblings ...)
2001-03-03 0:46 ` Mike
@ 2001-03-03 1:57 ` Fei
2001-03-03 3:18 ` Mike
2001-03-03 14:14 ` bert
5 siblings, 0 replies; 7+ messages in thread
From: Fei @ 2001-03-03 1:57 UTC (permalink / raw)
To: lartc
<PRE>I am using kernel 2.4.1. Iptables shows accept for input, forward,
output. The Windows machine has the Linux machine as the gateway.
><i>From the windows machine, I can ping the IPs on the linux machine,
</I>but I cannot ping the T1 gateway.
><i>From the linux machine, I can go out the T1.
</I>
Thanks,
Fei Lung
At Friday, 02 March 2001, Mike Fedyk <<A HREF="mailto:mfedyk@matchmail.com">mfedyk@matchmail.com</A>> wrote:
><i>Fei Lung wrote:
</I>>><i>
</I>>><i> This must be the easiest question ever, but I've been stumped for
</I>>><i> days. I can't seem to get my Linux box to route traffic through
</I>>><i> to my Win box. What I have is:
</I>>><i>
</I>>><i> T1 Gateway : 100.0.0.1
</I>>><i> eth1 (Connected to gateway) : 100.0.0.2
</I>>><i> eth2 (Connected to Win) : 100.0.0.3
</I>>><i> Win box : 100.0.0.202
</I>>><i> (eth0 is connected to DSL, but that doesn't matter for now)
</I>>><i>
</I>>><i> for the rules, I have:
</I>>><i> 0: from all lookup local
</I>>><i> 32766: from all lookup main
</I>>><i> 32767: from all lookup 253
</I>>><i>
</I>>><i> for the routes I have:
</I>>><i> 100.0.0.202 dev eth2 proto kernel scope link src 100.0.0.3
</I>>><i> 100.0.0.1 dev eth1 proto kernel scope link src 100.0.0.2
</I>>><i> 127.0.0.1 dev lo scope link
</I>>><i> default via 100.0.0.1 dev eth1
</I>>><i>
</I>>><i> All I'm trying to do is to get the Windows machine to be able to
</I>>><i> use the Internet. I've read everything I could find, but I can't
</I>>><i> seem to get it to work. I've tried 'echo 1 > /proc/sys/net/ipv4/ip_forward',
</I>
>><i> flushing the cache, reading the adv routing howto over and over,
</I>>><i> but I can't seem to get this to work. Any sugestions?
</I>>><i>
</I>>><i> Thanks,
</I>>><i> Fei Lung
</I>><i>does your win box have your linux box set as it's default gw? can
</I>you get any
><i>packets through?
</I>><i>
</I>><i>What does `ipchains -L forward` say? does it default to "accept"?
</I>><i>
</I>><i>Please give more info, and details on what tests have been tried
</I>and failed.
><i>
</I>><i>Mike
</I>><i>
</I>><i>_______________________________________________
</I>><i>LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>><i><A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO: <A HREF="http://ds9a.">http://ds9a.</A>
</I>nl/2.4Routing/
><i>
</I>
====================================
Easy and free access to your email anywhere! <A HREF="http://www.starten.net/mail">http://www.starten.net/mail</A>
====================================
</PRE>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [LARTC] Simplest Routing Question EVER
2001-03-02 22:05 [LARTC] Simplest Routing Question EVER Fei
` (3 preceding siblings ...)
2001-03-03 1:57 ` Fei
@ 2001-03-03 3:18 ` Mike
2001-03-03 14:14 ` bert
5 siblings, 0 replies; 7+ messages in thread
From: Mike @ 2001-03-03 3:18 UTC (permalink / raw)
To: lartc
<PRE>Fei Lung wrote:
><i>
</I>><i> I am using kernel 2.4.1. Iptables shows accept for input, forward,
</I>><i> output. The Windows machine has the Linux machine as the gateway.
</I>><i> >From the windows machine, I can ping the IPs on the linux machine,
</I>><i> but I cannot ping the T1 gateway.
</I>><i>
</I>Whenever I get something like this, I either run ipchains or netfilter with the
check command, or add accounting rules and see where the packets stop. The
latter is only useful if you can make a rule specific enough to distinguish
between other traffic that may go through your firewall.
Please try the accounting rules, and see if you can find where the packets stop.
Mike
</PRE>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [LARTC] Simplest Routing Question EVER
2001-03-02 22:05 [LARTC] Simplest Routing Question EVER Fei
` (4 preceding siblings ...)
2001-03-03 3:18 ` Mike
@ 2001-03-03 14:14 ` bert
5 siblings, 0 replies; 7+ messages in thread
From: bert @ 2001-03-03 14:14 UTC (permalink / raw)
To: lartc
<PRE>On Fri, Mar 02, 2001 at 05:40:04PM -0500, Fei Lung wrote:
><i> My Windows box does have a publicly routable IP address. Actually,
</I>><i> I have a /24 subnet and I aws just using the windows box to test
</I>><i> with before I take the network down to install the machine as a router.
</I>><i> In the future, after I get this working, I will add a DSL line
</I>><i> to it, but first, I need to get the forwarding working.
</I>
Run tcpdump on all your interfaces and see where your packets are or aren't
going.
regards,
bert
--
<A HREF="http://www.PowerDNS.com">http://www.PowerDNS.com</A> Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</PRE>
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2001-03-03 14:14 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-03-02 22:05 [LARTC] Simplest Routing Question EVER Fei
2001-03-02 22:24 ` bert
2001-03-02 22:40 ` Fei
2001-03-03 0:46 ` Mike
2001-03-03 1:57 ` Fei
2001-03-03 3:18 ` Mike
2001-03-03 14:14 ` bert
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.