I am looking for a little bit of best practise advise; we are in the process of setting up a small Wireless ISP here in the UK and we have a bit of a challenge in the we are unable to get a EoFTTC connection…so what I have is this.
CHR in a UK data centre with a /27…and IPIP link to our FTTC connection which just has a /32, the /27 is then routed over the IPIP link and distributed to wireless clients, thus giving them a public IP address from our CHR in the datacentre and all is working nicely in terms of routing - I am however getting an additional 20 - 25ms of latency on this link and as such, impacting on TCP speed tests, which unfortunately customers think is the beall and endall
Is there any better way of doing this? Ideally I want to give all customers a public IP address and not NAT behind the connection
FTTC is closet to my remote clients yes and the datacentre is else where, ping to DC from the FTTC is 22ms over the IPIP is 25ms, which is fair but not great; definitely not CPU capped, the one in DC is a CHR and CPU is barely getting to 3% and the other is CCR1009 and max cpu is around 10%
So a net gain of 3 ms? Doesn’t seem to be the culprit if that’s the case. How is your MTU set along the path from the customer to the remote datacenter? Are you downstream to your customers at 1500 even after the IPIP tunnel?
We currently have MTU in the network set to 1500 and then 1480 on the PPPoE to the end client.
I suspect this is where some of my issue arrises, but I dont fully understand MTU at this time and currently researching, any help would be much appreciated