Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Please help Ethernet Bridge Suddenly not allow access via ext ip


  • Please log in to reply
17 replies to this topic

#1 mattcctv

mattcctv

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 AM

Posted 29 October 2016 - 07:35 AM

Hi all,

Apologies if this has been covered already and apologies for my lack of technical knowledge

I was using TPLink to join my CCTV DVR to my router but had lots of drop out problems. Having spent weeks googling I realised it was not my DVR or router but probably the wiring in the house.

I found a Linksys WRT54GS v7 in my loft and followed online instructions to convert it into an ethernet bridge.

This was all working perfectly for four days and then suddenly at lunchtime yesterday i could no longer link externally.

Equipment Setup:
a. CCTV Cameras connected to
b. DVR QVIS i-appollo connected via ethernet out to
c. Ethernet Bridge, a converted Linksys WRT54GS using Micro Generic firmware
connected wirelessly to
d. BT Business Hom Hub 5 with static ip address

So now I can still link to the DVR wirelessly from my iPhone to the internal IP BUT i can no longer link externally via my static IP address - this was working fine until yesterday.

I am still getting alerts sent to my iPhone that was set up externally and so it seems to be logging in externally that is the problem?!?

On the iPhone it says timeout but via my mac it says no device found.

I spent so long googling to get it working it is so deflating to have it stop working. I have changed nothing except change the admin password on Tuesday and still worked for two days after that.

An open reach van was outside the house yesterday morning and that always worries me as one time they unplugged me completely but the internet, phone, and DVR internally all work fine and so I dont think it is anything to do with that.

So far all I have tried is to reboot the BT Home Hub5, reboot the ethernet bridge and reboot the DVR but still works internally and not from external.

If someone could save me another few weeks of stress and moans from the mrs for spending endless evenings googling a solution I would be so grateful. I am hoping that it is something really simple.

Thanks
Matt

BC AdBot (Login to Remove)

 


#2 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:03 AM

Posted 29 October 2016 - 09:27 AM

lets start with gathering a bit of info:

 

When connected to the bt hub can you ping the dvr?

What port(s) are you forwarding?

Did you assign a static ip to the dvr?

Post the results of a tracert yahoo.com via a command prompt for review



#3 mattcctv

mattcctv
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 AM

Posted 29 October 2016 - 10:40 AM

Thanks for responding Wand3r3r,

 

When connected to the bt hub can you ping the dvr?

Yes results are:

PING 192.168.1.100 (192.168.1.100): 56 data bytes

64 bytes from 192.168.1.100: icmp_seq=0 ttl=64 time=120.441 ms

64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=5.321 ms

64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=6.108 ms

64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=4.552 ms

64 bytes from 192.168.1.100: icmp_seq=4 ttl=64 time=5.173 ms

64 bytes from 192.168.1.100: icmp_seq=5 ttl=64 time=3.393 ms

^C

--- 192.168.1.100 ping statistics ---

6 packets transmitted, 6 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 3.393/24.165/120.441/43.064 ms

 

If I ping my public static ip I get the following:

PING 83.133.38.71 (83.133.38.71): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

Request timeout for icmp_seq 10

Request timeout for icmp_seq 11

Request timeout for icmp_seq 12

^C

--- 83.133.38.71 ping statistics ---

14 packets transmitted, 0 packets received, 100.0% packet loss

 

 

What port(s) are you forwarding?

QVIS CCTV DVR 

Protocol = TCP

Port Range 37777-37779 translated to the same

 

 

Did you assign a static ip to the dvr?

Yes it is always 192.168.1.100

 

Post the results of a tracert yahoo.com via a command prompt for review

Is this what you mean?

 

traceroute yahoo.com

traceroute: Warning: yahoo.com has multiple addresses; using 98.138.253.109

