OpenWrt Forum Archive

Topic: davidc502 1900ac 3200acm builds

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

farchord wrote:
davidc502 wrote:
KShion619 wrote:

Are the steps taken in OpenWRT's Wiki Page correct for enabling dnscrypt on the 4.4 build of your V1 LEDE (r4049-9412fc2) if not can you post the steps assuming I'm currently at the default configuration?

The steps on the wiki should work, as it worked when I went through them. The only issue was I couldn't just use 1 dns forward IP as 2 are needed  or it just didn't work.

Btw I thought I'd offer this, but we're underusing a box at work where I could probably set you up a VM for compiling new builds if you want.... Dual E5-2620 CPUs.... 130gb ram... etc....?

I mean ofc you wouldn't get all that but I could probably allocate you almost 32gb of ram without it even hurting us one little bit...

Wow!  Well, I bought a new Ryzen processor with 32Gigs of RAM, Gigabyte motherboad, and a few other things... At this point a CPU cooler and SSD are still needed, so I'm still a couple months out on having it finished. I've been buying components a bit at a time so the wallet isn't busted any more than it already is wink

Appreciate the offer though...

(Last edited by davidc502 on 3 May 2017, 15:27)

AddRemover wrote:

I can't start wlan0 on almost all channels, except few first and one last

Here is what I see in the syslog:

Wed May  3 16:49:56 2017 daemon.notice hostapd: wlan0: interface state ENABLED->DISABLED
Wed May  3 16:49:56 2017 daemon.notice hostapd: wlan0: AP-DISABLED
Wed May  3 16:49:56 2017 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Wed May  3 16:49:56 2017 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Wed May  3 16:49:56 2017 kern.info kernel: [ 5184.202633] device wlan0 left promiscuous mode
Wed May  3 16:49:56 2017 kern.info kernel: [ 5184.207137] br-lan: port 2(wlan0) entered disabled state
Wed May  3 16:49:56 2017 kern.debug kernel: [ 5184.222495] ieee80211 phy0: change: 0x40
Wed May  3 16:49:56 2017 kern.debug kernel: [ 5184.327488] ieee80211 phy0: change: 0x100
Wed May  3 16:49:56 2017 daemon.notice netifd: Network device 'wlan0' link is down
Wed May  3 16:49:56 2017 daemon.err modprobe: xt_multiport is already loaded
Wed May  3 16:49:56 2017 daemon.err modprobe: xt_connmark is already loaded
Wed May  3 16:49:56 2017 daemon.err modprobe: xt_comment is already loaded
Wed May  3 16:49:56 2017 daemon.err modprobe: xt_length is already loaded
Wed May  3 16:49:57 2017 daemon.notice netifd: radio0 (17266): command failed: Not supported (-95)
Wed May  3 16:49:57 2017 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Wed May  3 16:49:58 2017 kern.debug kernel: [ 5185.814469] ieee80211 phy0: change: 0xffffffff
Wed May  3 16:49:58 2017 kern.info kernel: [ 5185.922621] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Wed May  3 16:49:58 2017 kern.info kernel: [ 5185.929328] br-lan: port 2(wlan0) entered blocking state
Wed May  3 16:49:58 2017 kern.info kernel: [ 5185.934673] br-lan: port 2(wlan0) entered disabled state
Wed May  3 16:49:58 2017 kern.info kernel: [ 5185.940119] device wlan0 entered promiscuous mode
Wed May  3 16:49:58 2017 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Wed May  3 16:50:02 2017 daemon.notice hostapd: handle_probe_req: send failed
Wed May  3 16:50:02 2017 daemon.notice hostapd: handle_probe_req: send failed
Wed May  3 16:50:03 2017 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->HT_SCAN
Wed May  3 16:50:03 2017 kern.debug kernel: [ 5190.945418] ieee80211 phy0: change: 0x100
Wed May  3 16:50:03 2017 kern.debug kernel: [ 5190.954455] ieee80211 phy0: change: 0x40
Wed May  3 16:50:03 2017 kern.debug kernel: [ 5191.162360] ieee80211 phy0: change: 0x40
Wed May  3 16:50:03 2017 daemon.notice hostapd: wlan0: interface state HT_SCAN->DFS
Wed May  3 16:50:03 2017 daemon.notice hostapd: wlan0: DFS-CAC-START freq=5260 chan=52 sec_chan=1, width=1, seg0=58, seg1=0, cac_time=60s
Wed May  3 16:50:03 2017 daemon.err hostapd: DFS start_dfs_cac() failed, -1
Wed May  3 16:50:03 2017 daemon.err hostapd: Interface initialization failed
Wed May  3 16:50:03 2017 daemon.notice hostapd: wlan0: interface state DFS->DISABLED
Wed May  3 16:50:03 2017 daemon.notice hostapd: wlan0: AP-DISABLED
Wed May  3 16:50:03 2017 daemon.notice hostapd: wlan0: interface state DISABLED->DISABLED
Wed May  3 16:50:03 2017 daemon.notice hostapd: wlan0: AP-DISABLED
Wed May  3 16:50:03 2017 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Wed May  3 16:50:03 2017 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Wed May  3 16:50:03 2017 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Wed May  3 16:50:03 2017 kern.debug kernel: [ 5191.372409] ieee80211 phy0: change: 0x40
Wed May  3 16:50:03 2017 kern.info kernel: [ 5191.422445] device wlan0 left promiscuous mode
Wed May  3 16:50:03 2017 kern.info kernel: [ 5191.426950] br-lan: port 2(wlan0) entered disabled state
Wed May  3 16:50:03 2017 kern.debug kernel: [ 5191.476391] ieee80211 phy0: change: 0x100
Wed May  3 16:50:03 2017 daemon.notice hostapd: ELOOP: remaining socket: sock=22 eloop_data=0xa5db0 user_data=0 handler=0x353dc
Wed May  3 16:50:03 2017 daemon.notice netifd: radio0 (17266): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 16561 path ()
Wed May  3 16:50:03 2017 kern.debug kernel: [ 5191.650373] ieee80211 phy0: change: 0xffffffff
Wed May  3 16:50:03 2017 kern.info kernel: [ 5191.759395] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

