OpenWrt Forum Archive

Topic: DG834v2 [AR7] 24h using kamikaze - experience until now

The content of this topic has been archived on 4 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Well , i have just installed kamikaze on my DG834v2, what i can do with openwrt is amazing, soon i will be able to retire my old P100 that is doing the routing job on my building ;p Thank you guys.
Well, this is my experience until now.
Since i compiled the ar7 image by myself , at first i forgot to add ANNEX support [newbie mistake wink ], well on the second try i did it right ...
But i am still not able to get pppoe works , and i have a few questions which maybe someone can answer to me.


1) DG834v2 has 4 ports coRJ45 and a RJ11. ifconfig -a shows eth0 with the LAN IP [so i think eth0 are the switch 4 ports] and eth1. Is eth1 the RJ11 port [wan port]?
2) Can i set vlans to each switch port ?
3) Is it correct nas0 be created even if the modem is not plugged on the dsl outlet ?
4) nas0 is auto created by the init scripts with a strange MAC, shouldn`t the nas0 mac be the same of eth1[wan] ? I read in some thread some guy was not getting pppoe work cause of the "strange" mac in nas0 , and he was able to change the mac. But ifconfig hw ether nas0 SOME_MAC always fails with "Device is in use". How can i change the MAC of this device ?
5) Should i use :
option ifname   nas0   OR    option ifname  eth1 in pppoe section ? Though both fails anyway hmm

I know my modem detects my adsl correct:

# cat /proc/avalanche/avsar_modem_stats  |grep -i rate
        US Connection Rate:     160     DS Connection Rate:     608
        Trained Path:           1       US Peak Cell Rate:      377
        Showtime Count:         1       DS Max Attainable Bit Rate: 10112 kbps
        BitSwap:                1       US Max Attainable Bit Rate:     n/a


but ppp0 never comes up.
I keep getting :
Jan  1 00:16:23 OpenWrt daemon.info pppd[730]: Plugin rp-pppoe.so loaded.
Jan  1 00:16:23 OpenWrt daemon.notice pppd[731]: pppd 2.4.3 started by root, uid 0
Jan  1 00:16:38 OpenWrt daemon.warn pppd[731]: Timeout waiting for PADO packets
Jan  1 00:16:38 OpenWrt daemon.err pppd[731]: Unable to complete PPPoE Discovery


These are my config files:


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

config interface lan
        option ifname   eth0
        option proto    static
        option ipaddr   '192.168.0.1'
        option netmask  255.255.255.0



## Example for ATM bridging.
## Useful for PPPoE or IP over ATM. Will create 'nas${unit}'
#
  config atm-bridge
        option unit     0
        option encaps   llc
        option vpi      0
        option vci      33


  config interface wan
        option ifname   nas0
        option proto    pppoe
        option username  "myname"
        option password "mypass"



# ifconfig -a


root@OpenWrt:~# ifconfig  -a
eth0      Link encap:Ethernet  HWaddr 00:0F:B5:C1:96:53 
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:951 errors:0 dropped:0 overruns:0 frame:0
          TX packets:652 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:77031 (75.2 KiB)  TX bytes:94511 (92.2 KiB)
          Interrupt:41

eth1      Link encap:Ethernet  HWaddr 00:0F:B5:C1:96:52 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:27

imq0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:30
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

imq1      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:30
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:318 (318.0 B)  TX bytes:318 (318.0 B)

nas0      Link encap:Ethernet  HWaddr 00:00:02:03:04:05 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:75 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:3150 (3.0 KiB)

   
# ipkg list




ipkg  list
base-files-ar7 - 12-r10030 -
br2684ctl - 20040226-1 -
bridge - 1.0.6-1 -
busybox - 1.8.2-1 -
dnsmasq - 2.40-1 -
dropbear - 0.50-3 -
hotplug2 - 0.9+r102-2 -
ip - 2.6.20-070313-1 -
iptables - 1.3.8-2 -
iptables-mod-conntrack - 1.3.8-2 -
iptables-mod-filter - 1.3.8-2 -
iptables-mod-imq - 1.3.8-2 -
iptables-mod-ipopt - 1.3.8-2 -
kernel - 2.6.23.1-ar7-1 -
kmod-atm - 2.6.23.1-ar7-1 -
kmod-crypto-arc4 - 2.6.23.1-ar7-1 -
kmod-crypto-core - 2.6.23.1-ar7-1 -
kmod-crypto-md5 - 2.6.23.1-ar7-1 -
kmod-crypto-sha1 - 2.6.23.1-ar7-1 -
kmod-ipt-conntrack - 2.6.23.1-ar7-1 -
kmod-ipt-extra - 2.6.23.1-ar7-1 -
kmod-ipt-filter - 2.6.23.1-ar7-1 -
kmod-ipt-imq - 2.6.23.1-ar7-1 -
kmod-ipt-ipopt - 2.6.23.1-ar7-1 -
kmod-ipt-nat - 2.6.23.1-ar7-1 -
kmod-mppe - 2.6.23.1-ar7-1 -
kmod-ppp - 2.6.23.1-ar7-1 -
kmod-ppp-synctty - 2.6.23.1-ar7-1 -
kmod-pppoa - 2.6.23.1-ar7-1 -
kmod-pppoe - 2.6.23.1-ar7-1 -
kmod-sangam-atm-annex-a - 2.6.23.1+07.02.01.00-ar7-1 -
kmod-sched - 2.6.23.1-ar7-1 -
libgcc - 4.1.2-12 -
libpcap - 0.9.4-1 -
linux-atm - 2.4.1-1 -
mtd - 6 -
ppp - 2.4.3-9 -
ppp-mod-pppoa - 2.4.3-9 -
ppp-mod-pppoe - 2.4.3-9 -
tc - 2.6.20-070313-1 -
uclibc - 0.9.29-12 -
udevtrigger - 106-1 -


# lsmod
Module                  Size  Used by    Not tainted
pppoe                  11840  0
pppox                   2256  1 pppoe
tiatm                 142288  0
pppoatm                 4448  0
ppp_synctty             9952  0
ipt_REDIRECT            1312  0
ipt_NETMAP              1312  0
ipt_TOS                 1536  0
ipt_TTL                 1568  0
xt_MARK                 1600  0
ipt_ECN                 2240  0
xt_CLASSIFY             1216  0
ipt_ttl                 1312  0
ipt_tos                 1056  0
ipt_time                2304  0
xt_tcpmss               1696  0
xt_statistic            1536  0
xt_mark                 1280  0
xt_mac                  1344  0
xt_length               1376  0
ipt_ecn                 1664  0
xt_DSCP                 1792  0
xt_dscp                 1472  0
imq                     3600  0
ipt_IMQ                 1280  0
xt_string               1600  0
ipt_ipp2p               9024  0
ipt_LOG                 6624  0
xt_CHAOS                3200  0
xt_DELUDE               3648  1
xt_TARPIT               4000  1
xt_quota                1440  0
xt_portscan             4768  0
xt_pkttype              1312  0
ipt_owner               1376  0
iptable_raw             1504  0
xt_NOTRACK              1408  0
xt_CONNMARK             1888  0
ipt_recent              7584  0
xt_helper               1760  0
xt_conntrack            2080  0
xt_connmark             1536  0
xt_connbytes            2080  0
ppp_mppe                6736  0
ppp_async              11616  0
ppp_generic            26944  6 pppoe,pppox,pppoatm,ppp_synctty,ppp_mppe,ppp_async
slhc                    6080  1 ppp_generic
crc_ccitt               1472  1 ppp_async
br2684                  7312  1
atm                    48560  5 tiatm,pppoatm,br2684
sha1                    2176  0
md5                     5056  0
arc4                    1408  0
deflate                 2592  0
ecb                     2400  0
cbc                     3456  0
blkcipher               4976  2 ecb,cbc
crypto_hash             1632  0
cryptomgr               2432  0
crypto_algapi           9728  7 sha1,md5,arc4,deflate,ecb,cbc,cryptomgr







any ideas ?

uhh pppoe looks like this. you just need to figure out the hardware interface of the telephone port.

config interface        wan
        option ifname   "eth0.1"
        option proto    pppoe
        option username foo
        option password bar
        option keepalive 10

i there a way to figure it out this ?
If IFNAME is not nas0 , what do i need nas0 for ?
thanks smile

Well , i was able to connect. Apparently i need to change the MAC ADDRESS of the nas0 interface. No idea why. Is there a beauty way to do this automatically ?
Though ppp not reconnect after a DSL OUT SYNC.
I will write a HOW-TO to dg834 modem and put on documentation section on this forum ...

IMPORTANT QUESTION
why if i uncomment the line DEBUG="echo" inside /lib/network/config.sh i brick my modem ?
if i can not debug so that line could not be there. I had to reflash twice  ...

The only reason I can think of for changing your nas0 MAC address is your ISP.  When I had bridged (no PPP) DSL, if I didn't release the DHCP lease, I couldn't switch devices.

my isp does not care about the mac since i can change to anything and it will work.

well , i can connect just for a few seconds in the latest revision hmm
My modem keeps training , and training ... almost forever...
and when it connects takes less then one minute..
The problem appears to be the latest DSL driver.
I am getting back to revision 8425. The latest one with the old driver and post results here.

How can I distinguish between DG834G and DG834Gv2? Are they both compatible (or for a big part) with OpenWrt
I'm planning to buy a new Adsl router. I know DG834G and I think it's a nice product. I would be happy to install OpenWrt on it...

There is a lable in the bottom of the unit.
I was able to fix the training problem. It was the power supply ... Every time my PC was on. I could`nt sync.