traceroute to yahoo.com (98.138.253.109), 64 hops max, 52 byte packets

 1  btbusinesshub (192.168.1.254)  6.259 ms  1.777 ms  1.681 ms

 2  host81-130-224-1.in-addr.btopenworld.com (81.130.224.1)  10.977 ms  11.229 ms  11.429 ms

 3  213.120.178.141 (213.120.178.141)  11.468 ms  11.504 ms  11.110 ms

 4  213.120.177.98 (213.120.177.98)  13.016 ms  12.394 ms  11.934 ms

 5  217.41.168.37 (217.41.168.37)  11.704 ms  11.914 ms  12.019 ms

 6  217.41.168.107 (217.41.168.107)  12.679 ms  12.045 ms  12.615 ms

 7  109.159.249.110 (109.159.249.110)  12.661 ms

    109.159.249.122 (109.159.249.122)  13.098 ms

    acc1-10gige-0-2-0-6.l-far.21cn-ipp.bt.net (109.159.249.101)  11.824 ms

 8  core4-te0-12-0-18.faraday.ukcore.bt.net (109.159.249.17)  12.216 ms

    core4-te0-9-0-26.faraday.ukcore.bt.net (109.159.249.59)  11.975 ms

    core4-te0-0-0-26.faraday.ukcore.bt.net (109.159.249.57)  12.752 ms

 9  peer1-xe0-0-2.faraday.ukcore.bt.net (213.121.193.185)  12.701 ms

    peer1-xe-11-0-0.faraday.ukcore.bt.net (213.121.193.169)  12.941 ms

    213.121.193.195 (213.121.193.195)  12.584 ms

10  ae2.pat1.loz.yahoo.com (195.66.224.115)  12.456 ms  11.932 ms  13.551 ms

11  ae-0.pat2.loz.yahoo.com (66.196.68.135)  12.723 ms  12.822 ms

    ae-1.pat2.loz.yahoo.com (66.196.68.137)  12.940 ms

12  ae-8.pat1.dcp.yahoo.com (216.115.101.157)  90.672 ms  90.773 ms  90.788 ms

13  ae-4.pat1.che.yahoo.com (216.115.101.153)  110.283 ms

    ae-8.pat1.dcp.yahoo.com (216.115.101.157)  90.455 ms  90.607 ms

14  ae-4.pat1.che.yahoo.com (216.115.101.153)  109.420 ms  109.581 ms  109.227 ms

15  ae-7.pat2.nez.yahoo.com (216.115.104.126)  123.449 ms  126.563 ms

    ae-5.pat1.nez.yahoo.com (216.115.96.76)  119.008 ms

16  et-0-0-0.msr2.ne1.yahoo.com (216.115.105.179)  121.250 ms

    et-1-0-0.msr1.ne1.yahoo.com (216.115.105.29)  121.180 ms

    et-19-1-0.msr1.ne1.yahoo.com (216.115.105.27)  122.516 ms

17  et-19-1-0.clr1-a-gdc.ne1.yahoo.com (98.138.97.71)  118.432 ms

    et-17-1.fab2-1-gdc.ne1.yahoo.com (98.138.0.81)  117.016 ms

    et-19-1-0.clr1-a-gdc.ne1.yahoo.com (98.138.97.71)  117.352 ms

18  po-12.bas1-7-prd.ne1.yahoo.com (98.138.240.10)  123.346 ms

    et-18-25.fab6-1-gdc.ne1.yahoo.com (98.138.93.7)  116.980 ms

    po-11.bas1-7-prd.ne1.yahoo.com (98.138.240.8)  121.885 ms

19  * po-16.bas2-7-prd.ne1.yahoo.com (98.138.240.34)  122.048 ms

    po-10.bas1-7-prd.ne1.yahoo.com (98.138.240.6)  116.773 ms

20  * * *

21  * * *

22  * * *

23  * * *

24  * * *

25  * *^C

 

Not sure if i have answered correctly as i know very little about networking but hope it helps

 

Thanks

Matt



#4 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:03 AM

Posted 30 October 2016 - 12:11 AM

Was this test from the mac?

 

Your public ip does not appear to be 83.133.38.71 but 81.130.224.1

 from the 2nd hop in the tracert which is why the ping test failed



#5 mattcctv

mattcctv
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 AM

Posted 30 October 2016 - 04:39 AM

Thanks for reply

Yes this was from the mac.

I have just ran a what is my ip from my iphone and it says

Real IP 81.133.38.71
host81.133.38.71.in-addr.btopenworld.com
Real IPshows the ip you appear with on the internet

But I tried another trace and it again says
Warning: bbc.co.uk has multiple addresses; using 212.58.244.22
traceroute to bbc.co.uk (212.58.244.22) , 5 relative hops max, 52 byte packets
1 btbusinesshub.home (192.168.1.254) 2.483 ms 5.600 ms 7.898 ms
2 host81-130-224-1.in-addr.btopenworld.com (81.130.224.1) 11.642 ms * *

So 81.130.224.1 is being used and I can ping this but I can not ping 81.130.38.71

