I have to mention that the setup process is not working.
I tried to connect to 192.168.1.1 but got a request timeout even when I configured my pc to 192.168.1.2 and direct connect to one of the LAN port .
Also, I would think firmware update should be allowed to be done after you have configured the setting
I was able to connect to my router10 through the alta network program , it show as a noname device and prompt me to update the device. I didn’t managed to go through the setuo prompt and dont see any settings to do a proper setup.
Also, can someone advice if the SFP+ support DAC cabele and how do I configure one of the SFP+ as a 10G LAN port.
I wasted 4 hours fiddling with it and finally decided to revert back to my old setup.
I am also wondering if I can
a) configure a ip for the router insetad of the default 192.168.1.1
b) configure a DHCP range for the devices.
At this juncture , it is just a piece of metal junk. Have high hopes for it bit felt so letdown that a simple thing like setup can’t even work properly
It is not as easy as it could or should be. It is overly complex and complicated when it could be made very simple. It took me a week worth of wasted time to finally get a good understanding of the complexities. And I am someone coming from Enterprise Networking and Provider Networks.
However, once you get the hang of the little pains here and there it is getting to be a good little piece of kit. Granted, there is still a lot of work to be done on Alta Labs part.
Basically, I learned that if you will factory reset everything and let it update itself they work a lot better. If you do the little setup on the router and go into Control (local or Internet based) management most things can be adjusted.
Remember, Alta Labs is not a mature company. It is still very much a work in progress.
IHMO, this is a commercial product for sale. If your documention said that it can be configured this way, it should work as documented. We paid good money for the product and we are not guinea pigs to test and tell them if it working?
I totally agree. This seems to be the new norm for start-up companies. To sell and ship out half-baked equipment. The hardware from Alta Labs seems to be solid, but the software is not so much.
a) Router IP and subnet per VLAN (Router IP for Default/Native VLAN 1 corresponds to Router’s IP address on the network?)
b) Reserved IP and Pool size.
Pool size is reflected by changes in the subnet but can also be changed separately, though I don’t know how that works with respect to the subnet.
Edit:
Or, Route10 IP setting may possibly be part of LAN subnet selection in the initial setup process, and if so, Route10 firmware version 1.3z or later is required. So I guess it might not be possible until Route10 have been updated as it is a rather recent update and not very likely to be included fresh out of the box yet.
I thought there was some initial button pressing sequence that brought the route10 to a current firmware version that you could use before doing an install. (Perhaps someone from Alta Labs could comment on this.) As ebuckland81 pointed out, there are recent improvements aimed at easing the initial install. (It was pretty bad if you weren’t on the 196.168.1.x subnet)
Personally, I’m quite happy with the Route10. I have a 10gb service and I don’t think there’s anything else that would support that that’s anywhere near the Route10’s price. I also try very hard to limit the power draw of any always-on hardware that I run. The Route10 is quite miserly in that regard.
Yes, the software is still a bit raw - and if you buy it without knowing that, you might in store for an unpleasant surprise. It’s all built on top of openwrt though. So if you’re not willing for Alta Labs to implement some feature, chances are, you can patch it in yourself with CLI startup scripts.
@tssohn Our very first batch of Route10s did not like to be setup within an existing subnet of 192.168.1.1. The units that are shipping out to distributors now have resolved that issue. Based on what I am reading, it sounds like you may have received one of the units with the first version of firmware where that was an issue. To @techknight1@ebuckland81@jack points, a power on reset (PoR) where you hold the factory reset button, will trigger the Route10 to pull a later version of firmware that should resolve this issue.
I apologize for the frustration you experienced, but if you can see past that, I think you will pleasantly surprised with the performance and features available in Route10.
I’m always mistyping ip addresses. Actually what I was trying to point out was that setup used to be difficult when trying to install into a subnet other than 192.168.1.1
I appreciate all the responses to my post. I have upgrade the router to the latest firmware and am able to access the setup menu after my pc got a 192.168.0.10 address from router10 and I am able to access the setup menu from 192.168.0.1
I have not do a cutover to the router10 having fail the first time and going to wait until weekends to do so.
Have anyone use a copper DAC cable inserted into the spf+ port ? I observe that it don’t seem to work as there is no link activity light. When I use a spf+ optical module , the link activity light is working. I am trying to replace my pfsense firewall which one of the spf+ interface is not working with the router 10. I have isp 10gb broadband and my home network is a combination of 2.5gb and 10gb( including wireless AP)
There are a few topics on the matter of DACs. Maybe some of them can shine some light on compatibility/incompatibility regarding your specific case/DAC. Here are a couple topics, though there may be more out there:
If it doesn’t work, also report on the DAC model and see if Alta can possibly work on compatibility.
OK. I noted that you use a FS.com DAC cable. will buy one to try
I manage to connect the Router10 using WAN2 (SFP+) and configure WAN1 as LAN port .
The strange thing is that Router10 auto assigned me a 192.168.0.x subnet but in the management portal on the internet is showing VLAN1 the DHCP scope is 192.168.1.10 ( see below)
Also, using the Apple apps, I cannot see the IPS under Firewall but I can see it on the management portal in the internet.
Edit made. Moving too fast. Nice catch 