ggp81 wrote:

How can I distinguish between DG834G and DG834Gv2? Are they both compatible (or for a big part) with OpenWrt
I'm planning to buy a new Adsl router. I know DG834G and I think it's a nice product. I would be happy to install OpenWrt on it...

They look VERY different.  The former is a lot bigger.

http://kbserver.netgear.com/products/DG834.asp

Thanks smile
Is there the possibility to enter into the DG834G system using for example a serial console? I'm considering the idea to buy a DG834G in the next future, but I wouldn't like to take a chance on bricking my new AP smile
Is it easy to find the original firmware, so that I can reinstall it if OpenWrt isn't working properly for me?

ggp81 wrote:

How can I distinguish between DG834G and DG834Gv2? Are they both compatible (or for a big part) with OpenWrt
I'm planning to buy a new Adsl router. I know DG834G and I think it's a nice product. I would be happy to install OpenWrt on it...

I have both these devices and they are essentially identical internally. The v2 is much smaller (and white) and the v1 is larger and grey/silver. Both are supported by OpenWRT and take the same firmware image. I use my v1 for development (I have a serial cable attached) and the v2 for my live connection.

The ADSL connection works very well for me, but you should be aware that there are still some issues with the wireless and no VLAN's as the switch is not currently supported.

One thing to be careful of is that the v3 has a different ADAM2 bootloader which does not support FTP so currently you cannot put OpenWRT on it (though Matteo is working on this I think). The v4 is based on a completely different chipset (Broadcom) and I have no idea if this is supported. Both the v3 and v4 look the same as the v2 (small and white), but can be distinguished by the sticker on the bottom.

