I redo the diagram to show the gw info.
Router1: UTSStarCom WA3002G4
Wireless Router with 4 ethernet ports
NAT is enabled (Just a tickbox)
PC1, PC2 : gentoo, 2.6.18.3 kernel
Router2: LinkSys WRT54GL (default firmware)
used as access point
--------------------------------------------------
192.168.1.1
default gw: ISP net
192.168.2.0 gw: 192.168.1.23
+-+ +------------+
| |-----------| Router1 |=========ASDL conn
| | +------------+
| |
| |
| | 192.168.1.23 +-------+ 192.168.2.43
| |------------------| PC1 |----))).............
+-+ +-------+ .
Passive Hub gw: 192.168.1.1 .
.
192.168.2.1 .
+------------+ .
| W.AccessPt |--)))...
| (Router2) |
+------------+
|
+------+
| PC2 |
+------+
192.168.2.24
gw: 192.168.2.43
Yo Yo wrote:
> btw, why don't you use the wireless on the ROUTER1 (doesn't seem you
> want to do any firewalling on the PC1)?
Because this box is temporary, it will be replaced with a non-wireless
one by the ISP.
Richard Torres wrote:
> <snip> .. Unless you have 2 networks that need to be separate only one is
> needed. If you have a wireless router, use it as a wireless access point and
> not a router. Which means turn off DHCP on the wireless router and don't
> configure or use the WAN connection.
This router is LinkSys WRT54GL with default firmware and I am using
it really as an access point. There is no option to disable the WAN
connection, so I left it as 'DHCP'.
> Depending on the capabilities of the router you can connect a LAN port on
> Router2 to your ADSL (Router1) router and assign an IP address that's in the
> same network as Router1.
I agree this would have simplified the network, but the problem is, I cannot
run a cable due to walls in between. The default firmware on LinkSys does
not provide a client option. (Yes, I am aware of OpenWrt/DD-WRT etc )
I hope using the client option does not prevent the access point function.
reader wrote:
> By correct gateway I think in this case it would be the inward facing
> address of pc1 (192.168.2.43) so on router2 you would set the gw to
> that address.
Already done.
> And on pc2 the gw would be 192.168.2.1. That is unless router2 is
> just a WAP (wireless access point).
As router is just a WAP, the gw is set to 192.168.2.43.
kashani wrote:
> Router1 is the NAT device and everything else is internal or so I
> assumed. You don't want NAT behind NAT on your network if you can help
> it. It tends to break things and is hard to troubleshoot.
I just ticked the 'Enable NAT' tickbox in the router configuration.
> PC1 does need to have IP forwarding turned on which the original poster
> mentioned he configured.
Yes, this is done.
>The tests I would run are:
>
> ping 192.168.2.43 from router1. That'll test that router1 knows how to
> get to 192.168.2.0. I don't think packet forwarding has to be working
> for this to return since the interfaces are all local on PC1.
Ping is ok.
> ping router 1 from PC2 and vice versa. That'll make sure that PC1 is
> forwarding packets correctly.
Ping is ok.
> If both of these are fine, it's possible the router1 is not NATing
> 192.168.2.0/24 addresses.
Do you think an ISP would allow only one LAN segment (like 192.168.1.x)
and not allow 192.168.2.x at the same time ? Is there any incentive
for them ?
One thing, I cannot understand is the difference in traceroute
results. What does this say in plain english ? :-)
At PC2
# traceroute 218.248.240.46 (ISP's DNS server)
traceroute to 218.248.240.46 (218.248.240.46), 30 hops max, 40 byte packets
1 192.168.2.43 (192.168.2.43) 1.730 ms 0.840 ms 0.920 ms
2 192.168.1.1 (192.168.1.1) 1.440 ms 1.469 ms 1.287 ms
3 * * *
4 * * *
At PC1
# traceroute 218.248.240.46
traceroute to 218.248.240.46 (218.248.240.46), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 0.848 ms 0.706 ms 0.681 ms
2 117.192.128.1 (117.192.128.1) 19.712 ms 18.878 ms 19.920 ms
3 218.248.160.134 (218.248.160.134) 19.292 ms 19.796 ms 19.190 ms
--
sathish
--
[email protected] mailing list
