Re: [OT]ish Router +modem problem

[chris@xxxxxxxxxx]

Having looked again at your original email it occurred to me that my
initial assertion is a side issue - you have two different private address
in operation on your Lan side hence the reference to 192.168.3.1 (modem
gateway host address).

Your router Wan host 192.168.3.2, will have no problem talking to the
modem. The problem is the Lan pool 192.168.1.0 (am assume /24 address masks
in each instance on the two ranges?) differs.

Translation is not a viable solution for this problem. Easiest way would be
to have modem and router rolled in on one box. However I presume it would
defeat the object of your venture.





------------------

-----Original Message-----
From: "Peter Church" <yahoo@xxxxxxx>
Sender: ukha_d@xxxxxxx
Date: Fri, 7 Jan 2011 08:48:52
To: <ukha_d@xxxxxxx>
Reply-To: ukha_d@xxxxxxx
Subject: RE: [ukha_d] [OT]ish Router +modem problem

Isn't that effectively what DHCP in the router should be (and is?) doing?



Pete



Peter,

It sounds to me like you need to get the router to do address translation
from you Wan IP range to your Lan range and vice versa.
------------------

-----Original Message-----
From: "peter_church" <yahoo@xxxxxxx
<mailto:yahoo%40petechurch.co.uk>
>
Sender: ukha_d@xxxxxxx <mailto:ukha_d%40yahoogroups.com>
Date: Thu, 06 Jan 2011 23:13:04
To: <ukha_d@xxxxxxx <mailto:ukha_d%40yahoogroups.com>
>
Reply-To: ukha_d@xxxxxxx <mailto:ukha_d%40yahoogroups.com>
Subject: [ukha_d] [OT]ish Router +modem problem

I'm trying to set up the network in my holiday home so that it links to my
main home - that way I can control Comfort etc all via a VPN link (in
theory...). Problem is I can't even get that far and I think it is probably
some simple problem with the modem/router but cannot fathom it. Can anyone
of the bright sparks here suggest what might be wrong (bearing in mind I
cannot test again until I'm there in 6 weeks...)

At the simplest level the setup is this:

Huawei B260a 3g modem linked via Ethernet to a Netgear FVS318 Pro-Safe VPN
firewall, then the network.

The modem has DHCP capability, firewall, DMZ etc. facilities, but ideally
I'd want it just to present the WAN IP to the router (for the DynDNS VPN to
work) but I don't seem to be able to do that, so for now have enabled DHCP
on the modem (gateway 192.168.3.1 DHCP range .2-.100) to provide a LAN
address to the WAN port on the router.

The router is getting it's WAN IP address (192.168.3.2) from the router
then
acting as a DHCP for the LAN side of it (Gateway 192.168.1.1 range
.2-.100).
The management page on the router allows me to ping the web.

However when I connect a PC to the router the machine gets an IP address
but
cannot see the web. One thing I have noticed is that all of the assigned
DNS
servers inside the router refer to 192.168.3.1.

When I connect the PC straight to the modem it works.

I think it must be something to do with DNS or subnets, but am not that
familiar with the impact they have, so any pointers would be greatfully
received. I've tried various combinations including forcing the external
DNS
settings onto the router and the PC - no good. And moving the router to
192.168.3.101 range 102-200) and neither work.

I've left it with the router out of the loop and am receiving daily e-mails
from the low power PC I've left out there with temperatures and heating
settings - so I at least feel I've got something working!

TIA

Pete

PS there was a discussion recently around 3g signal boosters and I've got
one of those running as well - works well, although the positioning of the
antenna is extremely sensitive and trial and error has it only working
attached to the upper hinge of some french doors - but connection is rock
solid once there!

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]



------------------------------------

<*> Join the Automated Home Forums
http://www.automatedhome.co.uk/vbulletin/