Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #1050

Re: accessing to router

Show all headers | View raw

On 10.2.12 5:02 , alanford wrote:
> On 02/09/2012 08:11 PM, Tauno Voipio wrote:
>> On 9.2.12 1:57 , alanford wrote:
>>>> Errm, the just forward that Port to your local IP address
>>>> an make sure someone is listening on it.
>>> *** I made this, but like i write i can not access it.
>>>
>>> Your not feit from your Provider changing IP address, though.
>>> *** this should not be a problem
>>
>>
>> 'Can not access' is not a good diagnostic.
>> What happens really (not just imagined)?
>>
>> Use a network sniffer, e.g. tcpdump or Wireshark to capture
>> the traffic with responses. If you cannot interpret the
>> results, post them, so we can try to help you.
>>
> -----------------
> wireshark is really very nice tool.
> What information do you need and for should i setup the wireshark.
>
> 192.168.1.222 is the local ip where i want to connect myself when in
> accessing my local network from internet, and this ip is opened, dmz-ed
> and forwarded.
>
> D-Link_dc:51:2c Broadcast ARP Who has 192.168.1.222? Tell 192.168.1.1


192.168.x.y is a RFC 1918 block address, which is not allowed to
be forwarded in the public Net. It is absolutely correct that you
cannot (and should not be able) access it from the outside.

To access something in the internal RFC 1918 network from the outside
net, you have to use the IP address on the outside network interface
in the router and do an address translation in the router, usually
called port forwarding.

-- 

Tauno Voipio

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

accessing to router alanford <af@mfb.com> - 2012-02-09 11:18 +0100
  Re: accessing to router Ralph Spitzner <rasp@spitzner.org> - 2012-02-09 12:21 +0100
    Re: accessing to router alanford <af@mfb.com> - 2012-02-09 12:57 +0100
      Re: accessing to router Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2012-02-09 21:11 +0200
        Re: accessing to router alanford <af@mfb.com> - 2012-02-10 16:02 +0100
          Re: accessing to router Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2012-02-10 22:29 +0200
            Re: accessing to router alanford <alanford@kjas.com> - 2012-02-11 16:29 +0100
              Re: accessing to router Bit Twister <BitTwister@mouse-potato.com> - 2012-02-11 16:17 +0000
                Re: accessing to router Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-02-11 18:38 +0000
                Re: accessing to router alanford <alanford@kjas.com> - 2012-02-12 11:26 +0100
                Re: accessing to router Bit Twister <BitTwister@mouse-potato.com> - 2012-02-12 10:46 +0000
                Re: accessing to router alanford <af@mfb.com> - 2012-02-13 09:57 +0100
                Re: accessing to router Bit Twister <BitTwister@mouse-potato.com> - 2012-02-13 09:21 +0000
                Re: accessing to router alanford <af@mfb.com> - 2012-02-14 07:54 +0100
                Re: accessing to router Bit Twister <BitTwister@mouse-potato.com> - 2012-02-14 08:10 +0000
                Re: accessing to router alanford <af@mfb.com> - 2012-02-16 12:38 +0100
                Re: accessing to router Bit Twister <BitTwister@mouse-potato.com> - 2012-02-16 11:46 +0000
                Re: accessing to router nescafe <nc@ms.com> - 2012-02-17 07:56 +0100

csiph-web