Unlocking the potential of Sagemcom 2704N
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Other forums
- :
- Tech Help - Software/Hardware etc
- :
- Unlocking the potential of Sagemcom 2704N
Re: Unlocking the potential of Sagemcom 2704N
01-05-2015 7:27 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Could you point out where i've asked for help with bridging mode arsh?
Re: Unlocking the potential of Sagemcom 2704N
01-05-2015 7:30 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Darsh
Re: Unlocking the potential of Sagemcom 2704N
10-05-2015 5:04 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: Darsh Confirmed, to enable pings to the WAN interface, you need to add the following lines to your config: <DslCpeConfig version="3.0">
<InternetGatewayDevice>
<X_BROADCOM_COM_AppCfg>
<IcmpCfg>
<NetworkAccess>LAN or WAN</NetworkAccess>
</IcmpCfg>
</X_BROADCOM_COM_AppCfg>
<WANDevice instance="1">
<WANConnectionDevice instance="1">
<WANPPPConnection instance="1">
<X_BROADCOM_COM_FirewallException instance="1">
<Enable>TRUE</Enable>
<FilterName>ICMP</FilterName>
<Protocol>ICMP</Protocol>
</X_BROADCOM_COM_FirewallException>
<X_BROADCOM_COM_FirewallException nextInstance="2" ></X_BROADCOM_COM_FirewallException>
</WANPPPConnection>
</WANConnectionDevice>
</WANDevice>
</InternetGatewayDevice>
</DslCpeConfig>
Works now.
Darsh
Has anyone managed to get pings to work in "Fibre" mode?
I can see the firewall is enabled under the WANPPPConnection section (in this case eth3), but when I add the firewall exception, the router rejects the XML file when I attempt to reload it.
The <IcmpCfg> section is accepted without any errors.
Re: Unlocking the potential of Sagemcom 2704N
12-05-2015 1:31 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: grm (only using it as an AP so wouldn't expect any firewall entries)
Hello grm,
I've had a play with OpenWrt, and I was wondering if your any good at playing with openwrt firmware. The wireless chipset is supposed to be fully supported, but I cant get it working right/fully?
EDIT:
oh <beep> forget it, it has the wrong PCI - ID
EDIT2:
Never mind... got it working
Re: Unlocking the potential of Sagemcom 2704N
12-05-2015 4:45 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote Has anyone managed to get pings to work in "Fibre" mode?
Yes, I am on Fibre and have"pings" working.
IPv4 by modifying and reloading the config file.
IPv6 by using the ip6tables command from the command line http://community.plus.net/forum/index.php/topic,138295.msg1224689.html#msg1224689.
Pete
Re: Unlocking the potential of Sagemcom 2704N
12-05-2015 8:15 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I am using IP4 so just trying to modify the config file as per Darsh's note and adding the firewall exception XML inside the WANPPPConnection section of the file but the file is rejected as invalid when I try to upload it to the router (I can make other changes to the file and re-upload without problem)
I am using the stock firmware.
Re: Unlocking the potential of Sagemcom 2704N
12-05-2015 8:31 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
In case it is of any use here is the output from a linux diff for the two files, noping.txt & ping.txt.
diff noping.txt ping.txt
19a20,22
> <IcmpCfg>
> <NetworkAccess>LAN or WAN</NetworkAccess>
> </IcmpCfg>
676a680,685
> <X_BROADCOM_COM_FirewallException instance="1">
> <Enable>TRUE</Enable>
> <FilterName>ICMP</FilterName>
> <Protocol>ICMP</Protocol>
> </X_BROADCOM_COM_FirewallException>
> <X_BROADCOM_COM_FirewallException nextInstance="2" ></X_BROADCOM_COM_FirewallException>
Re: Unlocking the potential of Sagemcom 2704N
13-05-2015 3:36 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
(Currently have it at just after the <X_BROADCOM_COM_FirewallEnabled>TRUE</X_BROADCOM_COM_FirewallEnabled> statement in the <WANPPPConnection instance="1"> section I have also tried the top and bottom of the WANPPPConnection with no joy). Assuming that is the correct section, I guess I should probably try going back to factory default settings with no forwarding rules etc and see if that works.
Re: Unlocking the potential of Sagemcom 2704N
13-05-2015 3:43 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
@PeteB,
Seeing as I am not familiar with where I need to put the following lines in the config for FTTC, could you give us a few pointers please.
I see you have pulled the following commands using diff and have defined what we need to add which is as follows, bearing in mind you are on FTTC with a locked 2704n as are we.
<IcmpCfg>
<NetworkAccess>LAN or WAN</NetworkAccess>
</IcmpCfg>
<X_BROADCOM_COM_FirewallException instance="1">
<Enable>TRUE</Enable>
<FilterName>ICMP</FilterName>
<Protocol>ICMP</Protocol>
</X_BROADCOM_COM_FirewallException>
<X_BROADCOM_COM_FirewallException nextInstance="2" ></X_BROADCOM_COM_FirewallException>
Do I put those lines at the end of the config, or is it mind-bendingly complicated to place those elements in the config.
Re: Unlocking the potential of Sagemcom 2704N
13-05-2015 3:53 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Try this:
Before
<X_SAGEM_COM_ppp_retry_period>15</X_SAGEM_COM_ppp_retry_period>
</WANPPPConnection>
<WANPPPConnection nextInstance="2" ></WANPPPConnection>
After
<X_SAGEM_COM_ppp_retry_period>15</X_SAGEM_COM_ppp_retry_period>
<X_BROADCOM_COM_FirewallException instance="1">
<Enable>TRUE</Enable>
<FilterName>ICMP</FilterName>
<Protocol>ICMP</Protocol>
</X_BROADCOM_COM_FirewallException>
<X_BROADCOM_COM_FirewallException nextInstance="2" ></X_BROADCOM_COM_FirewallException>
</WANPPPConnection>
<WANPPPConnection nextInstance="2" ></WANPPPConnection>
Re: Unlocking the potential of Sagemcom 2704N
13-05-2015 4:08 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Mine has a little extra, so as follows.
<X_SAGEM_COM_ppp_retry_period>15</X_SAGEM_COM_ppp_retry_period>
<X_BROADCOM_COM_FirewallException instance="1">
<Enable>TRUE</Enable>
<FilterName>ICMP</FilterName>
<Protocol>ICMP</Protocol>
</X_BROADCOM_COM_FirewallException>
<X_BROADCOM_COM_FirewallException nextInstance="2" ></X_BROADCOM_COM_FirewallException>
<X_SAGEM_COM_ppp_neg_mtu>16384</X_SAGEM_COM_ppp_neg_mtu>
<PortMapping nextInstance="375" ></PortMapping>
</WANPPPConnection>
Re: Unlocking the potential of Sagemcom 2704N
13-05-2015 4:13 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: Unlocking the potential of Sagemcom 2704N
13-05-2015 4:24 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I'll test that and get back to you
Re: Unlocking the potential of Sagemcom 2704N
13-05-2015 4:43 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I might come back to you for ssh in a bit.
Re: Unlocking the potential of Sagemcom 2704N
13-05-2015 4:55 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
The lines aren't accepted if I put them after the port mappings, but they are accepted before the port mappings and immedately after the X_SAGEM_COM_ppp_retry_period
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Other forums
- :
- Tech Help - Software/Hardware etc
- :
- Unlocking the potential of Sagemcom 2704N