Sagem Modem
Prince Aboubakar
Background:
After replacing my very stable but not so fast Google Nest Mesh system with an Orbi RBK852 Mesh system, my internet connection suddenly became incredibly unstable. I contacted my internet provider, which is Denmark's largest, as I had not done anything else on my network other than replace my Google Mesh system with an Orbi system.
My internet provider was, as always, very helpful and took my issue very seriously. They began monitoring my cable modem and sent a technician to my address to ensure that I did not have noise on my coax cable. YouSee my internet provider, could not detect any faults on the coax cable, signal values, or their cable modem. Therefore, their clear conclusion was that the problem must be something on my network that caused their modem to go down.
As my internet provider seemed extremely confident in their assessment, there was not much else to do but begin troubleshooting my own installation. Since I was unable to find faults on my switches, patch cables, cross-connects, or other equipment, there was nothing else to do but start replacing my cables, switches etc.
The only thing I had yet to troubleshoot was my new router, which in hindsight I should have started with. It turned out that my problem was the Amor product, which I had of course activated during the setup of the Orbi system. As soon as I deactivated the Amor security solution, my internet connection was 100% stable again.
Now I am almost $2,200 poorer, but much wiser. So to all those who need a router with built-in security software and who use a Sagemcom Fast 3890V3 modem, I strongly recommend finding another solution.
Your ISP Modem already has a built in router and wifi. This would be a double NAT (two router) condition which isn't recommended. -is-Double-NAT
-to-fix-issues-with-Double-NAT
Couple of options,
1. Configure the modem for transparent bridge or modem only mode. Then use the Orbi router in router mode. You'll need to contact the ISP for help and information in regards to the modem being bridged correctly.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ/ExposedHost or IP Pass-Through for the IP address the Orbi router gets from the modem. Then you can use the Orbi router in Router mode.
3. Or disable all wifi radios on the modem and connect the Orbi router to the modem, configure AP mode on the Orbi router. -do-I-configure-my-Orbi-router-to-act-as-an-access-point and =H7LOcJ8GdDo&app=desktop
-features-are-disabled-on-my-Orbi-router-when-it-is-set-to-AP-...
It's a bit frustrating that one has chosen a router based on the security software that came with it, only to realize that it is the piece of software that is causing the biggest problem on the network.
What I prefer to do in your situation is to have the ISP put their device into bridge mode, which lets yours get teh public IP address. When I cannot do that, then I just put the WAN IP of MY device into the DMZ of THEIR device, and that lets all inbound traffic hit my device, including inbound VPN traffic.
thx for your Workaround suggestion to put the ASUS router IP address as a DMZ in the Sagemcom modem - I have done that. Even after designating DMZ, the WAN IP in the ASUS router still shows as internal private 198.168.0.1.
I do not want to have to run a nonstop 24x7 PC with DynDNS Updater client software installed - on the local LAN. When I am away from home, I only want the modem & router to be powered on, and no other PC to be left powered on.
Again, thx for the Workaround suggestion about DMZ. I do wonder if DMZ if necessary if SAGEMCOM modem is already in BRIDGE mode & connect directly to the ASUS router. I may be able to test hypothesis eventually when I get to an external wifi system I trust to use for a test.
Oh, bummer! That kills my setup unless you have an internal device that can update DynDNS. Have you tested what DynDNS does? By default, they claim it gets the public IP address by querying the WAN IP address.
I'm looking to add support for F@ST 4320 by Sagemcom, it's a Windstream modem I bought at a vintage store years ago (if the ISP needs to be redacted, please do so. I just added it so anyone else with the same modem can find the modem more easily via Google).
This post is long as I try to put as much info I can to help figure out how to add support for this modem. I'm using a combination of -developer/adding_new_device#collecting_relevant_data and my own knowledge of Linux to pull the information.
I also pulled the rootfs and data partition off of the modem via netcat. The rootfs is stored at /dev/mtdblock0 and the data partition is stored at /dev/mtdblock2. Both of them are jffs2 partitions. Block 1 is jffs2 but has no files when mounted as mount -t jffs2 /dev/mtdblock1 /tmp/block1. Blocks 4 through 7 returns a No such device error when attempting to mount them. I had verified the transfer of the rootfs and data partitions by using sha256sum that I statically compiled for mips32 from coreutils (I did remount rootfs as rw to put a test.txt at the root in order to determine that I had the right block for rootfs).
I know the adsl line driver chip is a BCM6306KMLG from opening up the casing on the modem. I determined that the board chip id is 63268 from seeing what happens by loading a wrong firmware against the modem via tftp. Using the command, tftp -g -t i -f openwrt_cfe_image_filename.bin my_computers_ip_assigned_by_this_modem_via_ethernet.
The modem has a DSL port, WAN port, 4 ethernet ports, two usb ports, a reset button, one unlabeled light, an "@" light (forgot what that means), a DSL light, a Bonding Light (whatever that means, it uses the same icon as the DSL icon right next to it), an ECO button with a light below it, a WPS button also with a light, a Wireless button with a light (it looks like a radio antenna), and a power button also with a light. As for power, it receives a 12 V DC and a minimum of 2 Amps.
Here are a couple of images of the board itself and one image of me showing how to open the casing (after removing the screws). As the images are too big to open here, and I'm not trying to make the quality poorer than it needs to be, here's an Imgur link:
If we can figure out how to get the modem to boot from usb and/or tftp without flashing the firmware, that'll be great as then I can test a built firmware without worrying about bricking the modem. I don't have access to a jtag, and have to find my solder if using serial. I don't know if the RPi is stable enough for flashing firmware, but I've used the RPI before to communicate with a sim900 over serial.
Edit: I believe BCM963268 is the bootloader. It seems that quite a few devices share this id and on this mirror of Wikidevi (cause the original site is dead and well search isn't going to work on the Wayback machine), a random device I found in search shows this id refers to a bootloader. I did find out where I got the US from back then. -cat.ru/Sagemcom_F@ST_4320US
Edit 2: I'm currently trying to work out if the source code named bcm963xx_4.12L.08_consumer_release.tar.gz, would contain the necessary data for being able to compile OpenWRT for this router. The source of my link is _gpl_violation/dfxglda?utm_source=share&utm_medium=web2x&context=3. That'll most likely be a no as other devices with that bootloader can have different hardware configuration. E.g. SKY SR102 from the old OpenWRT Wiki does not have USB.
If by xDSL modem you mean the ability to connect it to an ISP, then that's fine. I don't plan on using this with an ISP (moreso I plan on using this to play around with mesh networking). As for wireless, I can work with that. I'll just have to use ethernet for now and see if I can get this to boot OpenWRT to a state where I can connect via ethernet.
My goal is to stick this into an RV and then see if I can get 3G+ to work via the USB port. I can then use another modem I have which already works with OpenWRT to send out the wireless connection (assuming I can't get wireless working on this one).
Edit: If I can learn how to get any system to work on this at all, that'd be great to help teach me how to build firmware for devices which aren't officially supported. I've never built firmware for a board before and am currently working out how exactly to use the build tools to do so. -developer/adding_new_device
From what I can tell, I need a device tree file to decompile in order to find out information like the leds, network adapters, and any other hardware. Problem is, /sys/firmware is an empty folder, so I'm trying to figure out where the information is located at (as the stock firmware knows about the hardware, so it's getting the info from somewhere). The symlink /proc/device-tree does not exist either.
Edit: Okay, so looking at and the dmesg log, I have 100% confirmed this modem uses the brcm63xx target. It's renamed to bcm63xx which is what shows up in the dmesg log. I'm still not sure why the cpu is marked as Broadcom4350 in /proc/cpuinfo instead of the BCM63168 that is on the wiki. I do know it's mips32 big endian though due to checking the existing busybox which I pulled and being able to successfully compile and run sha256sum for the modem statically.
I am pluged in and using it. Happy with speed but un-happy that I dont have Green Bars to indicate that I am on a 5G network (from the tower). Customer care, IT support and website all tell my my address is in 5g area. I still have a ticket open for this matter.
I do not mean devices connecting to my WIFI router as 2.4GHz vs 5GHz, im talking about 5g connection from TPG tower to my Modem. (my laptop is connected to modem via cable so no Wifi to devise issues)
I am close to a window etc. I have even taken my modem on an extension cord and sat in my backyard with no trees etc and still only Amber lights. Thus no excuse for not being close to a window or other interference.
I called Sky (my ISP) support who happily informed me that there is a common issue with the power supply to the Sagem router that caused them to fail. Wanting to get back on the net immediately and conversation about a replacement power supply giving vague delivery lead times, I opted to purchase the new Sky branded router (dubbed the Sky Hub):
4a15465005