When wlan0 is started OK:

Wed May  3 16:49:20 2017 daemon.err modprobe: xt_multiport is already loaded
Wed May  3 16:49:20 2017 daemon.err modprobe: xt_connmark is already loaded
Wed May  3 16:49:20 2017 daemon.err modprobe: xt_comment is already loaded
Wed May  3 16:49:20 2017 daemon.err modprobe: xt_length is already loaded
Wed May  3 16:49:20 2017 daemon.notice netifd: radio0 (16036): command failed: Not supported (-95)
Wed May  3 16:49:20 2017 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Wed May  3 16:49:21 2017 kern.debug kernel: [ 5148.861901] ieee80211 phy0: change: 0xffffffff
Wed May  3 16:49:21 2017 kern.info kernel: [ 5148.971099] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Wed May  3 16:49:21 2017 kern.info kernel: [ 5148.977816] br-lan: port 2(wlan0) entered blocking state
Wed May  3 16:49:21 2017 kern.info kernel: [ 5148.983167] br-lan: port 2(wlan0) entered disabled state
Wed May  3 16:49:21 2017 kern.info kernel: [ 5148.988612] device wlan0 entered promiscuous mode
Wed May  3 16:49:21 2017 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Wed May  3 16:49:26 2017 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->HT_SCAN
Wed May  3 16:49:26 2017 kern.debug kernel: [ 5153.997427] ieee80211 phy0: change: 0x100
Wed May  3 16:49:26 2017 kern.debug kernel: [ 5154.006464] ieee80211 phy0: change: 0x60
Wed May  3 16:49:26 2017 kern.debug kernel: [ 5154.222826] ieee80211 phy0: change: 0x40
Wed May  3 16:49:26 2017 kern.debug kernel: [ 5154.432827] ieee80211 phy0: change: 0x60
Wed May  3 16:49:26 2017 daemon.err hostapd: Using interface wlan0 with hwaddr 60:38:e0:xx:xx:xx and ssid "XXXXX"
Wed May  3 16:49:26 2017 kern.debug kernel: [ 5154.532826] ieee80211 phy0: change: 0x100
Wed May  3 16:49:26 2017 kern.debug kernel: [ 5154.588106] ieee80211 phy0: change: 0x100
Wed May  3 16:49:26 2017 kern.debug kernel: [ 5154.597126] ieee80211 phy0: change: 0x62
Wed May  3 16:49:26 2017 kern.info kernel: [ 5154.762828] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Wed May  3 16:49:26 2017 kern.info kernel: [ 5154.769262] br-lan: port 2(wlan0) entered blocking state
Wed May  3 16:49:26 2017 kern.info kernel: [ 5154.774603] br-lan: port 2(wlan0) entered forwarding state
Wed May  3 16:49:27 2017 daemon.notice hostapd: wlan0: interface state HT_SCAN->ENABLED
Wed May  3 16:49:27 2017 daemon.notice hostapd: wlan0: AP-ENABLED
Wed May  3 16:49:27 2017 daemon.notice netifd: Network device 'wlan0' link is up

