Packet loss with Gigabox Bridged

hesker

Hi,

I have a VDSL 100mbps service from Vodafone which works really well. I recently got a new Gigabox router from vodafone as the old router was knackered.

I am trying to bridge the Gigabox to an Asus router. It seems fairly straight forward. Just put the gigabox in bridge mode and input the vodafone details into the Asus. All works well except I get packet loss which affects IP calls really badly.

If I ping the router it looks OK but pings to websites such as Google show 5-10% packet loss.

I have checked for double NAT using traceroute and it looks fine.

If I disconnect the ASUS and just use the Gigabox I get zero lost packets

Anyone got any ideas?

hesker

Vodafone tech support say they are not doing anything to prevent bridging so not a problem on their end.

nelly17

Duplex mismatch on the eth ports?

hesker

Not sure what you mean but I have no Ethernet cables attached. Just Lan port on Gigabox to WAN on ASUs.

ED E

How long is the run between the two?

hesker

About 1 meter

KildareP

What MTU have you set on your router?

hesker

Am away from home for the week so can’t check. Didn’t change it from the default and have installed the latest version of firmware. Router is a few years old. RT-AC87U

robbiep958

This might be completely irrelivent but if noticed a lot of packet loss on my own connection from vodafone at certain times for the past month!!

hesker

I get zero packet loss using the Vodafone router on it’s own. So it’s either some config or the Gigabox is not playing nice with the ASUs or else the ASUs is knackered.

alec76

If it is truly bridged then it’s ASUS fault.

hesker

Is there any way to prove it’s the Asus at fault. If I set up the Asus as an access point and still got packet loss would that prove it.

ondafly

Have you tried a different network cable ?

hesker

Yes. Tried different cable.

alec76

https://www.boards.ie/discussion/comment/118373704#Comment_118373704

I believe it is other way around, you have packet loss when Asus in router mode and you should be all right when Asus in AP mode.

ED E

Is the ASUS getting an IP in the same block as the Gigabox?

Try MTU of 1400. Shouldnt be this but test it just in case.

hesker

How would I tell that.

Asus is 192.168.1.1.

I can’t see what the Gigabox is assigned as far as I remember.

hesker

Back home now and tried an MTU of 1400. Initially I thought it had worked as I got zero packet loss on a couple of tests. I optimized the MTU as per this guide.

https://homenetworkadmin.com/what-is-mtu-size/

Coincidently this gave me a number of 1400 also.

Did a few more ping tests and I started getting 8-10% loss again.

PING www.google.com (74.125.193.104): 56 data bytes

64 bytes from 74.125.193.104: seq=0 ttl=113 time=8.213 ms

64 bytes from 74.125.193.104: seq=1 ttl=113 time=8.164 ms

64 bytes from 74.125.193.104: seq=2 ttl=113 time=8.450 ms

64 bytes from 74.125.193.104: seq=3 ttl=113 time=8.512 ms

64 bytes from 74.125.193.104: seq=4 ttl=113 time=8.070 ms

64 bytes from 74.125.193.104: seq=5 ttl=113 time=8.255 ms

64 bytes from 74.125.193.104: seq=6 ttl=113 time=7.984 ms

64 bytes from 74.125.193.104: seq=7 ttl=113 time=7.881 ms

64 bytes from 74.125.193.104: seq=8 ttl=113 time=7.949 ms

64 bytes from 74.125.193.104: seq=9 ttl=113 time=8.410 ms

64 bytes from 74.125.193.104: seq=10 ttl=113 time=8.285 ms

64 bytes from 74.125.193.104: seq=11 ttl=113 time=8.122 ms

64 bytes from 74.125.193.104: seq=12 ttl=113 time=8.276 ms

64 bytes from 74.125.193.104: seq=13 ttl=113 time=8.658 ms

64 bytes from 74.125.193.104: seq=14 ttl=113 time=8.459 ms

64 bytes from 74.125.193.104: seq=15 ttl=113 time=8.048 ms

64 bytes from 74.125.193.104: seq=16 ttl=113 time=8.218 ms

64 bytes from 74.125.193.104: seq=17 ttl=113 time=8.353 ms

64 bytes from 74.125.193.104: seq=18 ttl=113 time=8.441 ms

64 bytes from 74.125.193.104: seq=19 ttl=113 time=8.038 ms

64 bytes from 74.125.193.104: seq=20 ttl=113 time=8.436 ms

64 bytes from 74.125.193.104: seq=21 ttl=113 time=8.558 ms

