Unable to ping IP on another interface

AlohaSpark · Tue Aug 29, 2023 11:13 pm

Hello,

I have set up static IPs on my Mikrotik hEX, set up a DHCP server, and connected my laptop. All is well. My laptop can ping other devices on the LAN (192.168.1.3, etc.) as well as the MT itself (192.168.1.1).

However, when I add an IP address on another interface, the laptop cannot ping that (in this case, cannot ping 169.254.101.2).

Am I missing something? The MT is freshly reset, and there are no firewall rules, etc. I expected it to just work.

  ┌────────────────────┐                        ┌─────────────────────────────┐
  │Laptop              │                        │ Mikrotik                    │
  │ DHCP On            │LAN Port                │  All static IPs             │
  │ IP: 192.168.1.2/29 │◄──────────────────────►│                             │
  │ GW: 192.168.1.1/29 │                 ether2 │  ether2: 192.168.1.1/29     │
  │                    │                        │                             │
  └────────────────────┘                        │  ether3: 169.254.101.2/30   │
                                                │                             │
                                                └─────────────────────────────┘

The routing table on the MikroTik is as one might expect for this configuration.

[admin@MikroTik] > /ip/route/print
Flags: D - DYNAMIC; A - ACTIVE; c - CONNECT, s - STATIC, o - OSPF
Columns: DST-ADDRESS, GATEWAY, DISTANCE
#     DST-ADDRESS         GATEWAY                      DISTANCE
  DAc 192.168.1.1/29      ether2                       0
  DAc 169.254.101.0/30    ether3                       0
[admin@MikroTik] >

ConradPino · Wed Aug 30, 2023 12:28 am

I don't buy the ether2 route table entry:

DAc 192.168.1.1/29      ether2                       0

I expect it to look like:

DAc 192.168.1.0/29      ether2                       0

Take a look at corresponding

/ip address add network=

ConradPino · Wed Aug 30, 2023 12:32 am

RouterOS CHR 7.11 example:

/ip address print
Columns: ADDRESS, NETWORK, INTERFACE
# ADDRESS           NETWORK       INTERFACE
0 192.168.45.1/24   192.168.45.0  brcont
1 192.168.41.15/24  192.168.41.0  bridge
2 192.168.40.15/24  192.168.40.0  ether2
3 192.168.44.15/24  192.168.44.0  ether3
4 192.168.42.15/24  192.168.42.0  ether4
5 192.168.43.15/24  192.168.43.0  ether5

/ip route print
Flags: D - DYNAMIC; A - ACTIVE; c - CONNECT, s - STATIC
Columns: DST-ADDRESS, GATEWAY, DISTANCE
#     DST-ADDRESS      GATEWAY       DISTANCE
0  As 0.0.0.0/0        192.168.41.1         1
  DAc 192.168.40.0/24  ether2               0
  DAc 192.168.41.0/24  bridge               0
  DAc 192.168.42.0/24  ether4               0
  DAc 192.168.43.0/24  ether5               0
  DAc 192.168.44.0/24  ether3               0
  DAc 192.168.45.0/24  brcont               0

AlohaSpark · Wed Aug 30, 2023 7:08 am

I don't buy the ether2 route table entry:
Code: Select all
DAc 192.168.1.1/29      ether2                       0
I expect it to look like:
Code: Select all
DAc 192.168.1.0/29      ether2                       0
Take a look at corresponding
Code: Select all
/ip address add network=

All good now. I manually edited the entries for privacy; this is related to this other post: viewtopic.php?t=199073

Secondly, I found the problem. There were nothing wrong with the MT config. It was that Windows (I tested only on a laptop before) did not play nicely with 169.254.*.* addresses.

Replacing all 169.254 addresses solved all issues, including the other post.

Unable to ping IP on another interface [SOLVED]

Unable to ping IP on another interface

Re: Unable to ping IP on another interface

Re: Unable to ping IP on another interface

Re: Unable to ping IP on another interface [SOLVED]

Who is online