On Thu, 11 Feb 2010 12:28:00 +0100, Eric <(E-Mail Removed)> wrote:
>> On Wed, 10 Feb 2010 15:45:06 +0100, Eric <(E-Mail Removed)> wrote:
>>
>>>> On Tue, 09 Feb 2010 16:33:36 +0100, Eric <aucune@adresse> wrote:
>>>>
>>>>> Hi,
>>>>> I'm trying to configure a dir-100 d-link router to access to a
>>>>> 192.168.20.0 network from a 192.168.0.0 network. I don't know how to
>>>>> attribute an ip address for the wan interface. The ip address for the
>>>>> routeur is 192.168.0.51.
>>>>
>>>> Log into the router and select manual setup, then select "Static IP"
>>>> for the WAN interface. Enter the IP and Netmask that you want, (plus
>>>> gateway IP and DNS, if desired). Does that do it for you?
>>>
>>> thanks. It's ok from a side (from lan to wan), but i can't ping from
>>> the other. I have to search where the problem is.
>>
>> Actually, that's probably normal. The DIR-100, like every NAT router,
>> defaults to blocking connection attempts in the WAN->LAN direction. If
>> that's not the desired behavior, you can forward specific ports to
>> specific hosts on the LAN side of the router, or you can put a
>> specific host in the router's DMZ (a misnomer, but think of it as
>> simply forwarding ALL ports to that host), or look around in the
>> router's config and see if it has a "router" mode versus a "gateway"
>> mode. If so, by default it will be in gateway mode, but changing it to
>> router mode will make it act the same in both directions and is
>> probably what you want.
>
>Hi,
>I don't need to make a route from WAN to LAN ?
If I'm reading your initial post correctly, you want to be able to
access a network on the WAN side of the router from a computer on the
LAN side of the network. You don't need to specify any routes to do
that.
|