64 bytes from 74.125.193.104: seq=22 ttl=113 time=8.207 ms

64 bytes from 74.125.193.104: seq=23 ttl=113 time=8.212 ms

64 bytes from 74.125.193.104: seq=28 ttl=113 time=8.292 ms

64 bytes from 74.125.193.104: seq=29 ttl=113 time=8.466 ms

64 bytes from 74.125.193.104: seq=30 ttl=113 time=8.356 ms

64 bytes from 74.125.193.104: seq=31 ttl=113 time=8.221 ms

64 bytes from 74.125.193.104: seq=32 ttl=113 time=8.260 ms

64 bytes from 74.125.193.104: seq=33 ttl=113 time=8.338 ms

64 bytes from 74.125.193.104: seq=34 ttl=113 time=8.179 ms

64 bytes from 74.125.193.104: seq=35 ttl=113 time=8.345 ms

64 bytes from 74.125.193.104: seq=36 ttl=113 time=8.454 ms

64 bytes from 74.125.193.104: seq=37 ttl=113 time=8.093 ms

64 bytes from 74.125.193.104: seq=38 ttl=113 time=8.206 ms

64 bytes from 74.125.193.104: seq=39 ttl=113 time=8.357 ms

64 bytes from 74.125.193.104: seq=40 ttl=113 time=8.407 ms

64 bytes from 74.125.193.104: seq=41 ttl=113 time=8.169 ms

64 bytes from 74.125.193.104: seq=42 ttl=113 time=8.448 ms

64 bytes from 74.125.193.104: seq=43 ttl=113 time=8.012 ms

64 bytes from 74.125.193.104: seq=44 ttl=113 time=9.400 ms

64 bytes from 74.125.193.104: seq=45 ttl=113 time=8.458 ms

64 bytes from 74.125.193.104: seq=46 ttl=113 time=8.328 ms

64 bytes from 74.125.193.104: seq=47 ttl=113 time=8.336 ms

64 bytes from 74.125.193.104: seq=48 ttl=113 time=9.040 ms

64 bytes from 74.125.193.104: seq=49 ttl=113 time=8.688 ms

--- www.google.com ping statistics ---

50 packets transmitted, 46 packets received, 8% packet loss

round-trip min/avg/max = 7.881/8.327/9.400 ms

smuggler.ie

https://www.boards.ie/discussion/comment/118377016#Comment_118377016

Try set Asus on something high (192.168.1.254, 192.168.1.253) on LAN and/or reservation for gigabox within DHCP to NOT 192.168.1.1

hesker

Did that. No difference

hesker

Well at last some major progress if not a root cause.

I have an old HG658c lying around so I took out the Gigabox and bridged the HG658c instead.

Here are the ping test results:

Ping Test 1:   50 to Google.com      Result: zero packet loss

Ping Test 2:   50 to Google.com      Result: zero packet loss

Ping Test 3:   50 to facebook.com      Result: zero packet loss

Ping Test 4:   50 to wikipedia.org      Result: zero packet loss

Ping Test 5:   99 to Google.com      Result: zero packet loss

Ping Test 6:   99 to facebook.com      Result: zero packet loss

Ping Test 7:   99 to wikipedia.org      Result: zero packet loss

Next step is to test an IP call. If that works it should be good enough for me.

hesker

Thanks to everyone for assistance. Have yet to test IP call. If I get the Gigabox bridging to work I’ll report back.

hesker

A test video call on Teams worked fine. No more than 0.3% packet loss using the Teams call health monitor.

ED E

Using the HG658c purely as a modem will be equivalent to the gigabox, so I'd stick with it.

Just be aware if it dies all new units will likely be a gigabox so fixing the issue might be of some value.

Glaceon

This is a known issue with the Gigabox alright. We had the exact same issue with a client in Dublin. One of our lads went to site and was able to replicate it by using a different modem which didn’t have the issue. When we contacted Vodafone, their account manager confirmed it and said he wasn’t allowed to provide us with an older model, but if we sourced a compatible VDSL modem ourselves they’d credit us for it. So we did and it has been fine since.

ED E

Knowing their CPE is dud and doing nothing, shouldnt really be surprised.

hesker

https://www.boards.ie/discussion/comment/118387142#Comment_118387142

Just out of interest how did their account manager confirm it. Because when I contacted them they said all was fine as far as they could see.

Glaceon

https://www.boards.ie/discussion/comment/118389945#Comment_118389945

This would have been a business account so maybe they had better support? The client put my colleague on to the account manager and when we explained the issue, he said that he knew about it.