Hope that helps, Nick.

Thanks very much Nick, you have been very clear smile

About the serial cable you mentioned. I'm now looking at http://wiki.openwrt.org/OpenWrtDocs/Har … ear/DG834G, and so I'm going to find a proper serial cable for it. Any suggestions?

About wireless issues:
Are you able to use WPA with no issues?
Did someone of you try to use multi SSID? Are there the same problems as Broadcom (only one SSID visible)?

Thanks

(Last edited by ggp81 on 8 Jan 2008, 10:46)

ggp81 wrote:

About the serial cable you mentioned. I'm now looking at http://wiki.openwrt.org/OpenWrtDocs/Har … ear/DG834G, and so I'm going to find a proper serial cable for it. Any suggestions?

I found this page http://www.nslu2-linux.org/wiki/HowTo/AddASerialPort very useful and in fact ended up using an old Nokia DLR-3P as described about half-way down the page. I just soldered the coloured cable ends as described on this page to the pins described on the OpenWRT DG834G page.

ggp81 wrote:

About wireless issues:
Are you able to use WPA with no issues?
Did someone of you try to use multi SSID? Are there the same problems as Broadcom (only one SSID visible)?

There are currently two wireless drivers for the ACX chipset in these devices. I have only tested the mac80211 version as the old "acx" version has not been working in recent builds, although I think this may have been fixed now. Perhaps someone who has tested the fixed "acx" driver can comment on what works?

