Category Archives: Hardware

Manually flashing new firmware to Sagem Fast 3464 (bbox2)

Published by:


Yesterday I got a Sagem Fast 3464 modem that was in safe mode. It said “your cpe is now in rescue mode”. My mission was to have it download the latest firmware.

Normally the modem will download the latest firmware by itself when connected. But this one didn’t.

Another way to get it to update was to somehow provide it with a TFTP server with the correct files hosted. That implied listening to the modem with a packet sniffer and watch for it to try and make a connection to a pre-defined TFTP server. Like explained here:
But that didn’t work either, since the modem did not initiate any kind of traffic other than some IGMP packets. I guess these instructions only apply when a firmware was already present, and since this modem was in CPE rescue, it did not work as expected.

Important: If your modem is NOT in recue mode and it shows anything else than “your cpe is now in rescue mode” in your browser, then you need to flash the rescue mode firmware first. In that case, don’t continue, but instead follow the instructions here :…

I managed to connect using telnet (PUTTY) using the standard username/password. As it was an old modem, I used login:admin password:OLOVDSL2 ( Which is the non-belgacom password. If that doesn’t work for you try login:admin password:BGCVDSL2 )

This made it possible to instruct the modem to download the new firmware. But first we need a TFTP server that is hosting the firmware files. You can find one here.
I found a working firmware (60A06W Belgacom) here: direct link (source:… )
I configured the TFTP server to host the firmware (the setup is very basic).

These are the instructions I to use in the telnet session:

Change the IP adress to the one your TFTP server is running.

That’s it. Let it download and when finished reboot.
The modem should now have runtime code 6LR10A-60A06W.
Configure it by using a web-browser, and the serial number as a password.
Then let it sit for a while to complete the latest update by itself.

Hope this works for you.

Guild Wars 2 low fps slow performance on nVidia GTX 260

Published by:

When I first tried Guild Wars 2 on my AMD X4 PC equipped with a nVidia Geforce GTX 260, I was in for a shock. The game was unresponsive and slow, and no matter what settings or resolution I applied, the game didn’t give me more then 20 fps. In cities I only got 7 fps, with everything disabled or set to low.

I have been reading about this for a week now, and nothing came up. Until I saw something strange in GPU-Z. In the “interface” field it said PCI-E 2.0 x 16 @x4 1.1.
@x4 means it was running on 4 channels of the PCIe bus, while it should be using all 16…

Then I realized that I had plugged the videocard into the wrong PCI-E slot. My motherboard has two PCI-E slots as I came to learn, one x4 and one x16. Normally it is written beside the slot.

After I moved the GTX 260 from the x4 slot to the x16 slot , GPU-Z showed PCI-E 2.0 x 16 @x16 2.0 .

Guild Wars is now running at high settings at about 50 FPS and it’s running smooth as a cat.

So if you are having trouble getting a good performance in Guild Wars 2, check if your video-card is correctly installed.

BBox2 Sagem Blocked – NAT out failed First packet in connection is not a SYN packet (part 2)

Published by:

I have been experimenting again with the ” First packet in connection is not a SYN packet: TCP> on ppp0 ” error in my SAGEM F@ST router.

What I found was that the Sagem firewall and/or NAT throws this messages whenever tcp packets are fragmented and this has to do with the MTU (maximum transmission unit)

In short this means:
IP packets have a maximum load of 1500 bytes without fragmentation. If the load is bigger, the package will be split in multiple fragments that are transmitted separately. (fragmentation). When a PC (browser) communicates with a server, they agree on a maximum packet size (mtu) and that will be used for the remainder of the communication. Both your computer and server use the internal MTU and they don’t care about the MTU of devices and routes in between. Windows usually has a MTU of 1500, meaning it will squeeze every last bit in one packet. This is fine on a local LAN, without routers. But when the packet needs to be transmitted over PPPoE (ADSL), there is some additional 8 bytes of header-information that needs to be added, thus making the packet 1508 bytes, which is to big and will be fragmented. (learn more about this here)

Normally fragmentation is handled fine by routers in between, but the Sagem seems to mess things up.

What we need to do is lowering the MTU on the computer. This may avoid fragmentation and maybe with it this problem. To do that I used TCP/IP Optimizer 3 found here.

This program needs to run as Administrator. Put it on “Custom” (bottom right) and select you Network Adapter. Then set MTU to something like 1492 (or if you want to be absolutely safe 1460) and press Apply changes. Reboot.

If found that using a setting less then 1492 would reduce the “NAT out failed First packet” errors somewhat, but not completely. I still believe there is no real fix, unless there is a firmware upgrade (doubtful).

Please let me know in the comments what results you had.

Sagem error Only one WAN connection can be enslaved by each bridge : Resolved

Published by:

sgmSymptoms: You want to change IP settings, change IP address ( local Ip address, default ) but Sagem router returns a message: “Only one WAN connection can be enslaved by each bridge

Reason: Other VLAN interfaces are enabled and should be disabled when changing the LAN settings.

Solution: You do not need VLAN , so disable the VLAN circuits

– Go to advanced settings
– Choose Network Interfaces
– Click on LAN Bridge
– Click on settings (button)
– Disable the Wan ethoa0 … 12 ( disable everything exept LAN Ethernet en LAN Wireless – first and last ).


– Now you can change your LAN IP settings.
– Eventually return the state of the disabled interfaces ( only if required )

The Sagem 3464 is a (wireless) VDSL2 broadband internet router. It’s used by Belgacom, EDPNET, and maybe other providers using VDSL2 in Belgium.

Connect to the Sagem via a crossed UTP/STP cable into the Yellow port on the back of the unit (next to the power switch). The default IP is Alternatively connect both router and PC to a hub or switch. ( Mind the unit’s DHCP server is active by default. )