Welcome Guest 

Show/Hide Header

Welcome Guest, posting in this forum requires registration.





Pages: First << 35 36 37 [38]
Author Topic: Support for RT-N16
xproject70
Newbie
Posts: 3
Permalink
Post Re: Support for RT-N16
on: January 29, 2014, 15:35
Quote

Quote from amain on January 25, 2014, 18:54
Btw, why not installing asterisk from Debian?

apt-get install asterisk should do the job.

I've already do the apt-get approach and asterisk works very well. A lot faster than dd-wrt !!

The problem is that referring to the debian version installed, only Asterisk 1.6 is available and i would like to use asterisk 11. Another thing is that debian asterisk version has files/dirs in different path and if i plan to install freepbx probably the installation fails (i've not tried i presume that things won't install...).

Anyway a guide to integrate FreePBX with debian asterisk 1.6 is appreciated ๐Ÿ˜‰

Thanks.

xproject70
Newbie
Posts: 3
Permalink
Post Re: Support for RT-N16
on: January 29, 2014, 15:58
Quote

Quote from amain on January 25, 2014, 18:50
DebWrt normally ships with a kernel headers tar.gz. But user mod does not. You could try just downloading the full kernel sources 3.3.7 and use these to compile against. See http://dev.debwrt.net/wiki/Doc for the various options you have for (cross-)compiling.

Thanks for the reply.

Where can i find/download "kernel headers tar.gz" for 3.3.7 mipsel kernel ?

Following the documentation:

I've downloaded the dewrt-trunk:
1. svn checkout https://svn.debwrt.net/debwrt/trunk debwrt-trunk
2. make menuconfig

but i haven't found the appropriate target for my board Broadcom BCM47xx only "Broadcom BCM47xx/53xx with ARM CPU" but i have mipsel not ARM !

I've tried with stable svn:
svn checkout https://svn.debwrt.net/debwrt/branches/12.09 debwrt-12.09

but no support for BCM47XX in mipsel so i can't continue.

Please help. RT-N16 has a great board and works very well with debwrt !

amain
Administrator
Posts: 222
Permalink
Post Re: Support for RT-N16
on: January 31, 2014, 22:17
Quote

You're welcome. Seems that you could first try out any of these repos: http://packages.debian.org/search?arch=mipsel&keywords=asterisk for asterisk 11. I don't know about FreePBX but is sounds strange that it won't be able to cope with some file locations.

Follow http://dev.debwrt.net/wiki/Doc. It will help you with the various cross-compile option you have. Hint: you will need to compile a mipsel firmware, in order to get the kernel header files, but you probably won't need to install the firmware on your device. Don't know how big the asterisk code base is, but you may even be able to native compile on your RT-N16 with a little patience.

stevester
Pro
Posts: 136
Permalink
Post Re: Support for RT-N16
on: February 1, 2014, 00:11
Quote

Have you read the tutorial I posted here: http://dev.debwrt.net/wiki/DocNetUserVoip ? I think this should be a good starting point for you to get asterisk up and running from source.

EHeM
Advanced
Posts: 56
Permalink
Post interfaces.broadcom Oddity
on: June 26, 2014, 06:10
Quote

I noticed it a while ago, but what is up with the odd setup of the device "wan" in the sample interfaces.broadcom?

auto wan
iface wan inet manual
        pre-up if ! grep -q eth0 /etc/network/run/ifstate; then echo "First bring eth0 up."; false; fi
        pre-up /etc/firewall/firewall.sh start
        pre-up /sbin/ip link add link eth0 name wan type vlan id 2
        pre-up start-stop-daemon --start  \
                                --oknodo \
                                --quiet  \
                                --pidfile /var/run/dhclient.wan.pid \
                                --exec /sbin/dhclient \
                                -- -v -pf /var/run/dhclient.wan.pid -lf /var/lib/dhcp/dhclient.wan.leases -nw wan
        post-down /sbin/ip link delete wan
        post-down start-stop-daemon --stop \
                                --signal HUP \
                                --pidfile /var/run/dhclient.wan.pid \
                                --exec /sbin/dhclient
        post-down /etc/firewall/firewall.sh stop

Why use `start-stop-daemon --exec /sbin/dhclient`, instead of the more commonly used "iface wan inet dhcp"? I'm under the impression pre-up/post-down lines are still allowed with dynamic interfaces. Failing that, there is the option of using files in /etc/network/if-pre-up.d/ and /etc/network/if-post-down.d/.

EHeM
Advanced
Posts: 56
Permalink
Post Re: Support for RT-N16
on: March 11, 2015, 03:31
Quote

I've got a pretty well fully Debianized RT-N16. Newer versions of ifupdown (0.7.8 here) interpret <ethernetdevice>.<digit(s)> as VLAN interfaces and can take care of setting everything up for you. For example:

# raw ethernet interface to switch chip
auto eth0
iface eth0 inet manual
    pre-up    /sbin/ifconfig eth0 up
    pre-up    /sbin/modprobe switch-core switch-robo; exit 0
    pre-up    /bin/echo 1 > /proc/switch/eth0/reset
    pre-up    /bin/echo 1 > /proc/switch/eth0/enable_vlan
    pre-up    /bin/echo "0 8"       > /proc/switch/eth0/vlan/1/ports
    pre-up    /bin/echo "1 2 3 4 8" > /proc/switch/eth0/vlan/2/ports
    post-down /sbin/modprobe -r switch-robo switch-core; exit 0
    post-down /sbin/ifconfig eth0 down

# VLAN 1 from switch ("wan" interface)
iface eth0.1 inet dhcp

# VLAN 2 from switch ("lan" interface)
auto eth0.2
iface eth0.2 inet static
    address 192.168.66.1
    netmask 255.255.255.0

Now, where does one find documentation on `nas`? I've seen working examples (here for instance), but this tells me very little about what `nas` can do or any additional capabilities it has.

In other news, apparently with newer kernels (3.16 or so) the 802.11 interface on the Broadcom 4718 chip (Broadcom 4716 family, but actual chip is a 4718 apparently) in the RT-N16 is supportted by the brcmsmac driver. Also with the later kernel it should be possible to configure the switch using `swconfig`. Alas, I'm holding off on fighting the patch situation until I know which kernel version will be in the next stable release (right now it looks like 3.16, but this may well change).

EHeM
Advanced
Posts: 56
Permalink
Post Re: Support for RT-N16
on: March 23, 2016, 20:24
Quote

Definitely have a Debian 3.16 kernel which has had OpenWRT's patches added on working. For the RT-N16 you need to add "bgmac" to /etc/modules.

You really want Debian 8.3 (jessie) since many things work rather a bit better when the distribution matches the kernel. Of particular note, you really want access to firmware-b43-installer version 1:019-2. I'm a little bit unsure whether it is firmware-b43-installer or the tools to load the b43 firmware into the kernel, but with the newer release I'm able to get the b43 driver to work (I was having problems trying to get b43 to work on wheezy).

Now I'm onto getting b43 to work. This requires the `iw` package, instead of `wireless-tools`. One weakness of `iw` is it doesn't have a support script for `ifupdown`.

Listing of kernel 802.11 drivers (I suspect brcmsmac may work in future)
b43 driver documentation (this one works with newer kernel)
iw documentation (replaces iwconfig)

On a side note, this thread really should be moved to "Hardware ยป Broadcom BCM947xx based", instead of remaining in "Other devices".

Pages: First << 35 36 37 [38]
Mingle Forum by cartpauj
Version: 1.0.34 ; Page loaded in: 0.041 seconds.