Should I be able to ping my public facing static IP?

#6 mattcctv

mattcctv
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 AM

Posted 30 October 2016 - 04:50 AM

Aslo I tried changing the ip address in the cctv app from 81.130.38.71 (my public facing static IP) to 81.130.224.1 (the IP address showing in the reace route) but this did not work. The idmss app came back instantly whereas with 81.130.38.71 it tries for 3 seconds before timeout. If I try and view from my mac on pss mini it says host unknown.

#7 mattcctv

mattcctv
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 AM

Posted 30 October 2016 - 07:04 AM

I have just checked and 81.130.224.1 (the IP address showing in the trace route) is my default gateway

 

 

TCP/IP settings
Broadband network IP address: 81.133.38.71   Default gateway: 81.130.224.1        

#8 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:03 AM

Posted 30 October 2016 - 11:07 AM

You would never assign a public ip to your internal lan device like your DVR.  Leave it at a static ip of 192.168.1.100.  Any other address will make forwarding fail since forwarding is only to 192.168.1.100

 

"Should I be able to ping my public facing static IP?"

Yes unless icmp response is disabled in the router

 

I can ping both addresses so that's not the issue.

 

Did you get a phone update? Install something on your phone?  I am assuming this is the access that stopped working.



#9 mattcctv

mattcctv
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 AM

Posted 30 October 2016 - 01:02 PM

No iphone update. External CCTV access via 81.133.38.71was working from last Sunday until about Thursday lunch and it was working from three places:
1. My iphone via iDMSS PLUS app
2. My wife iphone via iAppollo app
3. My macbook via PSSmini

Then it stopped on all of them while we were out for the day and I had changed nothing. The only thing that could have changed is if BT do auto updates on the BT Business Hub5 without telling the customers or if the openeeach van that was mwssing with cables under the pavement on Thursday morning did something but my internet works fine so I really dont know.

#10 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:03 AM

Posted 30 October 2016 - 01:10 PM

Key to what you posted was the mac not being able to access.  That takes internet/forwarding out of the equation.

 

Mac was connected to the bt hub when you did your test?

 

If you connect the mac to the extender wired can it see the DVR?



#11 mattcctv

mattcctv
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 AM

Posted 30 October 2016 - 01:38 PM

Yes mac was wi fi connected ro BT hub.

Mac has no ethernet and so I will get my old windows laptop out and try it connected by wire later.

Funny thing is I have push notifications setup in iDMSS app on the external sevice setup and everytime a motion is detected I get an alert from the DVR saying:

External CCTV
Channel X
VideoMotion
Date and time etc

and so the DVR can write to my iphone when I am outside my network but I cant go back the other way to view the DVR.

#12 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:03 AM

Posted 30 October 2016 - 03:00 PM

Please post a pic of the bt hubs forwarding page

 

via the mac if you go to portforward.com and use the port test tool does the 37777-37779  show as open?


Edited by Wand3r3r, 30 October 2016 - 03:01 PM.


#13 mattcctv

mattcctv
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 AM

Posted 30 October 2016 - 03:34 PM

Screen_Shot_2016_10_30_at_20_23_11.png

 

Screen_Shot_2016_10_30_at_20_23_29.png



#14 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:03 AM

Posted 30 October 2016 - 03:57 PM

https://www.cctvaware.com/blog/qvis-dvr-port-forwarding-networking-details

 

it says the following

Port From 37777 Port To 37779 Protocol BOTH(TCP/UDP)

 

So add udp in the port forward

 

This assumes you have this unit

QVIS i-Series/DAHUA DVRs



#15 mattcctv

mattcctv
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 AM

Posted 30 October 2016 - 03:58 PM

 aha I could not find the port test on port forward.com but on

 

Port check – Tests if port is opened on specified IP   IP address or host name:  Port number:   
81.133.38.71:37777 port is closed

 

 

IP address or host name:  Port number:   
81.133.38.71:37778 port is closed
 
 
 
22_port.gif Port check – Tests if port is opened on specified IP   IP address or host name:  Port number:   
81.133.38.71:37779 port is closed
 
 
 

I also tested on http://www.canyouseeme.org

 

Error: I could not see your service on 81.133.38.71 on port (37777)

Reason: Connection timed out

Your IP: 
Port to Check: 
 
Check Port

 

I am assuming that this is the reason and I need to do something to open my ports?


aha we posted at same time - I will try what you said and get back

 

Thanks

Matt






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users