Yes, we understand that even if GLI compiles a clean CC w/ luci, we the users have to trust that GLI didn’t “sneak in” some additional code. Granted. For me (and apparently frietpan) this is fine.

My concern is not thinking that GLI cannot be trusted. It is that your closed-source code can have problems that are much less likely to be identified and fixed as compared to the OpenWRT final CC. We have already identified an earlier issue with passwords being stored as clear text in an earlier GLI GUI version.

Please compile the final OpenWRT CC with packages for use with the AR150. Many of us would use it and appreciate it!

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 12:07 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Dear Santa, could you compile CC for GLiNet AR150

Thanks for the reply Rene, but maybe you misunderstand my problem.
I have set up the router fine (2 or 3 times), but the problem is that when I try to access the ‘advanced settings’/luci, that the page keeps refreshing as I say and I cannot do anything, and I can’t seem to be able to ssh into it.

Actually, I just tried once more, I connected to the device itself (192.168.8.1) (not via my normal wifi and it’s local ip) – and now I can get into LuCI.
I hope I can still access LuCI when I am not using the AR150’s wifi though.
SSH also works too

So this is just a problem with accessing the AR150 from a network and not directly?

— I got the problem to happen again, still directly connected to the AR150’s wifi. I see in the main GL gui page that the access port is 83. But for some reason, I accessed the page before with 80/no port specified. When I add :83 to the end, I get the refresh problem.
What is happening? I’m confused!

This reply was modified 10 hours by nasna.

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 12:46 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

Well, it depends first of all there is no port 83 open on the router (webinterface works with port 80)

second, if you would like to access ssh and the webinterface from your local network you have to change the firewall settings by default incoming traffic to the wan port will be blocked.. if you want use ssh you will also have to select the port of the dropbear instance (Advanced ->System -> Administration)

I would recommend to make all changes and settings with wifi from the gl.ar150 or with a lan cable attached to it, sometimes there a strange problems using another router to configure as you can see

edit: Port 83 seems to be the port you can access from the internet if u want to access the router from ur workspace or similar. havent tried it before,

This reply was modified 10 hours by Rene.

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 1:22 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

Hi Rene.
Ok I understand the ‘problem’ now, yes I will have to specify :83 if I want to access it over my local network that the AR150 is connected to. When connected to the AR150 directly, I don’t need to give a port, good

But the problem still remains that I cannot access LuCI or ssh when I am accessing the AR150 over a network.
I don’t understand why I will have to select the port for dropbear, wouldn’t it default to 22?
And if incoming traffic via WAN would be killed, then why can I still enter the GL’s web ui, but not LuCI?

Thanks for the help and information, sorry I am not very knowledgeable about networking…!

— I think I just found what I want for SSH. – “Allow remote hosts to connect to local SSH forwarded port”
— no, it wasn’t that simple, ha (it didn’t seem to work)

This reply was modified 9 hours by nasna.
This reply was modified 9 hours by nasna.

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 1:37 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

You could try to modify the firewall settings go under advanced settings to firewall and then modify the wan interface to allow incoming traffic

i havent tried it before to use the little router in my existing network :-)

And yes, ssh is port 22 but you try it to access with the wan port and i think this could be the problem under Advanced -> System -> Administration you could select the wan interface for dropbear.. Maybe it´s working.. maybe not i dont know but i would like to help anyways! 😀

This reply was modified 9 hours by Rene.

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 2:08 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

Thanks again
Ok, well under ‘Administration’, dropbear/ssh’s interface is the default ‘unspecified’. Below I see = “Listen only on the given interface or, if unspecified, on all. So that part is not the problem, it will work over wan. But when I attempt to connect and enter the correct password, it tells me it is incorrect… yet a direct connection is fine.

Yes I will look at the firewall… but, I wouldn’t think the problem is with the firewall if I get an ‘incorrect password’ error.
Would allowing incoming wan traffic be ‘insecure’?
Maybe the solution was ‘Gateway hosts’ like I thought earlier and I did something wrong…
Thanks

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 2:28 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

Hello nasna

well i tried it.. and you´re right with port 83 and another network the site keeps refreshing under advanced settings

i will test ssh and the firewall settings and let you know if its working in a few minutes

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 2:34 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

Yes the solution for the problem is changing the firewall settings, modify the wan interface to accept incoming traffic after that you could access ssh AND the webinterface (on port 80) within your local network

This reply was modified 8 hours by Rene.

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 2:41 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

Alfie, could you check if you can access the routers webinterface on port 83 (connect the wan port to different router)and you could access the advanced settings page?

i think nasna found a bug here

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 3:14 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

Rene, very kind for testing, thanks for your time!
Ok so editing the firewall is the answer, excellent.
I will read more, I have never played with firewalls before!
I see this: https://forum.openwrt.org/viewtopic.php?id=24683
Maybe it is cleaner/safer to restrict wan incoming connections to ssh only, as opposed to letting everything in. I’m not sure if it is safe/unsafe, as I say I am new to networking

↧

Reply To: Some questions + luci problem (AR150)

December 19, 2015, 4:02 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

you should be safe i think your local router before the gl-ar does also incoming traffic blocking additional there is your password for ssh / webinterface

↧

Reply To: Some questions + luci problem (AR150)

December 20, 2015, 4:53 am

≫ Next: Reply To: Making the OpenWrt device page more complete

≪ Previous: Reply To: Some questions + luci problem (AR150)

Luci is blocked from WAN, because in Luci you can do anything easily. However, keep reflashing is a bug. It should just give a deny message. This is done in lighttpd. We will check and get back to this issue.

SSH (port 22) is blocked from WAN too. You can open it on firewall.

Why we use 83 not 80 on WAN. First reason is to differentiate LAN and WAN access. Second, a lot of ISP just blocks 80 port, but not other port by default.

↧

Reply To: Making the OpenWrt device page more complete

December 20, 2015, 4:56 am

≫ Next: Reply To: Some questions + luci problem (AR150)

≪ Previous: Reply To: Some questions + luci problem (AR150)

Thanks very much for your effort. The wiki page needs a lot of learning of the grammar.

We hope to make our docs using mdwiki first.

↧