Community discussions

MikroTik App
 
brilthor
just joined
Topic Author
Posts: 5
Joined: Tue Aug 27, 2019 7:00 pm

CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Tue Aug 27, 2019 7:26 pm

Hi,

This is the first problem I've run into where searching and testing have not been able to solve it. So time to create a forum account...

The scenario: having configured a CRS125-24G-1S [running versions 6.45.3 (firmware) 6.45.3 (packages)] following https://wiki.mikrotik.com/wiki/Manual:C ... ith_Trunks and https://wiki.mikrotik.com/wiki/Manual:C ... s_examples I noticed very poor performance to devices attached to access ports (in this case 1-6). As a step in debugging I put a sniffer inline between the port and the device I was trying to access and got the following dumps (examples, timestamps might not line up exactly).
15:02:59.766778 IP 10.250.15.100 > 10.250.2.151: ICMP echo request, id 58486, seq 1868, length 64
15:02:59.767019 IP 10.250.2.151 > 10.250.15.100: ICMP echo reply, id 58486, seq 1868, length 64
15:03:00.783420 IP 10.250.15.100 > 10.250.2.151: ICMP echo request, id 58486, seq 1869, length 64
15:03:00.783667 IP 10.250.2.151 > 10.250.15.100: ICMP echo reply, id 58486, seq 1869, length 64
15:03:01.618009 IP 10.250.2.151.443 > 10.250.15.100.40260: Flags [.], seq 138:1598, ack 1136, win 4074, length 1460
15:03:01.618601 IP 10.250.15.100.40260 > 10.250.2.151.443: Flags [.], ack 1598, win 501, length 0
15:03:01.618900 IP 10.250.2.151.443 > 10.250.15.100.40260: Flags [.], seq 3058:4518, ack 1136, win 4074, length 1460
15:03:01.619099 IP 10.250.2.151.443 > 10.250.15.100.40260: Flags [P.], seq 4518:4650, ack 1136, win 4074, length 132
15:03:01.619143 IP 10.250.2.151.443 > 10.250.15.100.40260: Flags [F.], seq 4650, ack 1136, win 4074, length 0
15:03:01.619473 IP 10.250.15.100.40260 > 10.250.2.151.443: Flags [.], ack 1598, win 501, options [nop,nop,sack 1 {4650:4651}], length 0
15:03:01.619781 IP 10.250.2.151.443 > 10.250.15.100.40260: Flags [.], seq 1598:3058, ack 1136, win 4074, length 1460
15:03:01.619843 IP 10.250.2.151.443 > 10.250.15.100.40260: Flags [.], seq 3058:4518, ack 1136, win 4074, length 1460
15:03:01.619898 IP 10.250.2.151.443 > 10.250.15.100.40260: Flags [P.], seq 4518:4650, ack 1136, win 4074, length 132
15:03:01.620217 IP 10.250.15.100.40260 > 10.250.2.151.443: Flags [.], ack 3058, win 494, options [nop,nop,sack 1 {4650:4651}], length 0
15:03:01.620417 IP 10.250.15.100.40260 > 10.250.2.151.443: Flags [.], ack 4651, win 495, length 0
15:03:01.620551 IP 10.250.15.100.40260 > 10.250.2.151.443: Flags [F.], seq 1136, ack 4651, win 501, length 0
15:03:01.620757 IP 10.250.2.151.443 > 10.250.15.100.40260: Flags [.], ack 1137, win 4074, length 0
15:03:01.639097 IP 10.250.15.100.40280 > 10.250.2.151.443: Flags [S], seq 2242431770, win 64240, options [mss 1460,sackOK,TS val 805512331 ecr 0,nop,wscale 7], length 0
15:03:01.639323 IP 10.250.15.100.40282 > 10.250.2.151.443: Flags [S], seq 2511092398, win 64240, options [mss 1460,sackOK,TS val 805512332 ecr 0,nop,wscale 7], length 0
15:03:01.639357 IP 10.250.2.151.443 > 10.250.15.100.40280: Flags [S.], seq 298937959, ack 2242431771, win 5840, options [mss 1460,nop,nop,sackOK,nop,wscale 1], length 0
15:03:01.639523 IP 10.250.15.100.40284 > 10.250.2.151.443: Flags [S], seq 3369204088, win 64240, options [mss 1460,sackOK,TS val 805512332 ecr 0,nop,wscale 7], length 0
15:03:01.639542 IP 10.250.2.151.443 > 10.250.15.100.40282: Flags [S.], seq 302644790, ack 2511092399, win 5840, options [mss 1460,nop,nop,sackOK,nop,wscale 1], length 0
15:03:01.639677 IP 10.250.15.100.40280 > 10.250.2.151.443: Flags [.], ack 1, win 502, length 0
15:03:01.639757 IP 10.250.2.151.443 > 10.250.15.100.40284: Flags [S.], seq 293523206, ack 3369204089, win 5840, options [mss 1460,nop,nop,sackOK,nop,wscale 1], length 0
15:03:01.639814 IP 10.250.15.100.40282 > 10.250.2.151.443: Flags [.], ack 1, win 502, length 0
15:03:01.640104 IP 10.250.15.100.40284 > 10.250.2.151.443: Flags [.], ack 1, win 502, length 0
15:03:01.783401 IP 10.250.15.100 > 10.250.2.151: ICMP echo request, id 58486, seq 1870, length 64
15:03:01.783643 IP 10.250.2.151 > 10.250.15.100: ICMP echo reply, id 58486, seq 1870, length 64
15:03:02.806749 IP 10.250.15.100 > 10.250.2.151: ICMP echo request, id 58486, seq 1871, length 64
15:03:02.806987 IP 10.250.2.151 > 10.250.15.100: ICMP echo reply, id 58486, seq 1871, length 64
and at the same time also seeing
15:02:06.306721 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 575: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [P.], seq 0:517, ack 1, win 502, length 517
15:02:06.320055 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 575: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40148 > 10.250.2.151.443: Flags [P.], seq 0:517, ack 1, win 502, length 517
15:02:06.510098 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 575: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [P.], seq 0:517, ack 1, win 502, length 517
15:02:06.523914 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 575: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40148 > 10.250.2.151.443: Flags [P.], seq 0:517, ack 1, win 502, length 517
15:02:06.916732 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 575: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [P.], seq 0:517, ack 1, win 502, length 517
15:02:06.940033 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 575: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40148 > 10.250.2.151.443: Flags [P.], seq 0:517, ack 1, win 502, length 517
15:02:07.753921 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [.], ack 138, win 501, length 0
15:02:07.754119 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 109: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [P.], seq 517:568, ack 138, win 501, length 51
15:02:07.754365 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 509: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [P.], seq 568:1019, ack 138, win 501, length 451
15:02:07.766791 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 509: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [P.], seq 568:1019, ack 138, win 501, length 451
15:02:07.781233 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40148 > 10.250.2.151.443: Flags [.], ack 138, win 501, length 0
15:02:07.781488 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 109: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40148 > 10.250.2.151.443: Flags [P.], seq 517:568, ack 138, win 501, length 51
15:02:07.781707 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 549: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40148 > 10.250.2.151.443: Flags [P.], seq 568:1059, ack 138, win 501, length 491
15:02:07.793356 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 549: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40148 > 10.250.2.151.443: Flags [P.], seq 568:1059, ack 138, win 501, length 491
15:02:09.338971 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40132 > 10.250.2.151.443: Flags [.], ack 4619, win 501, length 0
15:02:09.422452 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [.], ack 1598, win 501, length 0
15:02:09.422464 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [.], ack 3058, win 495, length 0
15:02:09.423180 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [.], ack 5978, win 501, length 0
15:02:09.423363 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [.], ack 10358, win 479, length 0
15:02:09.437161 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40148 > 10.250.2.151.443: Flags [.], ack 1598, win 501, length 0
15:02:14.229096 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [.], ack 11818, win 501, length 0
15:02:14.229151 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [.], ack 13278, win 501, length 0
15:02:23.849161 4c:5e:0c:90:0a:41 > 0c:c4:7a:ad:b8:d2, ethertype 802.1Q (0x8100), length 64: vlan 2, p 0, ethertype IPv4, 10.250.15.100.40146 > 10.250.2.151.443: Flags [.], ack 16198, win 495, length 0


