OpenWrt Forum Archive

Topic: Netgear DGN3500

The content of this topic has been archived between 8 Feb 2018 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

First message on this forum so hi everybody.

I was wondering if openWRT supports the target snr function, my isp handed me a stupidly high db dsl2 profile so my connection would never go over 5mb instead of the 7 I manage to get by tweaking the snr.

Thanks.

Thanks.

I haven't managed to get a working ppoa connection and going back to stock through the webui is not possible.


What's my best course of action? Is it possible to go back to stock?

Tleilax wrote:

I haven't managed to get a working ppoa connection and going back to stock through the webui is not possible

I'm not sure I've understood correctly your situation.
Do you have access to the LUCI interface?
Then, go to [ System | Backup / Flash firmware ] and upload the stock image again. Remember to uncheck "Keep settings".

chainofflowers wrote:
Tleilax wrote:

I haven't managed to get a working ppoa connection and going back to stock through the webui is not possible

I'm not sure I've understood correctly your situation.
Do you have access to the LUCI interface?
Then, go to [ System | Backup / Flash firmware ] and upload the stock image again. Remember to uncheck "Keep settings".


Dsl up and running by selecting PPPoA (supposedly my isp supporthed PPPoE too) and disabling ipv6 negotiation, so at least the router is working again.

Loading the stock netgear firmware through the  webui doesn't work and to my best understanding I should load it through tfpt, for the moment I'll stay with openwrt.

Issues encountered so far:
- booting takes considerably longer than the stock firmware
- the wan leds aren't working
- not sure if ht40 is supported


How do I access dsl_cpe_control? I suppose that it's a text file located somewhere? SSH is working btw.

(Last edited by Tleilax on 31 Aug 2014, 20:41)

Tleilax wrote:

- booting takes considerably longer than the stock firmware

Yes

Tleilax wrote:

- the wan leds aren't working

My wan/"i"nternet led works.. but it doesn't blink.

Tleilax wrote:

- not sure if ht40 is supported

No. I think its an atheros driver limitation.. I can't connect more than MCS 7 (65mbit HT20 LGI TX/RX).

Tleilax wrote:

How do I access dsl_cpe_control? I suppose that it's a text file located somewhere? SSH is working btw.

Connect with ssh and type:
root@OpenWrt:~# dsl_cpe_control --help

Anothe issue: firewall has port 0 and 1 "visible" (closed).

Tleilax wrote:

Loading the stock netgear firmware through the  webui doesn't work and to my best understanding I should load it through tfpt, for the moment I'll stay with openwrt.

OK, I misread: I thought you meant the OpenWRT image when saying "stock" and wanted to revert to the default settings.

If you want to flash the Netgear firmware, just follow the steps in my message here.

About the LEDs: go to [ System | LED Configuration ] and play around with the several choices. You might want to install additional packages to have some more options - just search for "led".

chainofflowers wrote:
Tleilax wrote:

Loading the stock netgear firmware through the  webui doesn't work and to my best understanding I should load it through tfpt, for the moment I'll stay with openwrt.

OK, I misread: I thought you meant the OpenWRT image when saying "stock" and wanted to revert to the default settings.

If you want to flash the Netgear firmware, just follow the steps in my message here.

About the LEDs: go to [ System | LED Configuration ] and play around with the several choices. You might want to install additional packages to have some more options - just search for "led".

I read all the thread pages (been lurking this thread for years actually) but I missed your post since I was a bit nervous today, I hate when people ask questions with clear answers and tutorials, sorry about that.


regarding cpe_dsl_control

