how-to block ads
How to Enable Bridge Mode on SagemCom
Don't know if anyone is interested but I found this post from t3st3r at the following link. I've tried it and been running stable for the past week. Get full (50/10) speed with my own Router and no PPPOE Passthru/Double NAT issue.
Couple of points I found while following these steps not mentioned in t3st3r's instructions.
- Read Instructions and follow carefully.
- Reset your SagemCom to Factory before attempting
- Default Factory Lan IP for SagemCom is 192.168.2.1
- Configure your Router to a different subnet if it's using 192.168.2.1
- Line 12 may not display Returned 0, this is ok.
- Line 14 may not work, just manually reboot (power cycle)
- Configuration survives a power failure/cycle
- Confirmed that Factory Reset will bring you back to default
- Serial Number is required because elevated commands use it as a confirmation.
- You won't receive updates from Bell (who cares!) But if you're connection ever stops working, see if an update was pushed up that breaks bridge mode. In which case you'll probably have to reset to get the update and I wouldn't be surprised if bell patches the telnet access used by the tool.
Original Link: »actinostome16.vinoreka.com/brows···item=803
[DSL] Sagemcom F@ST 2864 bridge mode guide
This post is intended as a simple guide to enabling "bridge" mode on your Sagemcom F@ST 2864 modem.
This is a proper bridge mode, rather than simply PPPoE forwarding. You will get the full speed of your connection with this setup. This guide is for VDSL only. Settings for FTTH can be found here: »Re: [DSL] bridge mode on Sagemcom f@st2864.
***VERY IMPORTANT NOTICE***
This process and any changes of your Sagemcom modem settings are absolutely not supported by anyone. Neither Teksavvy or Bell will help you with issues that arise due to changing settings on your modem to an unsupported configuration. If you follow this guide you do so entirely at your own risk.
Before we begin I'd like to thank forum user sibisties for his excellent work on the Sagemcom 2864 stats and unlock tool. Without the unlock tool this process would be a great deal more complicated. And thanks to everyone else on the forums who helped with various firmware files and testing ideas.
As of this posting the tools and settings used are known to work on the following firmware versions:
You can check your modem's firmware version in the About page on the Connection Hub site (e.g. »192.168.2.1/index.cgi?page=about )
Now for the guide:
1) Download sibisties' Line Stats & Telnet Unlock Tool from here: »mega.co.nz/#!ohMxkArD!JKqV9gd9wB···2qQqm38A
- For more information on the tool and its features see sibisties' thread here: »Line Stats & Telnet Unlock Tool for Sagemcom 2864 (V2.00)
2) Connect your PC directly to the Sagemcom modem and run the unlock tool, select the "Telnet enable" option and enter the requested information.
3) Run telnet.exe or any telnet connection program you have to connect to the modem at 192.168.2.1, log in with user: admin, pass: admin
3.5) Run the following commands at the Homegateway> prompt:
conf set /dev/br0/enslaved/eth2.35/stp 0
conf set /dev/br0/enslaved/eth2.35/def_vlan 1
conf set /dev/br0/enslaved/eth2.35/vid 1
conf set /dev/br0/enslaved/eth2.35/tagged 0
conf del /dev/ppp0
conf del /dev/ppp1
conf del /dev/ppp2
conf set /dev/br0/dhcps/enabled 0
conf set /fastpath/enabled 0
conf set /dev/br1/enabled 0
conf set /fw/enabled 0
conf ram_set /dev/br1/volatile_enabled 0
conf reconf 1
You should see Returned 0 after entering each command, this means that the command was accepted without errors.
**If for some reason your modem does not reboot after entering the last line, REBOOT YOUR MODEM**
4) Once the modem is finished rebooting, connect your router's WAN port to any one of the modem's LAN ports. Then configure your router's WAN for PPPoE using your DSL login credentials.
4.5)If you have a router running a WRT or Tomato firmware you can use the following commands (on your router) to allow you to access the modem's config page from behind your router*:
ifconfig `nvram get wan_ifname`:0 192.168.2.2 netmask 255.255.255.0
iptables -t nat -I POSTROUTING -o `nvram get wan_ifname` -j MASQUERADE
*Do not use this setting if your internal network uses the 192.168.2.X range.
Otherwise you can connect your PC directly to the Sagemcom modem, assign it a static IP of 192.168.2.2 and access the modem's configuration page at »192.168.2.1. Telnet access will also work.
a) This process is not compatible with IPTV due to the connection requirements of Bell's IPTV service. Do not use this if you have IPTV service as it will disable it.
b) Your modem cannot connect to Bell's ACS management system when in bridge mode. This means that you cannot receive firmware updates or direct support from Bell for connection issues. In order to receive firmware updates you will have to factory reset your router to defaults. It is possible to update the router's firmware through telnet when bridge mode is enabled but that process is not covered by this guide.
c) The settings in the guide are persistent even if your modem is rebooted/loses power. If you need to remove the settings you will need to reset your router to factory defaults. This can be done by holding the reset button (on the bottom of the modem) for ~30 seconds until you see the power light (top LED) go out, then release the reset button. The modem will reboot with all settings at their factory default values (as shipped by Bell).
Thank you Shoey5!!!
I followed these steps and it seems all my issues with this stupid, Bell branded Sagemcom modem is gone.
- Getting full speed (full 50/10)
- DNS issue resolved (Every few days or weeks, my internet would stop working for hours because the Sagemcom stopped passing IPv4 DNS requests properly. I could only get IPv6 responses. Of course we don't have access to do things like configure or disable IPv6. Rebooting the Sagemcom fixed the issue until the next time. Now it is gone!)
- Firewalled from Bell. (Don't know if any of you know, but with PPPoE Pass Through (not bridge real bridge mode, far from it), not only did I lose 1/3 of my download speed, but the SagemCom got 2 external IP's, one from Start and another from Bell. The one from Bell is used for 2 things: 1. Push firmware updates (taking down my Internet at whenever that happens) and 2. To remotely access the router for Bell customers. If your router is in this state, Bell has access to it when they choose and that means access to at least one of your internal IP addresses and that useful network map in the router software. So invasive. Unbelievable that Bell thinks this is okay, especially for non-Bell customers.
Thanks to this, I only get 1 IP (from Start) and it is on my router. Bell cannot push firmware updates, rebooting my router. I have not experienced the IPv6 DNS issue again. I can use my own firewall and I am actually getting slightly higher speeds. 50.50 vs. 50.10 Mbit/s and 10.38 vs. 10.11. Best of all, it can be completely restored if necessary.
Again... thank you Shoey5 for finding this and posting it. Cheers.
You're welcome, but the real credit goes to users t3st3r's and sibisties for putting it together.
I noticed the same thing after applying, DNS issue is gone and my speeds a pinch higher! Best of all, I'm back to my own Router which is far superior and port forwards properly. Couldn't forward UDP 9 (WOL) with the SagemCom either!