every other device on the network performs normally, it's just foxtel acting up.If you do a regular speed test on a laptop is there also a similar slowdown? Or is it only the Foxtel box?
the modem is in bridge mode, the telstra firmware is not that good and is too dumbed down, bridge mode is the best option.When the cable modem is plugged into the mik is it put in bridge mode or are you double NAT'ing. Nothing really jumped out at me in your config. I guess you've tried with and without the simple queue.
I have a CRS125-24G-1S-2HnD-IN that I could try this with. I'd imagine there would be a way to switch off the routing function with this?I guess the next thing I'd try in this situation is put a managed switch in between the modem and the routers and mirror the traffic to wireshark to look for any differences when it's working vs when it's not. Don't know if your comfortable at that low a level.
Eg: cable modem -> mirroring switch -> IQHD. And cable modem -> mirroring switch -> 951 -> IQHD.
Don't know if you have access a smart/managed switch or not, I'm not sure if the switch chip in your 951 could be used to mirror or not (might only be in the newer CRS devices) and I'd prefer switch hardware mirroring rather than a bridge+mangle sniff rules as you want to avoid the mikrotik cpu and any possible impact that might have on your bandwidth.
yeah this is a different device, the one I was using before was a RB951G-2HnD, but I setup a separate network with a CRS125-24G-1S-2HnD-IN and do all my testing on that, so I don't interrupt Internet connectivity for the rest of the family.Also, have you changed the router config to get 192.168.55.0/24 instead of 192.168.88.0/24? MAC looks different from bridge MAC in your config rsc posted earlier. Is this routerboard a different device?
I can get 2 public IPs from the modem for each of these networks, so no double NAT'ingAre you not getting a public IP on the routerboard and double NAT'ing?
"bridge mode modem" --> "mirror port" --> "mikrotik device" --> IQHD,
"bridge mode modem" --> "mikrotik device" --> "mirror port" --> IQHD, or
[admin@MikroTik] > ip firewall connection tracking print
[admin@MikroTik] > ip settings print
queue interface set [find default-queue="only-hardware-queue"] queue=ethernet-default
I tried changing the queue size, from 1 to 100000, still no change.if you've now used two different mikrotik devices and get the same behaviour that would tend to suggest it's something with them. maybe queue size on the interfaces?
only happens on the IQHD, every other device loads the image it tests with in about 5 seconds.
this only happens for IQHD? if someone else does a speediest at the same time it works ok?
yep, the second.
I'm not a TCP guru, hopefully some of them can comment here, but as far as I can tell, both streams start off identically, and it's only once the TCP window fills up the first time (packet 172) that it all seems to fall over after that in congestion collapse.
Where did you capture the failing stream? Was it:or was it:Code: Select all"bridge mode modem" --> "mirror port" --> "mikrotik device" --> IQHD,
I'm guessing the second?Code: Select all"bridge mode modem" --> "mikrotik device" --> "mirror port" --> IQHD, or
I'll get you these a bit later on tonight.What do you have for:and:Code: Select all[admin@MikroTik] > ip firewall connection tracking print
Assuming these will be factory default settings.Code: Select all[admin@MikroTik] > ip settings print
I've tried this, and every other queue, even a custom queue with a length of 1-100000 packets. it makes no difference.This might also be a bit of a long shot, but what happens to the speed test if you change the interface queue type of the ethernet ports?Code: Select allqueue interface set [find default-queue="only-hardware-queue"] queue=ethernet-default
OK.What do you have for:and:Code: Select all[admin@MikroTik] > ip firewall connection tracking print
Assuming these will be factory default settings.Code: Select all[admin@MikroTik] > ip settings print
[admin@MikroTik] > ip settings print
ip-forward: yes
send-redirects: yes
accept-source-route: no
accept-redirects: no
secure-redirects: yes
rp-filter: no
tcp-syncookies: no
max-arp-entries: 8192
arp-timeout: 30s
icmp-rate-limit: 10
icmp-rate-mask: 0x1818
route-cache: yes
allow-fast-path: yes
ipv4-fast-path-active: no
ipv4-fast-path-packets: 0
ipv4-fast-path-bytes: 0
ipv4-fasttrack-active: no
ipv4-fasttrack-packets: 0
ipv4-fasttrack-bytes: 0
[admin@MikroTik] >
[admin@MikroTik] > ip firewall connection tracking print
enabled: auto
tcp-syn-sent-timeout: 5s
tcp-syn-received-timeout: 5s
tcp-established-timeout: 1d
tcp-fin-wait-timeout: 10s
tcp-close-wait-timeout: 10s
tcp-last-ack-timeout: 10s
tcp-time-wait-timeout: 10s
tcp-close-timeout: 10s
tcp-max-retrans-timeout: 5m
tcp-unacked-timeout: 5m
udp-timeout: 10s
udp-stream-timeout: 3m
icmp-timeout: 10s
generic-timeout: 10m
max-entries: 218040
total-entries: 5
[admin@MikroTik] >
/ip firewall mangle
add action=change-mss chain=forward comment="MSS 1300 to foxtel 1" \
dst-address=192.168.88.11 new-mss=1300 protocol=tcp tcp-flags=syn \
tcp-mss=1301-65535
add action=change-mss chain=forward comment="MSS 1300 from foxtel 1" \
new-mss=1300 protocol=tcp src-address=192.168.88.11 tcp-flags=syn \
tcp-mss=1301-65535
add action=change-mss chain=forward comment=\
"Change MSS on WAN connection from foxtel 1" new-mss=1400 out-interface=\
ether1-gateway protocol=tcp src-address=192.168.88.11 tcp-flags=syn \
tcp-mss=1401-65535
add action=change-mss chain=forward comment=\
"Change MSS on WAN connection to foxtel 1" dst-address=192.168.88.11 \
in-interface=ether1-gateway new-mss=1400 protocol=tcp tcp-flags=syn \
tcp-mss=1401-65535