root@OpenWrt:~# dsl_cpe_control --help
DSL_CPE: Welcome to DSL CPI API control application
DSL_CPE: usage: [options]
DSL_CPE: following options are available:
DSL_CPE:  --help          (-h)    - help screen
DSL_CPE:  --version       (-v)    - display version
DSL_CPE:  --init          (-i)    - init device w/ <xtu> Bits seperated by underscore (e.g. -i05_01_04_00_04_01_00_00)
DSL_CPE:  --console       (-c)    - start console
DSL_CPE:  --event_cnf     (-e)    - configure instance activation handling <enable/disable>[_mask] (e.g. -e1_1)
DSL_CPE:  --msg_dump      (-m)    - enable message dump
DSL_CPE:  --auto_scr_1    (-a)    - autoboot start script for ADSL (empty by default)
DSL_CPE:  --firmware1     (-f)    - firmware file, default /opt/ifx/firmware/ModemHWE.bin
DSL_CPE:  --opt_off       (-o)    - deactivate footprint optimizations
DSL_CPE:  --notif         (-n)    - notification script name, default ./adslrc.sh
DSL_CPE:  --tcpmsg        (-t)    - enable dbgtool support on tcp ports 2000/2001, listen only on <ipaddr> (optional)

after a bit of headscratching I went with --console and there you get a prompt where you can enter the commands

root@OpenWrt:~# dsl_cpe_control --console
DSL_CPE: Device /dev/dsl_cpe_api opened successfully
DSL_CPE: Welcome to the CLI interface of DSL CPE API
DSL_CPE: Enter 'help all' for a list of built-in commands.
DSL_CPE: Could not unmask event(18) for device 0 (0)!
DSL_CPE:  open /opt/ifx/firmware/ModemHWE.bin failed.

DSL_CPE#>locs 0 -20
nReturn=-11

that error doesn't look promising

time to negotiate again

DSL_CPE#>acs 2
nReturn=0

DSL_CPE#>sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000000

sEventType=DSL_EVENT_S_AUTOBOOT_STATUS nStatus=3 nFirmwareRequestType=1

sEventType=DSL_EVENT_S_LINE_STATE nLineState=000000FF


sEventType=DSL_EVENT_S_FIRMWARE_DOWNLOAD_STATUS nError=0 nFwType=1
sEventType=DSL_EVENT_S_AUTOBOOT_STATUS nStatus=2 nFirmwareRequestType=0

sEventType=DSL_EVENT_S_LINE_POWERMANAGEMENT_STATE nPowerManagementStatus=DSL_G997_PMS_L3

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000100

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000200

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000300

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000380

sEventType=DSL_EVENT_S_SYSTEM_INTERFACE_STATUS nTcLayer=1 nEfmTcConfigUs=0x00000000 nEfmTcConfigDs=0x00000000 nSystemIf=3

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000001

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000000

sEventType=DSL_EVENT_S_AUTOBOOT_STATUS nStatus=3 nFirmwareRequestType=1

sEventType=DSL_EVENT_S_LINE_STATE nLineState=000000FF


sEventType=DSL_EVENT_S_FIRMWARE_DOWNLOAD_STATUS nError=0 nFwType=1
sEventType=DSL_EVENT_S_AUTOBOOT_STATUS nStatus=2 nFirmwareRequestType=0

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000100

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000200

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000300

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000380

sEventType=DSL_EVENT_S_SYSTEM_INTERFACE_STATUS nTcLayer=1 nEfmTcConfigUs=0x00000000 nEfmTcConfigDs=0x00000000 nSystemIf=3

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000800

sEventType=DSL_EVENT_S_CHANNEL_DATARATE nChannel=0 nAccessDir=DSL_DOWNSTREAM ActualDataRate=5047949 PreviousDataRate=5208000 ActualInterleaveDelay=25 ActualImpulseNoiseProtection=0

sEventType=DSL_EVENT_I_CHANNEL_DATARATE_SHIFT_THRESHOLD_CROSSING nChannel=0 nAccessDir=DSL_DOWNSTREAM nDataRateThresholdType=DSL_G997_DATARATE_THRESHOLD_DOWNSHIFT

sEventType=DSL_EVENT_S_LINE_POWERMANAGEMENT_STATE nPowerManagementStatus=DSL_G997_PMS_L0

sEventType=DSL_EVENT_S_LINE_STATE nLineState=00000801

sEventType=DSL_EVENT_S_FE_INVENTORY_AVAILABLE G994VendorID=(B5,00,49,46,54,4E,82,B3) SystemVendorID=(00,00,00,00,00,00,00,00) VersionNumber=(00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00) SerialNumber=(00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00) SelfTestResult=0 XTSECapabilities=(00,00,00,00,00,01,00,00)

