Just installed a RT-N66U with download master (currently seeding one file 1GB file only) and YES 4G.

I notice that the unifi primary WAN link will disconnect by itself
after some time.

If I reboot the asus router, then it is ok.

Why is this happening ?

I've upgraded to the lastest as you stated.

I realise that the problem maybe due to the fact that I can't rate limit the bittorrent traffic
within download master because at my traffic manager the QOS already states that the bittorrent
traffic is at the lowest.

The moment I removed the rate limit on the download master, it doesn't disconnect anymore.

That was before I upgraded the firmware from 3.0.0.4.***.1*** the one before the lastest firmware.

Thanks

Morning Asus technical,

The RT-N66U when it fail-over successfully from Unifi to YES 4G usb dongle (infomark from Korea),
it receives a 10.*.*.* ip address.

The system logs states that the DDNS client will attempt to ns1.asus.*.* to update the FQDN.

Then it states that the ip address (10.*.*.* from YES 4G WIMAX) is not valid ?

May I know why ?

I was looking at another YES 4G device called YES ZOOM gateway and in its technical specifications,
the ZOOM supports DDNS .

May I know how come ZOOM can support DDNS but not the YES 4G usb GO dongle ?

As you know when the DDNS client doesn't get updated when it fails over to the YES 4G connection,
there is no way for me to connect back to my home network.



Separately, how do I deny bittorrent traffic for users that connect to my wireless guest network or my
wireless 2.4 GHz or 5 GHz network ?


Lastly, is there a way to tell the Asus router to disallow bittorrent traffic or disable download master when it
failover to the YES 4G connection because the YES 4G is pay as you use at 9 cents for every 3MB !



Sorry, one more question, does the Asus RT-N66U support the Celcom LTE 4G usb dongle currently ?
I have a problem whereby in one particular location the YES 4G dongle is unable to get a connection.
I was thinking of using another 4G device.

Thanks.

Morning Asus technical,

I've purchased the YES Zoom and configured it at 192.168.1.3.

Connected it to one of the LAN port of N66U. (192.168.1.1) in router mode.

N66U is connected to unifi.

The problem now is that I can't ping 192.168.1.3 once I connect to the
switch port of the N66U. Is this because of the VLAN implemenation due
to the unifi setup ?

If I connect directly from my PC to the YES Zoom and ping 192.168.1.3,
it is fine.

Because YES Zoom has a DDNS client, I would like it be connected back
to N66U so that should the unifi link fail, I can still access the network from
outside.

Thanks.

The reason why I can't ping my Zoom at 192.168.1.3 is
because it was on port 4 of the RT-N66U which is configured
with a VLAN 600 for IPTV.

I tried to do a manual configuration to remove this VID 600
on the LAN port 4 because I don't use the unifi IPTV but
I can't.

Kindly advice.

I did explain previously that I was using the YES USB GO dongle on the
RT-N66U in dual-WAN mode.

And it fail over to the YES from unifi just fine.

But the ASUS ddns client says there is a failure to update the FQDN because
of the ip address given by YES .

That's why I went out to purchase Zoom because it has a DDNS client within it.

Do you want me to provide you with the error output from ASUS system log when
the DDNS fails to update correctly on the YES USB GO DONGLE ?

Yes, it is at its lastest firmware as stated above.

3.0.0.4.376_2524-g0013f52

Changing the ISP profile from unifi home to unifi-business on the LAN-IPTV tab,
I can now use port 4.


ASUSWRT RT-N66U_3.0.0.4 Sun Aug 17 09:39:28 UTC 2014
admin@RT-N66U:/tmp/home/root# ifconfig
br0 Link encap:Ethernet HWaddr 10:C3:7B:E0:EE:80
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9168 errors:0 dropped:0 overruns:0 frame:0
TX packets:12548 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1044010 (1019.5 KiB) TX bytes:8761033 (8.3 MiB)

