- This topic has 21 replies, 3 voices, and was last updated 6 years ago by
.
-
Posts
-
Yes, I manually set the DNS servers to 1.1.1.1 and 8.8.8.8 and used a cable to connect directly to the switch. It was when I went back to DHCP and power line it had a problem getting an IP address automatically.
I unplugged the power from the back of the box, counted to 10, then plugged it in again.
I too am sad I have given up on it, but this is my third attempt! I had an old T1000 that was very unreliable serving on demand, even on my old BT Homehub, and not at all with my new network set up. A couple of weeks ago, I replaced that with a new Humax Youview box, but that had all the problems I have been describing here as well, so I returned that and was determined to get this FVP 4000T working.
I’ve ordered a Panasonic DMR-PWT550EB Blu-Ray Player and HDD Recorder with Freeview Play. It has the benefit of me being able to reduce the number of boxes under the TV. It will be very interesting to see if it has similar issues. As I’m sure all these boxes probably share some open source software for networking it may not work either!
Well I finally got it to work. I used MTU checker to determine what MTU I was getting from BT Infinity. It showed a maximum MTU of 1484. I think this is lower than the default as the connection is PPPoE. Subtracting 40 bytes (20 bytes each for IP & TCP headers) I then set MSS clamping to 1444.
Bingo, it works. No idea why the Humax box needed this set, whereas nothing else did. The default setting for MSS clamping was “Auto”, so I suppose better behaved software worked with it on auto.
mcdonald_ajr – 2 hours ago »
Well I finally got it to work. I used MTU checker to determine what MTU I was getting from BT Infinity. It showed a maximum MTU of 1484. I think this is lower than the default as the connection is PPPoE. Subtracting 40 bytes (20 bytes each for IP & TCP headers) I then set MSS clamping to 1444.
Bingo, it works. No idea why the Humax box needed this set, whereas nothing else did.
Interesting observation, thank you.
Very interesting. My MTU size using the checker you quote is 1492. That value appears to be set in my Draytek 2862 router. My ISP is Plusnet. As a matter of interest, where did you set your MSS value – in the modem or your security gateway? This is a new and insightful diagnosis of this problem – which may help other users. I am (when time allows) going try my other routers (Sagem) to see whether I can discover more.
I set it in my Router (Unifi Security Gateway).
Here’s someone else with similar issues MTU
Quote:Well I finally got it to work. I used MTU checker to determine what MTU I was getting from BT Infinity. It showed a maximum MTU of 1484. I think this is lower than the default as the connection is PPPoE. Subtracting 40 bytes (20 bytes each for IP & TCP headers) I then set MSS clamping to 1444.Bingo, it works. No idea why the Humax box needed this set, whereas nothing else did.
I have run a wireshark trace of my FVP. Consistently, the HUMAX sends a SYN packet with MSS set at 1460. Now I don’t yet fully understand the details but I imagine that your diagnosis is consistent.
I suspect that there may be two different reasons why some find internet access troublesome. I can’t understand why clearing cookies would help with this MTU size problem.
Does anyone know what clearing cookies actually does?
- You must be logged in to reply to this topic.