Recent content by 7Knights

yes, I found very frustrated...

bond0 can access WAN/LAN, but not WLAN LAN can access WAN/WLAN checked iptables, no rules defined at all. would be vlan separation? as the only difference is, bond0 is on a different vlan? iptables -L -v Chain INPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in...

I've just have seen this in nvram nvram show | grep vlan vlan2ports=0 8u wl0_vlan_prio_mode=off wl_vlan_prio_mode=off lan_ifnames=vlan1 eth1 eth2 vlan1hwname=et0 vlan1ports=1 2 3 4 8* landevs=vlan1 wl0 wl1 size: 41891 bytes (23645 left) wl1_vlan_prio_mode=off checked wl0...

I agree, KAD. Thats why I had spent a while but still have no clue, so posted here for help. :D

Hi KAD, RMerlin I've got it working on RT-N66U 374.39-Merlin with Synology 412+ (DSM 5.0 Beta) but it brings another problem My WLAN is not able to talk to bond0 :( my pc in eth1 is okay to ping bond0, but all wireless clients are not able to ping bond0 check brctrl, all looks...