srd wrote:

leitec wrote:

Trunk is definitely not guaranteed to work on any given day. They are doing a lot of work now that CC is branched. Given the change to a new default C library and some security settings they're now enabling it's not a good idea to run trunk on a "production" device.

I think the majority of people are not reporting what they see as most don't run production and have no worries about doing a reboot. I have two friends that also run this router and we all experience problems of some sort. With all due respect to all the on-going work, this is the most unstable router we've ever run. At the very least a reboot is somewheres in the future. Trunk is seemingly more unstable as of late.

We can say that about the stock Linksys firmware, that likes to lock up, requiring a reboot, as well.

srd wrote:

leitec wrote:

Trunk is definitely not guaranteed to work on any given day. They are doing a lot of work now that CC is branched. Given the change to a new default C library and some security settings they're now enabling it's not a good idea to run trunk on a "production" device.

I think the majority of people are not reporting what they see as most don't run production and have no worries about doing a reboot. I have two friends that also run this router and we all experience problems of some sort. With all due respect to all the on-going work, this is the most unstable router we've ever run. At the very least a reboot is somewheres in the future. Trunk is seemingly more unstable as of late.

We can say that about the stock Linksys firmware, that likes to lock up, requiring a reboot, as well.

leitec wrote:

No, it should work. Your examples have two untagged VLANs going to the same CPU port (6). At least one needs to be tagged, and a corresponding eth1.X interface must be created. I don't know how to do it in LuCI, but the config file would look something like:

config interface 'wan3'
    option ifname 'eth1.3'
    option proto 'dhcp'

and so forth, assuming you tag VLAN 3 on port 6 but not VLAN 2. VLAN 2 would continue to appear untagged on eth1.

It works!  Thank you very much!

It cannot be done in LuCI because the eth1.3 shows as eth0.3 inLuCI, but it can be set under console.

Here is my /etc/config/network file (Dual wan settings for wrt1900ac openwrt):

I have been watching this thread for many months.  I haven't yet loaded openwrt because I don’t have a USB console cable and this is my only router for the household.

kirkgbr wrote:

I have been watching this thread for many months.  I haven't yet loaded openwrt because I don’t have a USB console cable and this is my only router for the household.

If the USB to TTL cable is the hangup, you can find them online shipping from the US for $15 - $25, while from China ~ $3 - $5.  Whenever you do decide to purchase one, make sure its  3.3v cable, not a 5v (utilizing a 5v cable on a header that's 3.3v will more than likely fry components).  Also, the WRT1900ac Wiki is worth a read prior to buying it, as you'll need 2.0mm pitch pins.

This is the one I bought --  http://www.amazon.com/gp/product/B00QT7 … ge_o00_s00

If you look at the first 2 reviews they specifically refer to the Linksys 1900ac LOL  >> This seems to be a "must have" for OpenWrt users :)_

I haven't had to use mine yet as all flashes have gone well > knock on wood.

hi@experts :-)
i am looking for a solution:
i have running polipo on my wrt1900ac, but sometimes polipo crashes without errormessage and without removing it's pid and all my clients have no internet.
i need a loop something like that:
look with "ps | grep polipo"; if polipo is running, wait 3 min, if not: remove polipo.pid and start polipo
can somebody help me?
cu
p.

JW0914 wrote:

kirkgbr wrote:

I have been watching this thread for many months.  I haven't yet loaded openwrt because I don’t have a USB console cable and this is my only router for the household.