Appears to be DFS issue. The channel width 80Hgz. With 40 it's same.

Do you have the country set up, so DFS can be determined?

beginner67890 wrote:
ekstse wrote:

hi david, where can i change the cert when i login 192.168.1.1/cgi-bin/luci/ ?

I'm not david, sorry.

The cert is located here:

Thanks! smile

davidc502 wrote:

Do you have the country set up, so DFS can be determined?

I've set country "Russia" which is true.

It turns out so?

root@wrt3200acm:~# iw reg get
country 98: DFS-UNSET
        (2402 - 2472 @ 40), (N/A, 20), (N/A)
        (5170 - 5250 @ 80), (N/A, 20), (N/A)
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
        (5650 - 5730 @ 80), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)

I have trouble with the wrt3200acm in combination with apple homekit devices. I seems that the multicast traffic will be dropped. I don't know if this behaviour is coming with the new WLAN driver (10.3.4.0-20170421) or with other default values within the new LEDE version.

Kernel version  4.9.20
WiFi driver 10.3.4.0-20170421

muth wrote:

I have trouble with the wrt3200acm in combination with apple homekit devices. I seems that the multicast traffic will be dropped. I don't know if this behaviour is coming with the new WLAN driver (10.3.4.0-20170421) or with other default values within the new LEDE version.

Kernel version  4.9.20
WiFi driver 10.3.4.0-20170421

Maybe allow IGMP through the firewall?

Just a guess

muth wrote:

I have trouble with the wrt3200acm in combination with apple homekit devices. I seems that the multicast traffic will be dropped. I don't know if this behaviour is coming with the new WLAN driver (10.3.4.0-20170421) or with other default values within the new LEDE version.

Kernel version  4.9.20
WiFi driver 10.3.4.0-20170421

If this is WLAN behavior with multicast then it should be reported. If you haven't already create a gethub account and create a new issue. Be sure to document as much behavior and details as possible.

I'm assuming you are on the 3200acm because that's the driver that is currently being worked on.

If not on 3200acm then there's probably another issue.

https://github.com/kaloz/mwlwifi/issues

davidc502 wrote:
muth wrote:

I have trouble with the wrt3200acm in combination with apple homekit devices. I seems that the multicast traffic will be dropped. I don't know if this behaviour is coming with the new WLAN driver (10.3.4.0-20170421) or with other default values within the new LEDE version.

Kernel version  4.9.20
WiFi driver 10.3.4.0-20170421

If this is WLAN behavior with multicast then it should be reported. If you haven't already create a gethub account and create a new issue. Be sure to document as much behavior and details as possible.

I'm assuming you are on the 3200acm because that's the driver that is currently being worked on.

If not on 3200acm then there's probably another issue.

https://github.com/kaloz/mwlwifi/issues

I think it has been reported already:
https://github.com/kaloz/mwlwifi/issues/36

starcms wrote:

You can use this script in SSH to easily switch between the two partitions.

#!/bin/sh
# Hacked from /lib/upgrade/linksys.sh (then taken from anomeome and hacked even further)

cur_boot_part=`/usr/sbin/fw_printenv -n boot_part`
target_firmware=""
if [ "$cur_boot_part" = "1" ]
then
    target_firmware="Switching to Kernel/Partition 2"
    fw_setenv boot_part 2
    fw_setenv bootcmd "run altnandboot"
elif [ "$cur_boot_part" = "2" ]
then
    target_firmware="Switching to Kernel/Partition 1"
    fw_setenv boot_part 1
    fw_setenv bootcmd "run nandboot"
fi
# Re-enable recovery so we get back in case the new firmware ist kaput
fw_setenv auto_recovery yes
echo "$target_firmware"

