Wireless Wire Connectivity issues from device itself

RouterOS Beginner Basics
1

Hi everyone,

hope I am in the right subforum for my question ... I am using a Wireless Wire link with two RBwAPG-60ad devices over a 50 meter distance and I am basically very happy with it, link is rock stable, I get full gigabit speed over it. One kinda small annoying issue from the beginning was that when trying to check for updates on the "inner" device, meaning the one residing at my house connected to my internal network, always had issues connecting to the update servers, checking for updates etc. It always take multiple tries till it works. The device on the other end of the wireless link, which sits behind my internet router via ethernet has no issues at all checking for and downloading updates. Alright, here is my setup first again to give you a brief understanding:

Internal network (10.0.187.0/24) -> ethernet -> RBwAPG-60ad #1 (static 10.0.187.220) -> wireless bridge -> RBwAPG-60ad #2 (static 10.0.187.221)-> Internet Router (AVM Fritz Box 6490, 10.0.187.1) -> Internet

I didn't change any of the default config the devices came with, except for the IP configuration, gave them static iPs, set my DNS servers etc. See the console outputs at the end of the post ...

Digging somewhat deeper, I tried pinging adresses from the consoles logged in via SSH. What I see is, that on both devices, I have trouble pinging devices "behind" the other side of the bridge.
Meaning, from device #1 I can hardly ping anything behind device #2, sometimes I get a few ping replies, e.g. trying to ping my router (10.0.187.1), but then it starts timing out. Same if I try to ping hosts or IP addresses on the internet from device #1. Pinging devices on my internal network (10.0.187.0/24) works without issues from device #1.

Same situation when I try this from device #2 ... pinging my router or hosts on the internet seems to work perfectly fine, but when I try to ping device #1 itself or hosts on my internal network (anyting behind device #1) results in the same odd behaviour, I might get a few replies, but then it starts timing out.

Is there anything I need to add to the standard routing config, or the IP firewalling config to correct this, meaning full network connectivity FROM the devices themselves. I think if I achieve that, my update check issues from the web interface would be gone as well.

Thanks for any advice


RBwAPG-60ad #1

[admin@mtik1] > ip address print detail
Flags: X - disabled, I - invalid, D - dynamic
0 address=10.0.187.220/24 network=10.0.187.0 interface=ether1 actual-interface=bridge

[admin@mtik1] > ip dns print
servers: 10.0.187.248,10.0.187.1,8.8.8.8
dynamic-servers:
allow-remote-requests: no
max-udp-packet-size: 4096
query-server-timeout: 2s
query-total-timeout: 10s
max-concurrent-queries: 100
max-concurrent-tcp-sessions: 20
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 19KiB

[admin@mtik1] > ip route print detail
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
0 A S dst-address=0.0.0.0/0 gateway=10.0.187.1 gateway-status=10.0.187.1 reachable via bridge distance=1 scope=30 target-scope=10

1 ADC dst-address=10.0.187.0/24 pref-src=10.0.187.220 gateway=bridge gateway-status=bridge reachable distance=0 scope=10

Alright here is the config for the second device:
RBwAPG-60ad #2

[admin@mtik2] > ip address print detail
Flags: X - disabled, I - invalid, D - dynamic
0 address=10.0.187.221/24 network=10.0.187.0 interface=ether1 actual-interface=bridge

[admin@mtik2] > ip dns print
servers: 8.8.8.8,10.0.187.1,10.0.187.248
dynamic-servers:
allow-remote-requests: no
max-udp-packet-size: 4096
query-server-timeout: 2s
query-total-timeout: 10s
max-concurrent-queries: 100
max-concurrent-tcp-sessions: 20
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 19KiB

[admin@mtik2] > ip route print detail
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
0 A S dst-address=0.0.0.0/0 gateway=10.0.187.1 gateway-status=10.0.187.1 reachable via bridge distance=1 scope=30 target-scope=10

1 ADC dst-address=10.0.187.0/24 pref-src=10.0.187.221 gateway=bridge gateway-status=bridge reachable distance=0 scope=10

2

No one here that can offer any thoughts on this? If this is the wrong subforum could some admin please move this topic?

Thanks, boba

3

sorry no idea

4

So why exactly did you reply to this particular 20 day old thread to add that gem of uselessness?
At least you didn’t post any spam links this time.

5

Hi, I have a similar setup but it works great. Maybe you can post the output of the following command between [ CODE ] [ /CODE ] tags.

 /export hide-sensitive
6

Sorry for the late reply, but I’ve been kinda busy.

I got the issue resolved. I found in the forum that the “Detect internet” functions may cause problems like that, and in fact … that did the trick. I took a look at the configuration of the interfaces, which are WAN, LAN etc. set them according to my logical understanding, only set those interfaces “facing” that should be able to connect to the internet as those that are relevant for internet detection, and voila my issues are gone permanently.

So anybody else experiencing something like this, check your “detect internet” setup …

Take care,

boba