If the USB to TTL cable is the hangup, you can find them online shipping from the US for $15 - $25, while from China ~ $3 - $5.  Whenever you do decide to purchase one, make sure its  3.3v cable, not a 5v (utilizing a 5v cable on a header that's 3.3v will more than likely fry components).  Also, the WRT1900ac Wiki is worth a read prior to buying it, as you'll need 2.0mm pitch pins.

Thanks JW, my amazon order is on its way. 

Well, trunk after branching isn't for the faint-hearted.. You shouldn't have issues flashing between CC images without going to the factory image first, but trunk to CC or the other way around might cause issues. When it will stabilize a bit, you can be sure I'll announce some images here

Anyone know which retail stores have the v2 cobra?

coffeecat wrote:

leitec wrote:

No, it should work. Your examples have two untagged VLANs going to the same CPU port (6). At least one needs to be tagged, and a corresponding eth1.X interface must be created. I don't know how to do it in LuCI, but the config file would look something like:

config interface 'wan3'
    option ifname 'eth1.3'
    option proto 'dhcp'

and so forth, assuming you tag VLAN 3 on port 6 but not VLAN 2. VLAN 2 would continue to appear untagged on eth1.

It works!  Thank you very much!

It cannot be done in LuCI because the eth1.3 shows as eth0.3 inLuCI, but it can be set under console.

Here is my /etc/config/network file (Dual wan settings for wrt1900ac openwrt):

What's the purpose of utilizing two WAN inputs into the router... a failsafe?

jmschu02 wrote:

Anyone know which retail stores have the v2 cobra?

If it's been RTM'd, Linksys should provide information on it's product page where it can be purchased from.

JW0914 wrote:

jmschu02 wrote:

Anyone know which retail stores have the v2 cobra?

If it's been RTM'd, Linksys should provide information on it's product page where it can be purchased from.

Router manufacturers almost never say anything about new versions of a product. You are sometimes lucky when you can even tell the difference without opening the retail packaging. In some cases you can't even tell by looking at the product itself.

Some quick Google-fu reveals the following ways to distinguish v1 from v2, and indeed it is subtle and not explicitly noted by Linksys.

https://community.linksys.com/t5/Wirele … d-p/940588

They have the same capabilities, and the same performance, so really the thing to hope for is better driver performance. Unless I'm missing something?

Before someone points out the possibility of having more RAM.. The v1 unit's don't half the RAM available, so adding more does nothing for performance unless it also have a faster data-rate.

JW0914 wrote:

jmschu02 wrote:

Anyone know which retail stores have the v2 cobra?

If it's been RTM'd, Linksys should provide information on it's product page where it can be purchased from.

Router manufacturers almost never say anything about new versions of a product. You are sometimes lucky when you can even tell the difference without opening the retail packaging. In some cases you can't even tell by looking at the product itself.

Some quick Google-fu reveals the following ways to distinguish v1 from v2, and indeed it is subtle and not explicitly noted by Linksys.

https://community.linksys.com/t5/Wirele … d-p/940588

davidc502 wrote:

They have the same capabilities, and the same performance, so really the thing to hope for is better driver performance. Unless I'm missing something?

Before someone points out the possibility of having more RAM.. The v1 unit's don't half the RAM available, so adding more does nothing for performance unless it also have a faster data-rate.

V2 should run cooler due to a newer manufacturing process and as a result does not require a cooling fan. The CPU is a teensy bit faster too (1.3GHz vs 1.2GHz).

drawz wrote:

davidc502 wrote:

They have the same capabilities, and the same performance, so really the thing to hope for is better driver performance. Unless I'm missing something?

Before someone points out the possibility of having more RAM.. The v1 unit's don't half the RAM available, so adding more does nothing for performance unless it also have a faster data-rate.

V2 should run cooler due to a newer manufacturing process and as a result does not require a cooling fan. The CPU is a teensy bit faster too (1.3GHz vs 1.2GHz).

What is anyone going to get out of 200mhz? The router doesn't even begin to utilize what it has now. As for cooler.. what should be said is that the new CPU will run cooler under load. The current processor doesn't need a fan, until it's loaded pretty hard. Under normal use, the fan never comes on anyway.

I guess my point is, there isn't any reason to buy version 2 over version 1 unless, it's more stable. If we find that the router is more stable, then it might be worth going after. But then again, the stability problems for v1 are getting better, so this may all be a mute point anyway.