I’ve just noticed something unusual. One of my mate that is also on Yayzi and actually we are both on 213.18.200.0/21 is getting bandwidth limit when watching anything from my plex server, reason for that is that he cannot reach me directly, so plex is tunneling him, limiting his bandwidth to 2mb/s. I’ve tested a few more things and seems yes I cannot route to him either.
This has nothing to do with the migration, other than the fact that after we both landed on the same subnet. Now probably my router is trying to reach him and tries an ARP as is already is in the destionation subnet and that fails of course.
Just wondering if anyone in the yayzi team or the community have any ideas for a fix, other than routing throught a tailscale like network.
Yeah, we both have 213.18.200.1 as gateway and I presume everyone in here on that /21 subnet also do. When I trace him or he traces me we both get from our router Destination unreachable, that is why am thinking it tries to arp and that is blocked on the public subnet.
Only solution I can think so far is to hardcode his mac and IP but cannot do that on his side as he is running a tp-link OR ask Yayzi to move one of us in a diffrent subnet, lol.
Yeah makes sense if you are both in the same broadcast domain. Im not on that range so not sure how Yayzi manages it, if for example they slice the network up internally into smaller /24s to limit the size of the broadcast domain (or they block arp on the core network), but is still advertised as a /21 prefix externally.
Thanks for taking the time to read through it, I’ll do a bit more investigating, but never thought I would be in a situation when me and one of my mates to be on the same ISP subnet
I deleted my static autogenerated route and seems I am now getting to the gateway and further when trying to reach an IP in the same subnet. Only issue now is how do I do that on my mates router as he has an tplink EX820v, while i have an openwrt one which was easy.
route del -net 213.18.200.0 netmask 255.255.248.0 dev eth1.911
traceroute 213.18.204.[hidden]
traceroute to 213.18.204.[hidden] (213.18.204.[hidden]), 30 hops max, 60 byte packets
1 router.lan (192.168.2.1) 0.420 ms 0.358 ms 0.319 ms
2 213.18.200.1 (213.18.200.1) 3.133 ms 2.757 ms 3.378 ms
3 * * *
I have the same problem in the same Yazi 213.18.200.0/21 subnet. I have two sites with ip numbers in this subnet, both with pfsense routers which cannot traceroute to each other. Have Yayzi responded with any help? Your supposition that they have disabled ARP on their subnet does make sense.
They haven’t fixed it yet, no, meanwhile my mate moved over to another ISP anyway, Aquiss i believe. but you can try what i coulnd.t and remove -net 213.18.200.0 netmask 255.255.248.0 network off both ends. internet access will still work dont worry
I don’t have these static routes so there is nothing to delete. The Yayzi router at 213.18.200.1 is returned by DHCP. I am wondering whether a static route could be used to specify a diffferent router to route traffic between the two sites.
You sure you don’t have a route for 213.18.200.0/21 ? that should be autogenerated, never really used pfsense but can install it tomorrow and have a look. Similar like 198.51.100.0/24 in this example Route Table Contents | pfSense Documentation
When i deleted mine traffic was reaching the other end so you having pfsense on both ends might be able to get it working.
Seen your other post, VPN has nothing to do with it, is just reachability in the same subnet causing it to fail.
My other post is related to VPN because the routing problem means that VPN between the 2 sites doesn’t work. This is a problem for us because we have equipment at both sites which need to talk to each other. It was working fine until 21st January and has not worked at all since then. I can be precise about this because the system sends out a warning email if no data has been transferred. I can also see that the internet service was unavailable from one of the sites on the afternoon of the 21st January so probably Yayzi made some changes on that date. Also about that time, the ip numbers changed at both sites so that they were in the same subnet - prior to that one of the sites was in 213.18.200.0/21 but the other one was in a different subnet so presumably that was why the VPN worked until then.
I have looked at the pfsense routing tables. It creates a route automatically for 213.18.200.0/21 - not a static route. But you can’t delete it with “route delete”. It says “delete net 213.18.200.0 fib 0: gateway uses the same route”.
That was with cli. Not sure that pfsense has a concept of sudo. You log in as root via ssh and have all rights as far as I can see. /home is empty and all files seem to belong to root.
I shall email yayzi support asking them to sort their subnet out.