This is on a port which is supposed to be configured with no tagged traffic (equivalent to a vlan 2 PVID). Something of possible note here: I have never seen ICMP traffic in the tagged traffic

The configuration of the CRS follows:
/interface bridge
add admin-mac=4C:5E:0C:90:0A:41 auto-mac=no comment=defconf name=bridge protocol-mode=none
add name=system1
/interface vlan
add interface=bridge name=vlan2 vlan-id=2
add interface=bridge name=vlan3 vlan-id=3
add interface=bridge name=vlan10 vlan-id=10
add interface=bridge name=vlan15 vlan-id=15
add interface=bridge name=vlan20 vlan-id=20
add interface=bridge name=vlan4001 vlan-id=4001
/interface ethernet switch
set drop-if-invalid-or-src-port-not-member-of-vlan-on-ports=ether1,ether2,ether3,ether4,ether5,ether6
/interface ethernet switch trunk
add member-ports=ether23,ether24 name=3938trunk
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=ether6
add bridge=bridge comment=defconf interface=ether7
add bridge=bridge comment=defconf interface=ether8
add bridge=bridge comment=defconf interface=ether9
add bridge=bridge comment=defconf interface=ether10
add bridge=bridge comment=defconf interface=ether11
add bridge=bridge comment=defconf interface=ether12
add bridge=bridge comment=defconf interface=ether13
add bridge=bridge comment=defconf interface=ether14
add bridge=bridge comment=defconf interface=ether15
add bridge=bridge comment=defconf interface=ether16
add bridge=bridge comment=defconf interface=ether17
add bridge=bridge comment=defconf interface=ether18
add bridge=bridge comment=defconf interface=ether19
add bridge=bridge comment=defconf interface=ether20
add bridge=bridge comment=defconf interface=ether21
add bridge=bridge comment=defconf interface=ether22
add bridge=bridge comment=defconf interface=ether23
add bridge=bridge comment=defconf interface=ether24
add bridge=bridge comment=defconf interface=sfp1
/interface ethernet switch egress-vlan-tag
add tagged-ports=3938trunk,switch1-cpu vlan-id=2
add tagged-ports=3938trunk,switch1-cpu vlan-id=3
add tagged-ports=3938trunk,switch1-cpu vlan-id=10
add tagged-ports=3938trunk,switch1-cpu vlan-id=15
add tagged-ports=3938trunk,switch1-cpu vlan-id=20
add tagged-ports=3938trunk,switch1-cpu vlan-id=4001
/interface ethernet switch ingress-vlan-translation
add customer-vid=0 new-customer-vid=2 ports=ether1,ether2,ether3,ether4,ether5,ether6
add customer-vid=0 new-customer-vid=4001 ports=ether22
add customer-vid=0 new-customer-vid=10 ports=ether20,ether19
/interface ethernet switch vlan
add ports=3938trunk,ether1,ether2,ether3,ether4,ether5,ether6,ether22,switch1-cpu vlan-id=2
add ports=3938trunk,switch1-cpu vlan-id=3
add ports=3938trunk,ether19,ether20,switch1-cpu vlan-id=10
add ports=3938trunk,switch1-cpu vlan-id=15
add ports=3938trunk,switch1-cpu vlan-id=20
add comment="Cell Fallback" ports=3938trunk,ether22,switch1-cpu vlan-id=4001
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge network=192.168.88.0
add address=10.250.2.5 interface=vlan2 network=10.250.2.0
add address=10.250.3.12/24 interface=vlan3 network=10.250.3.0
add address=10.250.15.5 comment="ip for dhcp server" interface=vlan15 network=10.250.15.5
add address=10.250.10.5 comment="ip for dhcp server" interface=vlan10 network=10.250.10.5
add address=10.250.20.5 comment="ip for dhcp" interface=vlan20 network=10.250.20.5
add address=10.250.10.2 interface=vlan10 network=10.250.10.2
add address=10.250.10.3/24 interface=vlan10 network=10.250.10.0
add address=10.250.2.3/24 interface=vlan2 network=10.250.2.0
add address=10.250.15.2 comment="dns ip" interface=vlan15 network=10.250.15.2
add address=10.250.20.3/24 interface=vlan20 network=10.250.20.0