Using the mac80211 version, there is no AP functionality available and WPA client-mode is unstable. WEP client-mode works OK, but you cannot bridge the wireless and ethernet interfaces reliably. I do not think mulitple SSID's are supported with either driver.

Thanks a lot again smile

NRForbes wrote:

Perhaps someone who has tested the fixed "acx" driver can comment on what works?

I'm running the older (now fixed by Florian: https://dev.openwrt.org/changeset/10102 ) acx driver on my DG834G(v2). This works properly in master mode, but only supports WEP, but at least this works in master mode; I had no end of misery with the acx-mac80211 driver ( https://dev.openwrt.org/ticket/2864 ). As for the acx driver, it's generally ok, but sometimes I get "wlan0: tx timeout" errors which generally leads to the wireless connection being reset. Given the number of google hits on this error message, I think it is quite a common occurrence with the acx driver itself and not specific to its openwrt implementation.  Also there is no template for /sbin/wifi to use for this card (https://dev.openwrt.org/ticket/2988), hence one has set this up via commands in the rcS file at the moment.

(Last edited by nabcore on 8 Jan 2008, 19:48)

Can I ask how you reflash your router?

I have loaded a custom built firmware for my DG834 v2 and have compiled a new one to load but can't using tftp or using mtd.

Do you need to use the reset button?

Ziggy wrote:

Can I ask how you reflash your router?

I have loaded a custom built firmware for my DG834 v2 and have compiled a new one to load but can't using tftp or using mtd.

Do you need to use the reset button?

tftp nor mtd on these devices I'm afraid.  FTP only.
Please read up on the wiki:  http://wiki.openwrt.org/OpenWrtDocs/Har … ear/DG834G

There is a very small window at power up to hit the ADAM2 FTP server and that's only if you have the "my_ipaddress" variable set in NVRAM.  If you do not, then you better make/buy a serial console cable.

Want to install this on my DG834G v2.  Primarily as a wireless bridge, don't really care about the other functions. Would i have to compile my own AR7 image or is there any good ones already out there?

Cheers

Thanks KillaB. FTP to Adam2 worked a treat!

Has anyone had problems with pppoe in the new version?

I am having and error come up when running 'ifup wan'

I have standard settings enabled.

/etc/config/network:

config atm-bridge
    option unit 0
    option encaps llc
    option vpi 8
    option vci 35
    option payload routed  <this may be where the problem is caused>

config interface wan
    option ifname nas0
    option proto pppoe
    option username "user"
    option password "pass"

When running 'ifup wan' the erro "/usr/sbin/pppd: unrecognized option 'nic-nas0'" occurs. On reading up in the dev tickets it says that this issue was resolved in 10738. It appears that pppd doesn't think that nas0 is a proper device. 'ifconfig -a' shows nas0 as a device. I have had this same problem in the current (11041) and previous versions.

Any ideas?

Ziggy wrote:

/etc/config/network:

config atm-bridge
    option unit 0
    option encaps llc
    option vpi 8
    option vci 35
    option payload routed  <this may be where the problem is caused>

Change it to payload 1 or payload bridge should fix the nic-nas0 problem.

Cheers

applied in r11044

Any care to help me out with the various wireless drivers options under kernel modules :-

There are 6 choices there :-

  kmod-acx
  kmod-acx-mac80211
  kmod-ieee80211
  kmod-ieee80211-softmac
  kmod-mac80211
  kmod-net-zd1211rw

What are these and which should I pick ?

( I think it wouldn't compile if I choose kmod-acx-mac80211 ..... )

Regards

The discussion might have continued from here.