Webpages with 192.* ipv4 address is unreachable form deco m5 deco network

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Webpages with 192.* ipv4 address is unreachable form deco m5 deco network

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
2020-06-18 13:24:29
Model: Deco M5  
Hardware Version: V1
Firmware Version: 1.4.4 Build 20200221

Following problem on my deco network.

Configuration is -

Modem LTE Huawei B720 in Bridge Mode is connected to the main deco via ethernet cable and the other 2 deco devices are connected via wifi to the main.

Main has Internet Dynamic IP DNS 8.8.8.8 and 8.8.4.4 and lan network 192.168.0.1 Subnet 255.255.255.0 DNS 192.168.0.130 (pihole) and 8.8.8.8

The strange thing is when I try to access webpage with ip in 192.* range eg. ww.obi.at which show on nslookup the following IP

Name:    cs757.wac.phicdn.net
Address:  192.229.133.143
Aliases:  www.obi.at

I receive timeout and no webpage is shown.

Same for address www.pi-hole.net which is

Name:    pi-hole.net
Address:  192.124.249.118
Aliases:  www.pi-hole.net

I do not know which pages else got this problem but these two I've recognized and common to this pages is that they both show 192.* address on nslookup entry.

If I put the modem from bridge to normal mode or the accessing device gets connected to the internet through an vpn then everthing works without any problems.

I thihk that the problem raised with the upgrade of the deco firmware to 1.4.4 but I'm not quite sure.

Any suggestions how to fix this issue.

thank you

best regards

Andi O.

 

 

  0      
  0      
#1
Options
8 Reply
Re:Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
2020-06-18 13:38:31
traceroute the 192.229.133.143 and the 192.124.249.118, check the path. you've changed the deco lan network to 192.168.0.x ?
  0  
  0  
#2
Options
Re:Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
2020-06-18 14:12:50

@Peli 

the tracert stops after the main deco device

C:\Users\Axxxx>tracert www.obi.at

Routenverfolgung zu cs757.wac.phicdn.net [192.229.133.143]
über maximal 30 Hops:

  1     1 ms     1 ms    <1 ms  192.168.0.1
  2     *        *        *     Zeitüberschreitung der Anforderung.
  3     *        *        *     Zeitüberschreitung der Anforderung.
  4     *        *        *     Zeitüberschreitung der Anforderung.
  5     *        *        *     Zeitüberschreitung der Anforderung.
  6  ^C
C:\Users\Axxxx>

 

 

  0  
  0  
#3
Options
Re:Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
2020-06-18 14:16:38
What's the public ip of the main deco ?
  0  
  0  
#4
Options
Re:Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
2020-06-18 15:10:06

@Peli 

hello - I've made a big mistake and now removed the maindeco from the network and without any confirmation my whole network was deleted. I've now reconfigured the basics but is it possible to restore the settings (especially port forwardings and adress reservations) from any place ?

According to your question the public ip of the main deco is 77.717.147.235 in the moment. The requested adresses still do not work - although I've tried them with the basic settings of 192.168.68.1.

best regards

Andi O.

  0  
  0  
#5
Options
Re:Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
2020-06-18 15:13:51
it's not possible to restore the settings. Okay, try to open the obi webpage without the deco - connect your computer directly to your isp modem/router/bridge. If it's working without the deco - it's a firmware problem on the deco - if it's not working without the deco, than it's an ISP problem.
  0  
  0  
#6
Options
Re:Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
2020-06-18 15:19:01

@wrzosw1 

Do you have any firewall/antivirus on your computer ? Try to disable the whole antivirus thing, maybe that's what is blocking the access

  0  
  0  
#7
Options
Re:Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
2020-06-19 12:59:49

@Peli 

I've now changed the internet connection to my iphones hotspot and everythink works without any problems. I can exclude the influence of any virus scanner or firewall cause I've tested it on many different devices with different operating systems. 

I've found an old traceroute from a working connection (do not exactly know from which date)

This traceroute shows the lan adress of the bridged modem as the second hop. Thats strange for me - cause I've expected a bridge not to be visible.

C:\Users\AOswald>tracert www.obi.at

Routenverfolgung zu cs757.wac.phicdn.net [192.229.133.143]
über maximal 30 Hops:

  1     2 ms     2 ms     1 ms  192.168.0.1     - deco main device
  2     8 ms     3 ms     3 ms  192.168.8.1     - lan adress of the bridged modem ????
  3    38 ms   149 ms    27 ms  172.17.22.42
  4     *        *        *     Zeitüberschreitung der Anforderung.
  5    31 ms    23 ms    27 ms  213.94.72.88
  6    26 ms    19 ms    24 ms  ae-82.border1.vim.edgecastcdn.net [152.195.240.196]
  7    32 ms    27 ms    44 ms  ae-65.core1.via.edgecastcdn.net [152.195.240.129]
  8    41 ms    26 ms    32 ms  192.229.133.143

Ablaufverfolgung beendet.

 

This is the traceroute over the iphone connection from today:

C:\Users\AOswald>tracert www.obi.at

Routenverfolgung zu cs757.wac.phicdn.net [192.229.133.143]
über maximal 30 Hops:

  1     4 ms     4 ms     2 ms  172.20.10.1
  2    55 ms    37 ms    38 ms  172.20.162.37
  3    72 ms    36 ms    37 ms  172.17.8.96
  4     *        *        *     Zeitüberschreitung der Anforderung.
  5    25 ms    40 ms    36 ms  213.94.72.90
  6    54 ms    34 ms    33 ms  213.94.72.12
  7    57 ms    40 ms    33 ms  ae-82.border1.vim.edgecastcdn.net [152.195.240.196]
  8    77 ms   155 ms    45 ms  ae-65.core1.via.edgecastcdn.net [152.195.240.129]
  9    66 ms    35 ms    39 ms  192.229.133.143

Ablaufverfolgung beendet.

 

This are the IP settings:

C:\Users\AOswald>ipconfig /all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : EliteBookOSW
   Primäres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein

Drahtlos-LAN-Adapter WLAN 3:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8265 #2
   Physische Adresse . . . . . . . . : 00-28-F8-1E-BC-E8
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 172.20.10.4(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.240
   Lease erhalten. . . . . . . . . . : Freitag, 19. Juni 2020 14:38:24
   Lease läuft ab. . . . . . . . . . : Samstag, 20. Juni 2020 14:24:00
   Standardgateway . . . . . . . . . : 172.20.10.1
   DHCP-Server . . . . . . . . . . . : 172.20.10.1
   DNS-Server  . . . . . . . . . . . : 172.20.10.1
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

C:\Users\AOswald>

 

best regards

Andi O

  0  
  0  
#8
Options
Re:Webpages with 192.* ipv4 address is unreachable form deco m5 deco network
2020-08-25 20:17:27

@Peli 

 

hello - the problem still exists and it is very troublesome because I still recognize 3 problems.

1. I'm still unable to access the webpages with 192.* 

2. I'm unable to access the webui of my lte modem if the lancable from the modem to the deco wan port is connected although I try to access it over the wlan from the modem

3. I've recognized that the deco resetted to the default ip range 172.16.* after a reboot of the lte modem (I have to reboot once a day to control the renew of the ip adress)

 

So in the moment I'm not very happy with the mesh system. Any suggestions how to fix that ?

 

thank you

best regards

Andreas O.

 

 

  0  
  0  
#9
Options

Information

Helpful: 0

Views: 1342

Replies: 8

Related Articles