[admin@LinksCRS] > 

I'm unsure if this is a Mikrotik bug or if it's an outdated wiki page or if I've made an error here, help narrowing down those possibilities would be appreciated.
 
brilthor
just joined
Topic Author
Posts: 5
Joined: Tue Aug 27, 2019 7:00 pm

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Mon Sep 02, 2019 5:00 pm

Any input from Mikrotik Support on this?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11438
Joined: Thu Mar 03, 2016 10:23 pm

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Mon Sep 02, 2019 11:10 pm

Any input from Mikrotik Support on this?

If you really want to receive input from Mikrotik Support, then posting in this forum is not the best way. More likely you'll get some input if you sent the question to support@mikrotik.com ... and attach supout.rif, it'll contain complete device state and will help those guys to better understand what's going on.
 
Elliot
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Tue May 30, 2017 3:04 pm

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Mon Sep 02, 2019 11:13 pm

Hi friend,
first of all before anything you really need to study (2-3h max) about how switch chips in different Mikrotik works. You do VLAN on CRS125 like you would on CRS3xx series hence your poor performance. There's a manual how to do VLANs on CRS1xx/CRS2xx series.

link CRS1xx/CRS2xx https://wiki.mikrotik.com/wiki/Manual:C ... s_examples
Also you should listen to this VLAN processing presentation https://www.youtube.com/watch?v=ZMMpza-O7_w