eth0 Link encap:Ethernet HWaddr 10:C3:7B:E0:EE:80
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:428877 errors:0 dropped:0 overruns:0 frame:0
TX packets:457658 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:367510284 (350.4 MiB) TX bytes:331906274 (316.5 MiB)
Interrupt:4 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 10:C3:7B:E0:EE:80
UP BROADCAST RUNNING 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:3 Base address:0x8000

eth2 Link encap:Ethernet HWaddr 10:C3:7B:E0:EE:84
UP BROADCAST RUNNING 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:5 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:482 errors:0 dropped:0 overruns:0 frame:0
TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:62941 (61.4 KiB) TX bytes:62941 (61.4 KiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:175.139.20.189 P-t-P:175.139.23.254 Mask:255.255.255.255
UP POINTOPOINT RUNNING MULTICAST MTU:1492 Metric:1
RX packets:419167 errors:0 dropped:0 overruns:0 frame:0
TX packets:444569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:353650835 (337.2 MiB) TX bytes:311509385 (297.0 MiB)

vlan1 Link encap:Ethernet HWaddr 10:C3:7B:E0:EE:80
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9168 errors:0 dropped:0 overruns:0 frame:0
TX packets:12915 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1080682 (1.0 MiB) TX bytes:8831815 (8.4 MiB)

vlan500 Link encap:Ethernet HWaddr 00:1F:D0:97:A9:97
inet addr:169.254.58.157 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:419332 errors:0 dropped:0 overruns:0 frame:0
TX packets:444741 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:358688993 (342.0 MiB) TX bytes:323074279 (308.1 MiB)

admin@RT-N66U:/tmp/home/root# ping 192.168.1.3
PING 192.168.1.3 (192.168.1.3): 56 data bytes
64 bytes from 192.168.1.3: seq=0 ttl=64 time=16.476 ms
64 bytes from 192.168.1.3: seq=1 ttl=64 time=3.787 ms

--- 192.168.1.3 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 3.787/10.131/16.476 ms

admin@RT-N66U:/tmp/home/root# arp -a
? (192.168.1.100) at 94:DE:80:A3:C2:59 [ether] on br0
? (192.168.1.3) at F8:35:DD:6C:82:45 [ether] on br0
? (192.168.1.77) at 00:1F:D0:97:A9:97 [ether] on br0

Dear ASUSmy,

I know the dual WAN function can work with the YES 4G GO USB dongle.
But the DDNS client from asus will post an error saying the ip address from YES has an issue.

Recently YES replied me via email indirectly saying they don't support DDNS client even on their
YES Zoom even though on the box it says it does. They are very nice.

So the problem is not with Asus ddns client, rather with YES itself.

------------------------------------------------------------------------------------------------

Reference no. : SR YES-844329

Dear Valued Customer,

Thank you for contacting YesCare.

With reference to your inquiry,your email has been noted. Kindly be informed that we are no longer support for port forwarding services.

Please do not hesitate to contact us at 0183330000 if you have any further inquiries.

Always at your service

Syairah Ahmad
Customer Advocate
yescare@yes.my

--------------------------------------------------------------------------------------

Actually, I am using the YES Zoom because the antenna is omni directional and it is more
powerful than the USB GO dongle. The reception here is bad.

I will plug it to the LAN port 4 of the ASUS RT-N66U.

So I don't really understand your instruction on dual WAN and setting it at Automatic IP.
I can only set automatic IP for the primary WAN link. If I do that , I loose my unifi link.
Exactly how do I go about setting two subnets and how does this help in a failover mode for WAN ?

Can you provide some documentation to clarify the matter for me.

Asus technical,

I am unsure on how to use the Firewall_Network Services Filter.

I am trying to block access to any ports from the LAN to WAN from 1025 upwards.

I've left the first three columns empty and on the 4th column I place the 1025:65535 TCP ALL and UDP.
Is this the correct way ?

I then try to use my PC to access a website at port 8080 and it is able to do so ?
Then I try to on my bittorrent and based on the denied traffic logging, it is dropping the packets.

What is the right way to do this ?

Thanks.

Using Firmware Version:3.0.0.4.376_2524
on asus rt-n66u