@WKDRED
1. Not many UK ISPs offer DHCP instead of PPPoE. However if it's mtu you are concerned for, I know many openreach ISPs support baby jumbo frames, so you can still achieve 1500 MTU (with 8 extra bytes on top then for the ppp header). This is RFC6438, and it works with giganet alongside a Fritzbox I tried (where it has to be explicitly enabled). It does not work with the eero.
2. You can get a reduction on the install fee if you opt not to use their router. I think it's 25 or 30
3. There's a referral scheme (I am a customer so can happily offer a referral if you wish) whereby each party gets 25 back
4. The eero is 'interesting'. Let me come onto that in another post!
5. I don't see why you need a static ip to forward ports as such. The issue is how you refer to them. The ip address may change. You can use DDNS to mitigate this, though it's not something the eero supports. Other routers often do. You could run a client on another machine you have locally like a raspberry pi. Note that for IPv6 (which giganet supports) you may not even need port forwarding, though the naming issue may remain. I haven't asked how stable the IP prefixes seem to be, though they look stable. Nor have I looked into dns for my local ipv6 systems.
6. I share your confusion over contract. I would take a screenshot of the page sayin no exit fee just in case - it looks to me as if there's no contract but I've not tested this. A big reason I went with them is that cityfibre may be here any moment. We got BT fttp in Jan. Cityfibre. Who knows. April 2023? Sep? Jan 24? Never. Really can't tell. So I wanted flexibility, but also get a decent service now
My experience generally
- the network service has worked without any problems
- the eero had a few issues - see below
- call times to customer service seem to be getting worse. Hard to know if this is a blip
- when I did get sensible replies from level 2, they seemed helpful and eager to get things sorted -- but were clearly overloaded.
eero next