If you have more questions after you understand how VLAN in Mikrotik works I will be more than happy to give you advice.
 
brilthor
just joined
Topic Author
Posts: 5
Joined: Tue Aug 27, 2019 7:00 pm

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Mon Sep 02, 2019 11:30 pm

Hi friend,
first of all before anything you really need to study (2-3h max) about how switch chips in different Mikrotik works. You do VLAN on CRS125 like you would on CRS3xx series hence your poor performance. There's a manual how to do VLANs on CRS1xx/CRS2xx series.

link CRS1xx/CRS2xx https://wiki.mikrotik.com/wiki/Manual:C ... s_examples
Also you should listen to this VLAN processing presentation https://www.youtube.com/watch?v=ZMMpza-O7_w

If you have more questions after you understand how VLAN in Mikrotik works I will be more than happy to give you advice.
Thanks for replying. You'll notice in my original post I mentioned the link that you have provided here as my source for example configuration. Could you point out what from the configuration you saw as being out of step with the 1xx series examples?
 
peson
Trainer
Trainer
Posts: 202
Joined: Tue Jul 20, 2004 10:33 am
Location: Sweden

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Wed Sep 25, 2019 10:02 am

Thanks for replying. You'll notice in my original post I mentioned the link that you have provided here as my source for example configuration. Could you point out what from the configuration you saw as being out of step with the 1xx series examples?
First, this switch chip is awesome in terms of configuration options, but needs lots of thinking and knowledge about it.
Looks like you only filtering ingress traffic to ports, not egress.
Check your /int eth swi port egress-vlan-mode=untagged, /int eth swi set forward-unknown-vlan=no.
You got some strange setting in the IP-address:
"add address=10.250.2.5 interface=vlan2 network=10.250.2.0 # 32-bit mask and subnet 10.250.2.0 this tells the routing table to find your subnet 10.250.2.0 via 10.250.2.5
"add address=10.250.2.3/24 interface=vlan2 network=10.250.2.0" # this looks better :-)
 
brilthor
just joined
Topic Author
Posts: 5
Joined: Tue Aug 27, 2019 7:00 pm

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Thu Oct 17, 2019 9:45 pm

Thanks for suggesting the
/int eth swi port egress-vlan-mode=untagged
for the interfaces and
/int eth swi set forward-unknown-vlan=no
for the switch

Unfortunately neither of these appear to have had any effect.

