HS8145V - static routing works on router, not for connected device

Created: Sep 19, 2019 11:01:41Latest reply: Sep 23, 2019 08:55:13 163 6 0 0
  Rewarded Hi-coins: 5 (problem resolved)

I am trying to set up stating routing on HS8145V to allow for connections via another router (192.168.2.0/24 connected at 192.168.1.2 to HS8145V). I managed to set up stating routing using telnet ip route add . The routing table at the HS8145V looks as follows:

default dev ppp257 metric 10                                                                                          

185.238.204.1 dev ppp257 src 185.238.206.40                                                                           

192.168.1.0/24 dev br0 src 192.168.1.1                                                                                

192.168.2.0/24 via 192.168.1.2 dev br0 metric 10                                       

Pinging computers using HS8145V CLI works:

PING 192.168.2.1 (192.168.2.1): 56 data bytes                                                                          

64 bytes from 192.168.2.1: seq=0 ttl=64 time=1.144 ms                                                                  

But pinging or tracert'ing 192.168.2.0 network is impossible from a PC in 192.168.1.0 network. Oddly, the route leads to WAN IP, not br0 and 192.168.1.2 as written in the routing table.

Tracing route to 192.168.2.147 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1

  2     1 ms     1 ms     1 ms  185.238.204.1

  3  185.238.204.1  reports: Destination host unreachable.

 

Routing table at another router is:

ARP

Adress IPv4

Adress MAC

Interfejs

192.168.1.83

f4:d1:08:15:84:93

eth0.2

192.168.1.84

cc:52:af:49:90:93

eth0.2

192.168.1.10

58:e2:8f:90:44:d2

eth0.2

192.168.1.1

14:a0:f8:38:63:90

eth0.2

192.168.2.147

00:06:78:21:5a:8d

br-lan


Aktywne trasy routingu IPv4

Net

Target

Gateway IPv4

Metryka

Tablica

wan

0.0.0.0/0

192.168.1.1

0

main

wan

192.168.1.0/24

0

main

wan

192.168.1.1

0

main

lan

192.168.2.0/24

0

main


  • x
  • convention:

Featured Answers
liqiang185
Admin Created Sep 20, 2019 06:03:53 Helpful(0) Helpful(0)

The PC connected to the 192.168.1.0 cannot ping the PC at the bottom of the 192.168.2.0, This is because the 192.168.2.0 router performs NAT address translation. You can try to turn off this function, but if it is a home router, it cannot be turned off.
  • x
  • convention:

All Answers
liqiang185
liqiang185 Admin Created Sep 19, 2019 11:26:47 Helpful(0) Helpful(0)

Hello, the networking mode described by you is a non-standard networking scheme. Therefore, you cannot verify the feasibility of your plan. I suggest that your LAN port be connected to the user terminal and the WAN port be connected to the OLT.
  • x
  • convention:

MSz
MSz Created Sep 19, 2019 12:30:33 Helpful(0) Helpful(0)

Well, this is not exactly a "recommended answer" :)
On the Huawei router Lan port is connected to the user terminal (and the rest of the local network) and WAN is connected to OLT, which is pretty standard. Static routing is featured in the web configuration tool of the HS8145V.

Huawei router is considered WAN for the other router (routing table at the end), but my problem lies on the Huawei end.
  • x
  • convention:

liqiang185
liqiang185 Created Sep 20, 2019 06:13:23
If the problem occurs on Huawei routers, you can use a PC to directly connect to the VLAN interface of the HS8145V (replace the other router) and ping each other. If the ping succeeds, the device is normal. If the ping fails, check the settings.  
liqiang185
liqiang185 Admin Created Sep 20, 2019 06:03:53 Helpful(0) Helpful(0)

The PC connected to the 192.168.1.0 cannot ping the PC at the bottom of the 192.168.2.0, This is because the 192.168.2.0 router performs NAT address translation. You can try to turn off this function, but if it is a home router, it cannot be turned off.
  • x
  • convention:

MSz
MSz Created Sep 23, 2019 08:55:13 Helpful(0) Helpful(0)

This was super helpful. Double NAT was probably the issue.
The easiest answer for this simple network was to skip the forwarding rules altogether, kill DHCP on the other router, turning it into dumb access point. Everything works very well in one subnet now.
  • x
  • convention:

liqiang185
liqiang185 Created Sep 23, 2019 09:01:53
I hope we can communicate more, learn from each other, and make progress together  

Reply

Reply
You need to log in to reply to the post Login | Register

Notice Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!
Login and enjoy all the member benefits

Login and enjoy all the member benefits

Login