From: Don Gould <dig@bvc.com.au>
To: lartc@vger.kernel.org
Subject: [LARTC] 2 WAN - 1 LAN - ping and route problem
Date: Fri, 24 Mar 2006 10:31:15 +0000 [thread overview]
Message-ID: <1143196274.1612.133.camel@localhost> (raw)
ClarkConnect Home 3.2
eth0 - WAN - inet - ip:192.168.1.2 gw:192.168.1.1 (connected to my
www.woosh.co.nz gatway)
wlan - WAN - private community wireless networt - ip:10.252.16.16
gw:10.252.16.1
eth1 - LAN - ip:192.168.2.1
# route add -net 10.0.0.0 netmask 255.0.0.0 gw 10.252.16.1
[root@bowenvale etc]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.252.16.0 * 255.255.255.224 U 0 0 0 wlan0
192.168.2.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
10.0.0.0 10.252.16.1 255.0.0.0 UG 0 0 0 wlan0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
[root@bowenvale etc]#
I can ping 10.252.1.7 from the cc box (which is called 'bowenvale').
I can't get a ping result from any of the machines connected to the
LAN(192.168.2.0/24)
I can ping anything on the internet ok (ie where the ip being pinged is
located on the default route).
I've had it suggested to me that my problem is that I don't have the NAT
set up correctly to nat WAN-wlan0 --> LAN-eth1
I've had a look at the multi-WAN module but that seems to be more for
dealing with two or more wan links where they're both inet.
I want the 10.0.0.0 network on the WAN side of the network because it's
a public access network, hence needs to be on the other side of my
firewall.
What am I doing wrong and what should I be doing?
Cheers Don
--
Don Gould
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-03-24 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 10:31 Don Gould [this message]
2006-03-24 16:11 ` [LARTC] 2 WAN - 1 LAN - ping and route problem Mike Wright
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=1143196274.1612.133.camel@localhost \
--to=dig@bvc.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.