# Add option to reboot now or later
read -p "Are you ready to reboot now? y or n = " CONT
if [ "$CONT" = "y" ]; then
    echo "Rebooting now"
    reboot
elif [ "$CONT" = "yes" ]; then
    echo "Rebooting now"
    reboot
else
    echo "Exiting for manual reboot"
fi

Edit: This can only be used when in LEDE/OpenWRT.  When in the Linksys firmware, you could try the power reset trick that was linked, but it's not possible to SSH with the Linksys firmware.

Hi Guys,

Would you mind to help me out on this ?

I'm with LEDE (davidc502) for 1900AC  V1 on Partition 2 ( working very well ) and Linksys on Partition 1.

Ok, i used the script to switch from 2 -> to 1. Working fine too, so i flashed LEDE on Partition 1. But, when i used the script once again to go back to Partition 2. When i finished to boot, it goes back Linksys Firmware ( it was not exactly the one i was using but a different copy of Linksys. Also working.

If i use the trick with power to switch, it goes back to LEDE. OK no problem. While on Linksys, i once again flashed the LEDE, configured ( using another theme - material - just to be sure its a different partition ) used the script, to switch, and i don't have 2 LEDEs, i have  LEDE and Linksys.

What i'm doing wrong ?

(Last edited by ygor.almeida on 4 May 2017, 02:59)

It's a round-robin.

davidc502 wrote:
ygor.almeida wrote:

I'm using your build with WRT1900ac v1. Working pretty well here. Keeping with the last build.

... I just connected an USB 3.0 External drive ( Samsung 2TB ) to the router - with ext4 format. But i feel samba pretty slow. Read is about 45 and write only 30 over LAN cable. Did i missed something? isn't usb 3.0 be able to perform better.

I saw other guys screens about 110 at reading from router to desktop and about 50 from desktop do router (writting)

Any clues ??

Can you test NTFS?

Format the drive to NTFS.

Install -  kmod-fs-ntfs   
Install - ntfs-3g
Mount Example :  ntfs-3g /dev/sda /mnt/usb

Then Make sure the samba share is active and test mapping the drive, and then test transferring some files.

Huum,

So i gived it a try...

http://i.imgur.com/VmiD9Sg.png

This is with NTFS from my SSD Computer in Gigabit lan - to USB 3.0 Seagate HDD 2TB (ntfs-3g) format

Write is about 6 or 7 MB/s, while read is about 20 MB/s.

http://i.imgur.com/U2cBgZe.png

This is with EXT4 from my SSD computer in Gigabit lan - to USB 3.0 Seagate HDD 2TB ( ext4 ) format

Write is about 45 MB/s, while read is about 38 ~ 42 MB/s ext4.

Very good ... i can say it's very nice ... but is far away from other results i see in forum.
http://i.imgur.com/Jfile33.png

Like this is from the now ( discontinued cybernook post )

Isn't it possible to reach that speed ? what is wrong with my setup.

Thx for your help

ygor.almeida wrote:
davidc502 wrote:
ygor.almeida wrote:

I'm using your build with WRT1900ac v1. Working pretty well here. Keeping with the last build.

... I just connected an USB 3.0 External drive ( Samsung 2TB ) to the router - with ext4 format. But i feel samba pretty slow. Read is about 45 and write only 30 over LAN cable. Did i missed something? isn't usb 3.0 be able to perform better.

I saw other guys screens about 110 at reading from router to desktop and about 50 from desktop do router (writting)

Any clues ??

Can you test NTFS?

Format the drive to NTFS.

Install -  kmod-fs-ntfs   
Install - ntfs-3g
Mount Example :  ntfs-3g /dev/sda /mnt/usb

Then Make sure the samba share is active and test mapping the drive, and then test transferring some files.

Huum,

So i gived it a try...

This is with NTFS from my SSD Computer in Gigabit lan - to USB 3.0 Seagate HDD 2TB (ntfs-3g) format

Write is about 6 or 7 MB/s, while read is about 20 MB/s.

This is with EXT4 from my SSD computer in Gigabit lan - to USB 3.0 Seagate HDD 2TB ( ext4 ) format

Write is about 45 MB/s, while read is about 38 ~ 42 MB/s ext4.

Very good ... i can say it's very nice ... but is far away from other results i see in forum.

Like this is from the now ( discontinued cybernook post )

Isn't it possible to reach that speed ? what is wrong with my setup.

Thx for your help

Well, NTFS is supposed to run slower than ext4, always, as it's not optimized for a linux environment. Take a look at this benchmarks: https://www.phoronix.com/scan.php?page= … 7-FS-5-Way

Also, I think you can remove the  kmod-fs-ntfs module and just let ntfs-3g handle everything. Also install ntfs-3g-utils so you can make some more tests, get info on the partitions, etc.

farchord wrote:
muth wrote:

I have trouble with the wrt3200acm in combination with apple homekit devices. I seems that the multicast traffic will be dropped. I don't know if this behaviour is coming with the new WLAN driver (10.3.4.0-20170421) or with other default values within the new LEDE version.

Kernel version  4.9.20
WiFi driver 10.3.4.0-20170421

Maybe allow IGMP through the firewall?

Just a guess

Already done. :-/

AddRemover wrote:
davidc502 wrote:

Do you have the country set up, so DFS can be determined?

I've set country "Russia" which is true.

It's more reasonable to set Bolivia (BO) or Bermudes (BM) for 2.4G - 30dbm limit.
Don't sure Russia have 30 for low-5G as well - it's 20dmb only AFAIK, so use Germany or so for 5G.
Можешь не благодарить.

ygor.almeida wrote:

I'm using your build with WRT1900ac v1. Working pretty well here. Keeping with the last build.

... I just connected an USB 3.0 External drive ( Samsung 2TB ) to the router - with ext4 format. But i feel samba pretty slow. Read is about 45 and write only 30 over LAN cable. Did i missed something? isn't usb 3.0 be able to perform better.

I saw other guys screens about 110 at reading from router to desktop and about 50 from desktop do router (writting)

Any clues ??

Some controllers in SATA-USB can do this, i see examples before even to 5Mb for read at usb3.
I strongly recommend use e-SATA/USB cable instead, you can get full speed for $5 or less only.
I have the drive connected this way, 110Mb hdinfo, 80/60 Ethernet, 30 5G wifi.
I have about 30% less then use WD usb3 box.

Guys if you are experiencing the memory leak on the 3200ACM, disable all the wifi interfaces but the 5ghz one. That should halt the leak. It does for me anyway.

kaloz is working on a fix.

@david Here's the IPTV howto. This is for me running on Bell Fibe in Canada, and includes IPTV and Internet. I'll add the general ideas behind the configuration:

Software Requirements:

  • IGMPProxy

General idea behind the configuration
This configuration's end goal boils down to the following:
1- Setup the switch to have two different vlans (One for Internet, one for TV) running on the appropriate Vlan IDs (For Bell Fibe in Canada, Internet runs on Vlan 35; and TV on Vlan 36). This could also be done on the same lan as your other devices, but then all your devices will get flooded with the multicast packets. Maybe not the best idea. Note that in the example below, my TV receiver is plugged into port #4. If you have more than one receiver, you can change the port assignment under the switches. TV Receivers on Wifi is not configured in this setup and will require manual investigation (I do not have wifi receivers).
2- There should be 6 total Interfaces: WAN (PPPoE runs over it), PPPoE (I named it PPPoE-Bell because of my ISP name, you can rename it if you'd like), lan (My main Lan), TVLan (Self-explanatory) and TV (Vlan36 Wan). Main lan is set on 192.168.1.x while TV is set to 192.168.2.x. Note that I have to clone my ISP provided modem's MAC on the main LAN for my internet to work.
3- Added IGMP Proxy. Configuration is pretty self-explanatory. If you renamed the interfaces you'll need to modify this config as well.
4- (Depends on your ISP) Bell runs on IGMP v2, so I had to add this line into /etc/sysctl.conf:

net.ipv4.conf.all.force_igmp_version=2

You can find which version your TV provider runs on by listening on the TV Lan interface with tcpdump and check which IGMP version it runs on. You should see something like:

igmp v2 report

5- Added igmp_snooping option on the TV Lan interface
6- Setup the firewall to let everything from the TV Wan to go to the TV Lan (Not like you really gotta protect it, but in theory you could only allow UDP and Multicast. Up to you.
7- Find your default TV route. That's where this gets a little difficult. I notice that LEDE keeps the last DHCP lease gateway only. So you can probably work this in your favor by going under Interfaces and 'Connect'ing the vlan 36 interface. This will kill your internet, but then if you route -n in SSH, you will be able to see your TV gateway. Add that gateway as a static route, reboot the router (Or reconnect your internet interface) and you're good to go.

Configurations

/etc/config/igmpproxy:

config igmpproxy
        option quickleave 1
#       option verbose 2

config phyint wan
        option network TV
        option direction upstream
# NOTE: Modify your altnets to point to your ISP's main network. 224.0.0.0/4 is the broadcasting mask so it can
# probably be retained.
        list altnet 224.0.0.0/4
        list altnet 10.0.0.0/8

config phyint lan
        option network TVLan
        option direction downstream
        list altnet 192.168.2.0/16

/etc/config/network:

NOTE: You can remove the PPPoE connection if you don't need it. You need to add your modem's MAC address at the appropriate place, as well as your PPPoE login information (If applicable) I also deleted the static route from the config as it won't work for you.

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 'fde4:d132:9e84::/48'

config interface 'lan'
        option type 'bridge'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option _orig_ifname 'eth0.1 radio0.network1 radio1.network1 radio2.network1'
        option _orig_bridge 'true'
        option dns '8.8.8.8 8.8.4.4'
        option ifname 'eth0.1'

config interface 'wan'
        option proto 'dhcp'
        option macaddr 'YOUR MODEMS MAC ADDRESS'
        option type 'bridge'
        option _orig_ifname 'eth1.2'
        option _orig_bridge 'true'
        option ifname 'eth1.2'

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

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

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '4t 6t'
        option vid '35'

config switch_vlan
        option device 'switch0'
        option vlan '3'
        option vid '36'
        option ports '4t 5t'

config interface 'Bell'
        option proto 'pppoe'
        option ifname 'eth1.35'
        option username 'PPPOELOGIN'
        option password 'PPPOEPASSWORD'
        option ipv6 'auto'

config interface 'TV'
        option _orig_ifname 'eth1.36'
        option _orig_bridge 'true'
        option proto 'dhcp'
        option ifname 'eth0.36'
        option force_link '1'
        option broadcast '1'

config switch_vlan
        option device 'switch0'
        option vlan '4'
        option ports '0 6t'
        option vid '3'

config interface 'TVLan'
        option proto 'static'
        option netmask '255.255.255.0'
        option igmp_snooping '1'
        option _orig_ifname 'eth1.3'
        option _orig_bridge 'true'
        option ifname 'eth1.3'
        option ipaddr '192.168.2.1'

/etc/config/firewall:

NOTE: Pretty standard here. Allow traffic from main LAN to internet (But no forward or input). On the TV network,
allow everything. Again -- this can probably be limited more.

config rule
        option target 'ACCEPT'
        option dest 'lan'
        option name 'All'
        option src 'Internet'

config rule
        option target 'ACCEPT'
        option src 'lan'
        option dest 'Internet'
        option name 'All'

config defaults
        option syn_flood '1'
        option output 'ACCEPT'
        option input 'ACCEPT'
        option forward 'REJECT'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        option network 'lan'
        option masq '1'
        option mtu_fix '1'

config zone
        option name 'wan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option masq '1'
        option mtu_fix '1'
        option network 'wan'

config include
        option path '/etc/firewall.user'

config zone
        option output 'ACCEPT'
        option name 'Internet'
        option network 'Bell'
        option masq '1'
        option mtu_fix '1'
        option input 'REJECT'
        option forward 'REJECT'

config forwarding
        option dest 'lan'
        option src 'Internet'

config forwarding
        option dest 'Internet'
        option src 'wan'

config forwarding
        option dest 'lan'
        option src 'wan'

config forwarding
        option dest 'wan'
        option src 'Internet'

config zone
        option input 'ACCEPT'
        option forward 'ACCEPT'
        option output 'ACCEPT'
        option network 'TV'
        option name 'TV'
        option masq '1'
        option mtu_fix '1'

config zone
        option name 'TVLan'
        option input 'ACCEPT'
        option forward 'ACCEPT'
        option output 'ACCEPT'
        option network 'TVLan'
        option masq '1'
        option mtu_fix '1'

config forwarding
        option dest 'Internet'
        option src 'lan'

config forwarding
        option dest 'wan'
        option src 'lan'

config forwarding
        option dest 'Internet'
        option src 'TVLan'

config forwarding
        option dest 'TV'
        option src 'TVLan'

config forwarding
        option dest 'wan'
        option src 'TVLan'

config forwarding
        option dest 'TVLan'
        option src 'TV'

config forwarding
        option dest 'TVLan'
        option src 'wan'

config include 'miniupnpd'
        option type 'script'
        option path '/usr/share/miniupnpd/firewall.include'
        option family 'any'
        option reload '1'

config rule
        option src 'TV'
        option proto 'igmp'
        option target 'ACCEPT'

config rule
        option src 'TV'
        option proto 'udp'
        option dest 'TVLan'
        option dest_ip '224.0.0.0/4'
        option target 'ACCEPT'

config rule
        option src 'TV'
        option proto 'udp'
        option dest_ip '224.0.0.0/4'
        option target 'ACCEPT'
farchord wrote:

@david Here's the IPTV howto. This is for me running on Bell Fibe in Canada, and includes IPTV and Internet. I'll add the general ideas behind the configuration:

Great guide, farchord. It should make easy for anyone to make their IPTV work.

I'd like to add just a couple of things. And, as I said before, I'm no multicast expert, just an user with some years fighting with my IPTV smile.

First. My TV (ethernet connected) is in the same VLAN as anything else at home. That way I can browse Internet (or any other Internet related thing). I think that IGMP snooping (forgive me if it isn't so) prevents multicast flooding in any other device not using IPTV. I never had a problem with this, and the TV kitchen (2.4 WiFi) can also watch our IPTV channels without troubling anything else.

Second. If you have problems with wireless clients you can use "udpxy". Udpxy requires some configuration but once set up you can have all your multicast channels working through UDP, so no flooding. You can even create a playlist for a upnp server and distribute IPTV all around the house for any DLNA device. It may require some trial and error, but it works fine, at least if your ISP is not moving and changing channels frequently (as mine does...).

Just my 2 cents.

And again, congratulations and thanks for your guide,

davidc502 wrote:
anielarias wrote:
davidc502 wrote:

The first step before powering off/on is to use the reset button.

   Reset router by pressing reset button until PWR light starts to flash {should take ~ 15 seconds}

hi  davidc502 i have few questions
1) can i use qos/ sqm qos together ?
2) i have 250/30 speed connection yet when i im trying to download a movie to my phone from my ftp server the upload speed is slow. ?
3) how can i keep all pakages when upgrading ?

#1. Unknown.  I don't know, but would assume not. However, we know what happens when we assume.
#2. Is the download speed just as slow to a wired PC?
#3. What is being upgraded? Sock Firmware? DD-WRT? OpenWrt? Or perhaps a earlier version of LEDE?

hello davidc502 anyway to go back to factory without a serial cable, note: i have wrt3200acm and i believe both partitions have lede install.

anielarias wrote:
davidc502 wrote:
anielarias wrote:

hi  davidc502 i have few questions
1) can i use qos/ sqm qos together ?
2) i have 250/30 speed connection yet when i im trying to download a movie to my phone from my ftp server the upload speed is slow. ?
3) how can i keep all pakages when upgrading ?

