Sagem 2704n

[#1]

I have just tried the 2704n on my friends ADSL line, no IPv6.

[#2]

Have you tried setting <X_BROADCOM_COM_IPv6Enabled> to TRUE on <WANPPPConnection instance="1">?

Darsh

[#3]

Quote from: Bob

Can probably supply a few devices if anybody fancies the challenge?

I joined Plusnet just a month ago and don't have an IPv6 account. But I do have a 2704N. Can I get an IPv6 account?

Darsh

[#4]

Very many thanks to Darsh
I now have it working with IPv6.
Getting 10/10 when testing with http://test-ipv6.com/
I did gateway hop until I was on a non bng gateway.
My notes were as follows

Set up the router to use the ipv6 test login and password.
Set the  DNS Servers are set to google (8.8.8.8 & 8.8.4.4)
Advanced Settings > DNS
Make a plain text copy of the settings using http://192.168.1.254/dumpcfgdynamic.cmd
Make sure there is NOT a space at the start of the first line
Make sure the last few lines at the end are removed so that the last line is </DslCpeConfig>
Edit using notepad
Between the lines
<X_BROADCOM_COM_IfName>ppp1.1</X_BROADCOM_COM_IfName>
<ExternalIPAddress notification="2">81.174.XXX.XXX</ExternalIPAddress>
Add:
<X_BROADCOM_COM_IPv6Enabled>TRUE</X_BROADCOM_COM_IPv6Enabled>
i.e.
<X_BROADCOM_COM_IfName>ppp1.1</X_BROADCOM_COM_IfName>
<X_BROADCOM_COM_IPv6Enabled>TRUE</X_BROADCOM_COM_IPv6Enabled>
<ExternalIPAddress notification="2">81.174.XXX.XXX</ExternalIPAddress>
The last parts of the IP address have been hidden
Load the edited file using http://192.168.1.254/expert_user.html
Management > Settings > Update
N.B. Although the Connection Status screen on the router shows DSL Down it should be working.

[#5]

Why are you changing the DNS servers? OK it may be recommended, but surely it is not required:

C:\Users\John>nslookup loopsofzen.co.uk 212.159.6.9
Server:  cdns01.plus.net
Address:  212.159.6.9
Name:    loopsofzen.co.uk
Address:  2001:8b0:0:30::666:102

[#6]

The other issue is that it doesn't respond to pings (IPv4 or IPv6). Have you found a simple way of enabling that (some of the other posts I've seen about hacking this router seem rather drastic!).

[#7]

DNS change is not essential but I have been using them for longer than I care to remember.
Ping response is next thing on my to do list.
Gave up for today after my first attempt required a router reset.

[#8]

Plusnet 2704N by default comes with ICMP disabled on all interfaces in iptables. To enable it, you need to create firewall exception on WAN interface, allowing ICMP in (config here). This works for IPv4, might work for IPv6 as well. Worth trying.

Darsh

[#9]

Now getting a ping response for IPv4 but not for IPv6.
Can also login to the command line using PuTTY.
@Darsh, many thanks again for all your work on the 2704n. I followed your instructions, edited the config file by hand.

[#10]

Unfortunately, I can't play with IPv6 as I can with IPv4 because I don't have an IPv6 account.
Most of the credit should go to Matty123123, it's him who unlocked the router, I just examined the config.
By the way, you can try Matty123123's unlocked firmware - maybe it will allow you to configure the IPv6 firewall rules as well?
Plusnet's firmware has a lot of valuable GUI pages locked - when you try to access them, you get "you are not allowed to access this page" error. Matty123123 has managed to unlock them.
Full GUI is documented in Sagemcom's manual - but since it is describing Sagemcom's firmware, some GUI pages are different.
Looking in the manual - it seems that specifying IPv6 in the firewall rules is possible (section 6.4.6, page 108, parameter IP Version). But which config tag it will translate to - I don't know yet. Can try to play on my router - but I won't be able to tell whether it works or not - I don't have an IPv6 account.

Darsh

[#11]

Don't want to update the firmware, the unit was loaned to me.
I expect to have to return it in the near future and don't want to do anything a factory reset will not clear.
I got the unit to respond to an IPv6 TBB ping monitor by going to the command line and adding a rule to ip6tables.
Not sure that this rule is retained following a reboot, will look at that another time.

sh
ip6tables -I INPUT 4 -p icmpv6 -j ACCEPT --icmpv6-type echo-request
exit
save

I used the following from the command line to find the full IPv6 address.

ifconfig br0

[#12]

Quote from: PeteB

Don't want to update the firmware, the unit was loaned to me.

Matty123123 has posted the original Plusnet's firmware (the link to it is inside the pdf) as well. You can always return back to it.

Quote from: PeteB

Not sure that this rule is retained following a reboot, will look at that another time.

It won't. I've tried it for IPv4. You need to add this somehow to the config. You need to know the correct IPv6 firewall tags for this. One of the ways would be to upload the Matty123123's firmware, configure the firewall for IPv6, go to the CLI, do dumpmdm to dump the full config - then you will have an idea of how do IPv6 firewall tags look like.
After that - you can revert back to the original firmware.

Darsh

[#13]

I think I've found it. Look at the following config extract:

          <X_BROADCOM_COM_FirewallException instance="1">
            <Enable>TRUE</Enable>
            <FilterName>ICMP</FilterName>
            <IPVersion>4</IPVersion>
            <Protocol>ICMP</Protocol>
            <SourcePortStart>0</SourcePortStart>
            <SourcePortEnd>0</SourcePortEnd>
            <DestinationPortStart>0</DestinationPortStart>
            <DestinationPortEnd>0</DestinationPortEnd>
            <SourceIPAddress>(null)</SourceIPAddress>
            <SourceNetMask>(null)</SourceNetMask>
            <DestinationIPAddress>(null)</DestinationIPAddress>
            <DestinationNetMask>(null)</DestinationNetMask>
            <X_SAGEM_COM_HideForWEBGUI>FALSE</X_SAGEM_COM_HideForWEBGUI>
          </X_BROADCOM_COM_FirewallException>

These are the full tags for the FirewallException. Note the IPVersion tag. Try to add this tag with "6" in it to your IPv4 firewall config you've used to enable pings. I reckon it should enable IPv6 pings.
Warning: don't copy all the tags from this extract to your firewall config - this might cause the rules to work incorrectly. Just copy the IPVersion tag into your existing config.

Darsh