As far as the masking, I believe this is the correct way to configure IP Aliases with a mikrotik on subnets where there is already a primary address with submask configured.
 
peson
Trainer
Trainer
Posts: 202
Joined: Tue Jul 20, 2004 10:33 am
Location: Sweden

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Fri Oct 18, 2019 4:41 am

Thanks for suggesting the
/int eth swi port egress-vlan-mode=untagged
for the interfaces and
/int eth swi set forward-unknown-vlan=no
for the switch

Unfortunately neither of these appear to have had any effect.

As far as the masking, I believe this is the correct way to configure IP Aliases with a mikrotik on subnets where there is already a primary address with submask configured.
Please send the result of "/ip route print"
 
brilthor
just joined
Topic Author
Posts: 5
Joined: Tue Aug 27, 2019 7:00 pm

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Fri Oct 18, 2019 7:08 am

As requested:
...snip...
59 ADo  10.235.103.0/24                    10.250.3.10             110
60 ADo  10.235.254.0/24                    10.250.3.10             110
61 ADC  10.250.2.0/24      10.250.2.3      vlan2-management          0
62 ADC  10.250.2.13/32     10.250.2.13     vlan2-management          0
63 ADC  10.250.3.0/24      10.250.3.14     vlan3-interrouter         0
64 ADo  10.250.10.0/24                     10.250.3.12             110
...snip...
 
peson
Trainer
Trainer
Posts: 202
Joined: Tue Jul 20, 2004 10:33 am
Location: Sweden

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Fri Oct 18, 2019 8:27 am

As requested:
...snip...
59 ADo  10.235.103.0/24                    10.250.3.10             110
60 ADo  10.235.254.0/24                    10.250.3.10             110
61 ADC  10.250.2.0/24      10.250.2.3      vlan2-management          0
62 ADC  10.250.2.13/32     10.250.2.13     vlan2-management          0
63 ADC  10.250.3.0/24      10.250.3.14     vlan3-interrouter         0
64 ADo  10.250.10.0/24                     10.250.3.12             110
...snip...
Do you have a route to 10.250.15.0/24
 
peson
Trainer
Trainer
Posts: 202
Joined: Tue Jul 20, 2004 10:33 am
Location: Sweden

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Sat Oct 19, 2019 11:47 am

As requested:
...snip...
59 ADo  10.235.103.0/24                    10.250.3.10             110
60 ADo  10.235.254.0/24                    10.250.3.10             110
61 ADC  10.250.2.0/24      10.250.2.3      vlan2-management          0
62 ADC  10.250.2.13/32     10.250.2.13     vlan2-management          0
63 ADC  10.250.3.0/24      10.250.3.14     vlan3-interrouter         0
64 ADo  10.250.10.0/24                     10.250.3.12             110
...snip...
Do you have a route to 10.250.15.0/24
From your shared configuration, it doesn't look like you have any IP address for 10.250.15.0/24 subnet.
There is only 32-bit addresses.
 
Elliot
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Tue May 30, 2017 3:04 pm

Re: CRS125-24G-1S TCP (and other?) traffic exiting access port is sometimes tagged and sometimes not

Sun Oct 20, 2019 12:10 pm

As requested:
...snip...
59 ADo  10.235.103.0/24                    10.250.3.10             110
60 ADo  10.235.254.0/24                    10.250.3.10             110
61 ADC  10.250.2.0/24      10.250.2.3      vlan2-management          0
62 ADC  10.250.2.13/32     10.250.2.13     vlan2-management          0
63 ADC  10.250.3.0/24      10.250.3.14     vlan3-interrouter         0
64 ADo  10.250.10.0/24                     10.250.3.12             110
...snip...
I also may add why do you have OSFP running on a switch with CPU weaker than of that in Mikrotik hAP lite? Just set static default getaway and be done with it. This might hurt performance of the switch in your current configuration. Also it might be helpful to post a full export of your config here. cheers

Who is online

Users browsing this forum: fibracapi, FurfangosFrigyes, Google [Bot], hatred, hendry, Michiganbroadband, pajapatak, raiod, soulflyhigh and 74 guests