#1. Unknown.  I don't know, but would assume not. However, we know what happens when we assume.
#2. Is the download speed just as slow to a wired PC?
#3. What is being upgraded? Sock Firmware? DD-WRT? OpenWrt? Or perhaps a earlier version of LEDE?

hello davidc502 anyway to go back to factory without a serial cable, note: i have wrt3200acm and i believe both partitions have lede install.

https://wiki.openwrt.org/toh/linksys/wr … erequisite

Scroll down to the 3200acm, there's prerequisite commands to run and a howto to flash the default linksys firmware back in.

Question:

Is everyone liking Darkmatter LuCi?

Seems there have been some downloads of modern which seem to indicate users changing?

@farchord

Will go through the instructions to see if I can get IPTV working with my ISP.  This should give me time to get my head wrapped around everything that needs to be done.

Also, I know the guide so far isn't set in stone, so I would like to have other input as to what can be improved for clarity/ease on implementing or anything that could help the success for people trying to follow it.

appreciate the work on this...

davidc502 wrote:

Question:

Is everyone liking Darkmatter LuCi?

Seems there have been some downloads of modern which seem to indicate users changing?

I like it. Works well on an iPad.

davidc502 wrote:

Question:

Is everyone liking Darkmatter LuCi?

Seems there have been some downloads of modern which seem to indicate users changing?


Darkmatter is awesome!