did this twice (once with -50 and then with -20) but it doesn't make any difference

I think I've managed to get ht40 working by ticking the "force 40 mhz mode" checkbox under advanced wireless settings (complying with IEEE directives is for casuals); I'm using channel 6 and haven't experimented with 1 or 11.

Tleilax wrote:

I think I've managed to get ht40 working by ticking the "force 40 mhz mode" checkbox under advanced wireless settings (complying with IEEE directives is for casuals); I'm using channel 6 and haven't experimented with 1 or 11.

Hi,
maybe you are referring to "Always use 40MHz channels even if the secondary channel overlaps. Using this option does not comply with IEEE 802.11n-2009!"

Here my results using same settings (channel 6, ht40 forced):

SSID     MAC-Address     IPv4-Address     Signal     Noise     RX Rate     TX Rate
xxxAP    78:92:9C:05:73:84    192.168.1.2    -49 dBm    -93 dBm    65.0 Mbit/s, MCS 7, 20MHz    65.0 Mbit/s, MCS 7, 20MHz

Transfer speed from a wireless N (intel centrino wireless N 100) device is about 4.85Mb/s

Edit: I found the problem: my wireless card by default uses WMM off and 20mhz (LGI). I changed the advanced settings and now it works at MCS 7 40mhz (150mbit).

(Last edited by avware on 2 Sep 2014, 22:44)

avware wrote:
Tleilax wrote:

I think I've managed to get ht40 working by ticking the "force 40 mhz mode" checkbox under advanced wireless settings (complying with IEEE directives is for casuals); I'm using channel 6 and haven't experimented with 1 or 11.

Hi,
maybe you are referring to "Always use 40MHz channels even if the secondary channel overlaps. Using this option does not comply with IEEE 802.11n-2009!"

Here my results using same settings (channel 6, ht40 forced):

SSID     MAC-Address     IPv4-Address     Signal     Noise     RX Rate     TX Rate
xxxAP    78:92:9C:05:73:84    192.168.1.2    -49 dBm    -93 dBm    65.0 Mbit/s, MCS 7, 20MHz    65.0 Mbit/s, MCS 7, 20MHz

Transfer speed from a wireless N (intel centrino wireless N 100) device is about 4.85Mb/s

Edit: I found the problem: my wireless card by default uses WMM off and 20mhz (LGI). I changed the advanced settings and now it works at MCS 7 40mhz (150mbit).


I think the 40mhz implementation was flacky to begin with in the chipset since this router came out in 2010, I don't remember ever getting more than 65mbit from the original firmware (but I used channel 11) as an added bonus enabling the forced 40mhz mode improved coverage in a remote room through several concrete walls from barely keeping up to stable.


There's something going on with the usb port, hooked up an atheros 9270 tp link wifi card, installed ath9k-htc and the other ath9k common packet and this is what dmesg says

[   69.240000] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[   70.248000] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
[   70.252000] ath9k_htc: Failed to initialize the device
[   70.256000] usb 1-1: ath9k_htc: USB layer deinitialized

This bug is reported as fixed so maybe it's a board specific issue?
Since ht40 works it doesn't matter that much, but some people could like to run multiple wlan setups.

(Last edited by Tleilax on 2 Sep 2014, 23:15)

Tleilax wrote:

There's something going on with the usb port, hooked up an atheros 9270 tp link wifi card, installed ath9k-htc and the other ath9k common packet and this is what dmesg says

[   69.240000] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[   70.248000] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
[   70.252000] ath9k_htc: Failed to initialize the device
[   70.256000] usb 1-1: ath9k_htc: USB layer deinitialized

This bug is reported as fixed so maybe it's a board specific issue?
Since ht40 works it doesn't matter that much, but some people could like to run multiple wlan setups.

I found this one: https://dev.openwrt.org/ticket/13850
..but I don't think this patch was been applied to BB-rc3, you can try to compile the trunk or wait rc4 to resolve it.

