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

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

Re: accessing to router

Show all headers | View raw

On Tue, 14 Feb 2012 07:54:46 +0100, alanford wrote:

> This are the setting of my video recorder connected to my local network:
> 192.168.1.250
> 255.255.255.0
> 192.168.1.1
> dns: 85.114.42.51
> This is where i need to connect from internet, throe my router.
> Video recorder has normal network card, as any computer.

If 192.168.1.250 is something like mythtv backend, you do not want to
limit port connections. If you are trying to just hit the web server
then just forwarding port 80 should be ok.

> ------------------------------------------------------------
> I have also tested with my local PC located on 192.168.1.11 and this is 
> the result.The settings in router are the same as for video recorder but 
> 250 is changed to 11. DMZ,open port, port forward.
>
> 192.168.1.1	192.168.1.11	TCP	http > 55964 [ACK] 

Ok, I'll guess that is a result of you putting your internet address
into your browser or a script kitty script hitting port 80.

> 91.123.204.56	192.168.1.11	TCP	5938 > 59301 [PSH, 

There is a packet from somewhere in Sweden.

> 85.114.34.28	192.168.1.11	TCP	pop3s > 34332 [FIN, 

Guessing that appears to be a connection from your ISP's email server.

It is kinda hard to see what is going on when 192.168.1.11 apps are
chatting on the net.

With wireshark in the promiscuous mode on 192.168.1.11, and set to
watch for 192.168.1.250 packets only, you should be able to have the
router forward to 192.168.1.250 and see activity when you try to
connect to the video application from 192.168.1.11.

If you see packet activity but no application operation then I would
have to guess firewall/video access restrictions on 192.168.1.250
causing the malfunction.

By the way, you can get your internet ip with something like
wget -nv -O- http://cfaj.freeshell.org/ipaddr.cgi 

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