Does anybody have the schematics for DGN3500(B)? I am trying to reconfigure one of the lan ports as a wan, so internet access is not provided via ADSL but LAN. (http://pbforfoss.com/openwrt/2014/03/14 … -vlan.html) Or could someone help me right away?

Hi,
I report these strange messages, does anyone know the cause or how to fix?
Thanks !

...
[947669.320000] eth0: tx ring full
root@OpenWrt:~# dmesg | grep "tx ring full" | wc -l
2323
root@OpenWrt:~# uptime
21:36:25 up 20 days,  9:59,  load average: 0.54, 0.53, 0.55

(Last edited by avware on 29 Sep 2014, 22:41)

I managed to get BARRIER BREAKER (14.07, r42625) installed on a Netgear
DGN3500. I think the ADSL modem is working as I get this:

root@dgn3500:~# /etc/init.d/dsl_control status
Chipset:                Ifx-AR9 1.2
Line State:             UP [0x801: showtime_tc_sync]
Data Rate:              2.911 Mb/s / 647 Kb/s
Line Attenuation:       46.7dB / 22.6dB
Noise Margin:           9.4dB / 10.0dB
Line Uptime:            4s

My problem is when I try to connect to my ISP:

Thu Oct 30 19:01:53 2014 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Oct 30 19:01:53 2014 daemon.notice netifd: Interface 'wan' is now down
Thu Oct 30 19:01:53 2014 daemon.notice netifd: Interface 'wan' is setting up now
Thu Oct 30 19:01:54 2014 daemon.info pppd[740]: Plugin pppoatm.so loaded.
Thu Oct 30 19:01:54 2014 daemon.info pppd[740]: PPPoATM plugin_init
Thu Oct 30 19:01:54 2014 daemon.info pppd[740]: PPPoATM setdevname_pppoatm - SUCCESS:0.0.38
Thu Oct 30 19:01:54 2014 daemon.info pppd[741]: Plugin pppoatm.so loaded.
Thu Oct 30 19:01:54 2014 daemon.info pppd[741]: PPPoATM plugin_init
Thu Oct 30 19:01:54 2014 daemon.info pppd[741]: PPPoATM setdevname_pppoatm - SUCCESS:0.0.38
Thu Oct 30 19:01:54 2014 daemon.notice pppd[741]: pppd 2.4.7 started by root, uid 0
Thu Oct 30 19:01:54 2014 daemon.err pppd[741]: connect(0.0.38): Address already in use
Thu Oct 30 19:01:54 2014 daemon.info pppd[741]: Exit.
Thu Oct 30 19:01:54 2014 daemon.notice pppd[740]: pppd 2.4.7 started by root, uid 0
Thu Oct 30 19:01:54 2014 daemon.err pppd[740]: connect(0.0.38): Address already in use
Thu Oct 30 19:01:54 2014 daemon.info pppd[740]: Exit.

Google does not tell me what the cause of 'connect(0.0.38): Address already in use' might be.

If someone can give me some hints how to troubleshoot this and get a working internet connection, that would be great.

To answer my own question, I had to add:

        option payload 'routed'

to under the atm-bridge in /etc/config/network, after that everything worked as expected.

Anyone managed to flash Barrier Breaker using the Stock Netgear firmware flashing utility?

Yay! I flashed Barrier Breaker (14.07, r42625) via the stock firmware's image flash utility using the WW .img file downloaded from the openwrt downloads ftp site. I've got wireless network working, ethernet working, DHCP DNS, etc. But Ic an't get my ADSL connection working. I don't appear to have a /var/log/messages either, and dmesg isn't reporting anything regarding the ADSL that I can see. Where does the syslog sit?

Okay, I got ADSL working, with thanks to "frop" from #openwrt. My /etc/config/network is as follows

config interface 'loopback'
    option ifname 'lo'
    option proto 'static'
    option ipaddr '127.0.0.1'
    option netmask '255.0.0.0'

config globals 'globals'
    option ula_prefix 'fd52:a2ce:08b7::/48'

config interface 'lan'
    option force_link '1'
    option type 'bridge'
    option proto 'static'
    option ipaddr '192.168.42.1'
    option netmask '255.255.255.0'
    option ip6assign '60'
    option ifname 'eth0.1'
    option macaddr 'e0:46:9a:b8:b3:ab'

config switch
    option name 'switch0'
    option reset '1'
    option enable_vlan '1'
    option enable_vlan4k '1'

config switch_vlan
    option device 'switch0'
    option vlan '1'
    option ports '1 2 3 5t'

config switch_vlan
    option device 'switch0'
    option vlan '2'
    option ports '4 5t'

config atm-bridge 'atm'
    option vpi '8'
    option vci '35'
    option encaps 'llc'
    option payload 'bridged'

config interface 'wan'
    option _orig_ifname 'nas0'
    option _orig_bridge 'false'
    option ifname 'nas0'
    option proto 'pppoe'
    option username 'xxxx'
    option password 'xxxx'

config interface 'wan6'
    option ifname '@wan'
    option proto 'dhcpv6'

config adsl 'dsl'
    option annex 'a'
    option firmware '/lib/firmware/adsl.bin'
sirlark wrote:

Okay, I got ADSL working, with thanks to "frop" from #openwrt. My /etc/config/network is as follows

Hi, i just compile from the trunk(chaos calmer) and upgrade from stock firmware through web admin, everything works fine but I just can't get my ADSL connection working, but at least I have conection(link up). I try with your network config but it doesn't work.


Edit:
Linkup

Chipset:                Ifx-AR9 1.2
Line State:             UP [0x801: showtime_tc_sync]
Data Rate:              7.199 Mb/s / 669 Kb/s
Line Attenuation:       21.5dB / 22.2dB
Noise Margin:           13.9dB / 22.2dB
Line Uptime:            18m 27s

PPPoe try

Sun Nov 16 17:44:15 2014 daemon.info pppd[2757]: Plugin rp-pppoe.so loaded.
Sun Nov 16 17:44:15 2014 daemon.info pppd[2757]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Nov 16 17:44:15 2014 daemon.notice pppd[2757]: pppd 2.4.7 started by root, uid 0
Sun Nov 16 17:44:30 2014 daemon.warn pppd[2757]: Timeout waiting for PADO packets
Sun Nov 16 17:44:30 2014 daemon.err pppd[2757]: Unable to complete PPPoE Discovery
Sun Nov 16 17:44:30 2014 daemon.info pppd[2757]: Exit.

PPPoa try

Sun Nov 16 17:52:28 2014 daemon.notice pppd[4081]: Connect: pppoa-wan <--> 0.8.35
Sun Nov 16 17:52:58 2014 daemon.warn pppd[4081]: LCP: timeout sending Config-Requests
Sun Nov 16 17:52:58 2014 daemon.notice pppd[4081]: Connection terminated.
Sun Nov 16 17:52:58 2014 daemon.notice pppd[4081]: Modem hangup
Sun Nov 16 17:52:58 2014 daemon.info pppd[4081]: Exit.

My network config

config interface 'loopback'
    option ifname 'lo'
    option proto 'static'
    option ipaddr '127.0.0.1'
    option netmask '255.0.0.0'

config globals 'globals'
    option ula_prefix 'fd0a:ed07:ed67::/48'

config interface 'lan'
    option force_link '1'
    option type 'bridge'
    option proto 'static'
    option ipaddr '192.168.5.1'
    option netmask '255.255.255.0'
    option ip6assign '60'
    option ifname 'eth0.1'
    option macaddr 'XX:XX:XX:XX:XX:XX'

config switch
    option name 'switch0'
    option reset '1'
    option enable_vlan '1'

config switch_vlan
    option device 'switch0'
    option vlan '1'
    option ports '3 2 1 0 5t'

config atm-bridge 'atm'
    option vpi '8'
    option vci '34'
    option encaps 'llc'
    option payload 'bridged'

config interface 'wan'
    option _orig_ifname 'nas0'
    option _orig_bridge 'false'
    option proto 'pppoe'
    option username 'XXXXX'
    option password 'XXXX'
    option ifname 'nas0'

config adsl 'dsl'
    option annex 'a'
    option firmware '/lib/firmware/adsl.bin'

Edit 2: now I make it work

config interface 'loopback'
    option ifname 'lo'
    option proto 'static'
    option ipaddr '127.0.0.1'
    option netmask '255.0.0.0'

config globals 'globals'
    option ula_prefix 'fd0a:ed07:ed67::/48'

config interface 'lan'
    option force_link '1'
    option type 'bridge'
    option proto 'static'
    option ipaddr '192.168.5.1'
    option netmask '255.255.255.0'
    option ip6assign '60'
    option ifname 'eth0.1'
    option macaddr 'xx:xx:xx:xx:xx:xx'

config switch
    option name 'switch0'
    option reset '1'
    option enable_vlan '1'
    option mirror_source_port '0'
    option mirror_monitor_port '0'
    option enable_vlan4k '1'

config switch_vlan
    option device 'switch0'
    option vlan '1'
    option ports '0 1 2 3 5t'

config atm-bridge 'atm'
    option vpi '8'
    option encaps 'llc'
    option payload 'bridged'
    option vci '32'

config interface 'wan'
    option _orig_ifname 'nas0'
    option _orig_bridge 'false'
    option ifname 'nas0'
    option proto 'pppoe'
    option delegate '0'
    option username XXXX@tchile'
    option password XXXX'

config adsl 'dsl'
    option annex 'a'
    option firmware '/lib/firmware/adsl.bin'

(Last edited by aBrAx on 17 Nov 2014, 12:30)

Hi, I just figured out that wlan mac address change randomly every reboot, there's some way to fix it?
I need to connect other devices to my dgn3500 through wlan so it's a big issue that mac change.

Just to confirm that Barrier Breaker works flawlessly on my Netgear DGN3500.

I too flashed Barrier Breaker using the Netgear image flash utility, supplying the v14.07 openwrt-lantiq-xway-DGN3500-squashfs-factory-WW.img file as downloaded from the openwrt downloads ftp site.

The Luci interface makes installing software and configuring the router child's play!

I have the following working:
- DSL
- WiFi (802.11n)
- Samba (requires software download & configuration)
- Dynamic DNS (requires software download & configuration)
- ipv6 using 6to4 (requires software download & configuration) (because my ISP supplies only ipv4. Otherwise ipv6 just works.)

Happy days, because Netgear has end-of-life'd the router without ipv6 support being implemented!

Great work guys, thank you!

I can confirm this router works well with OpenWrt Barrier Breaker 14.07!

I used the "factory" image and flashed directly from Netgear web interface: it works! smile

The router seems to take quite a lot to boot (I have no serial, so exscuse me if no bootlog attached) but everything I tested untill now simply works.

I have ADSL2+ working with PPPoA (I couldn't test PPPoE with my ISP) and wifi full speed (40MHz mode too).

I only have one question about LED configuration: I could configure all of them but I don't understand how to make DSL led on just DSL is synchronized. I have set up INTERNET led to be triggered by netdev (pppoa0 device) when link is up and tx/rx happens; but I couldn't find an option to trigger the DSL led after synchronized with the DSLAM. Could you help me?

(Last edited by M3m3nt0 on 14 Jan 2015, 15:24)

Happy,

Upgraded my DGN3500 firmware V1.1.0028_1.00.28 to OpenWrt Barrier Breaker 14.07!
Flashed dirececly from web interface.

My internet provider (www.online.nl) and i got the ADSL Extra package.
Abonnementsvorm ADSL Extra (Family)
Verbindingsprotocol 1483 Bridged IP (RFC1483) LLC
VPI / VCI 8 / 35

The hard part was to match the labels...
the labels used in the livebox: bridged ip LLC - mer (MAC Encapsulated Routing).

Means use dhcp option.
In WAN -> advanced settings, i had to override my adsl MAC address. (wrote it down before the update).

ATM bridges:
VPI 8
VCI 35
LCC encapsulated

ATM bridges ->advanced settings:
forwarding mode to bridged.

So now i'm IPv6 ready tongue