riskable
11-08-2009, 03:33 PM
I've only received feedback from TWO people. Anyone try out PyCI yet?
View Full Version : Anyone get a chance to try my firmware yet?
rakpatel
11-08-2009, 09:39 PM
for PyCI also I am able to get ping from 192.168.1.20 but not able to login through port 80. Any Idea.... or can you describe the procedure. I had read the procedure and tried excatly what they said.... But no luck
ubnt-115
11-08-2009, 11:29 PM
for PyCI also I am able to get ping from 192.168.1.20 but not able to login through port 80. Any Idea.... or can you describe the procedure. I had read the procedure and tried excatly what they said.... But no luck
NETSHe starts dhpclient on eth1. Please, connect to eth1 and run wireshark to see dhcp-requests. (You can obtain second door to system, if you'll have dhcp server)
Reflash firmware, if you did not seen anything.
NETSHe starts dhpclient on eth1. Please, connect to eth1 and run wireshark to see dhcp-requests. (You can obtain second door to system, if you'll have dhcp server)
Reflash firmware, if you did not seen anything.
rakpatel
11-09-2009, 12:41 AM
hi ubnt-115,
I was able to loging to NETSHe by 192.168.24.1 IP (Which is RS IP). Now let me try with PyCI again which requires by default 443 port means https://192.168.1.20
I was able to loging to NETSHe by 192.168.24.1 IP (Which is RS IP). Now let me try with PyCI again which requires by default 443 port means https://192.168.1.20
rakpatel
11-09-2009, 01:27 AM
riskable,
I am getting loging prompt on https://192.168.1.20 but not let me in with root and no password. Than I change password by hyper terminal and than try again withh user name root and password ubnt but still it did not allow me to login
I am getting loging prompt on https://192.168.1.20 but not let me in with root and no password. Than I change password by hyper terminal and than try again withh user name root and password ubnt but still it did not allow me to login
pturkey
11-09-2009, 04:16 PM
I am also not able to login using root with no password.
If anyone knows the trick please inform the rest of us.
If anyone knows the trick please inform the rest of us.
rakpatel
11-09-2009, 08:36 PM
pturkey,
I am able to login by doing following,
1 Internet security add 192.168.1.20 as trust site
2 By SSH change /etc/config/network setting add GAteway
3 From SSH I change root password and reboot RS with PyCI
4 From internet explorer https://192.168.1.20 user name root and Password
I am able to login by doing following,
1 Internet security add 192.168.1.20 as trust site
2 By SSH change /etc/config/network setting add GAteway
3 From SSH I change root password and reboot RS with PyCI
4 From internet explorer https://192.168.1.20 user name root and Password
rakpatel
11-09-2009, 08:43 PM
Riskable,
I tried your firmware. Frankly speaking I do not find it friendly as what ubiquity is providing with their equipment. I was expecting something more user friendly and robust, strong with this Challange. I also tried NETSHe and my oppinion is same.
Mike with this contest, is it possible that UBNT is coming with something more powerful and user friendly firmware or may be UBNT as a HW mfg tell company like ANTCOR or MESHCOM or OpenWRT to produce some meaningful industrial grade firmware we do not mind to pay........
I tried your firmware. Frankly speaking I do not find it friendly as what ubiquity is providing with their equipment. I was expecting something more user friendly and robust, strong with this Challange. I also tried NETSHe and my oppinion is same.
Mike with this contest, is it possible that UBNT is coming with something more powerful and user friendly firmware or may be UBNT as a HW mfg tell company like ANTCOR or MESHCOM or OpenWRT to produce some meaningful industrial grade firmware we do not mind to pay........
riskable
11-10-2009, 08:55 AM
for PyCI also I am able to get ping from 192.168.1.20 but not able to login through port 80. Any Idea.... or can you describe the procedure. I had read the procedure and tried excatly what they said.... But no luck
Yeah, that's an issue I'm working on: http://192.168.1.20 should redirect you to https://192.168.1.20 but there's no way to do that without setting up a separate web server (which would take up unnecessary RAM). I'm actually going to port PyCI to a different web framework in the future and this is on the list of things to get working when that happens.
Yeah, that's an issue I'm working on: http://192.168.1.20 should redirect you to https://192.168.1.20 but there's no way to do that without setting up a separate web server (which would take up unnecessary RAM). I'm actually going to port PyCI to a different web framework in the future and this is on the list of things to get working when that happens.
riskable
11-10-2009, 10:54 AM
I am also not able to login using root with no password.
If anyone knows the trick please inform the rest of us.
You've found a bug! I just checked this myself and it seems that if you enter root with no password it won't let you in after a fresh flash. However, if you enter root with *anything* in the password box it'll let you in (I recommend typing in what you're going to set your password to).
It has to do with the order of the authentication checks in my code. Essentially, it checks to see if root has been setup with a password yet and if not, it lets you in as root automatically. However, it first tries to convert your password to a hash before it gets to that point. With an empty password it throws an exception and authentication fails.
It will get fixed in short order.
BTW: How did I miss such a stupid bug? Blame Firefox's "Remember Password" feature =)
If anyone knows the trick please inform the rest of us.
You've found a bug! I just checked this myself and it seems that if you enter root with no password it won't let you in after a fresh flash. However, if you enter root with *anything* in the password box it'll let you in (I recommend typing in what you're going to set your password to).
It has to do with the order of the authentication checks in my code. Essentially, it checks to see if root has been setup with a password yet and if not, it lets you in as root automatically. However, it first tries to convert your password to a hash before it gets to that point. With an empty password it throws an exception and authentication fails.
It will get fixed in short order.
BTW: How did I miss such a stupid bug? Blame Firefox's "Remember Password" feature =)
riskable
11-10-2009, 11:00 AM
Riskable,
I tried your firmware. Frankly speaking I do not find it friendly as what ubiquity is providing with their equipment. I was expecting something more user friendly and robust, strong with this Challange. I also tried NETSHe and my oppinion is same.
Fair enough. There's a ton of user-friendly features I intend to add but please keep in mind that my priority for the contest was meeting all of the requirements. Now that the contest is over I actually have time to make the essential stuff a lot easier to use (and faster--which is my current priority).
BTW: I'd love specifics as to what you think needs improvement. In my mind the "Help" needs a drastic overhaul and there needs to be more easy buttons. I should be able to simplify things for less experienced users while still keeping the infinite configurability of the interface.
I tried your firmware. Frankly speaking I do not find it friendly as what ubiquity is providing with their equipment. I was expecting something more user friendly and robust, strong with this Challange. I also tried NETSHe and my oppinion is same.
Fair enough. There's a ton of user-friendly features I intend to add but please keep in mind that my priority for the contest was meeting all of the requirements. Now that the contest is over I actually have time to make the essential stuff a lot easier to use (and faster--which is my current priority).
BTW: I'd love specifics as to what you think needs improvement. In my mind the "Help" needs a drastic overhaul and there needs to be more easy buttons. I should be able to simplify things for less experienced users while still keeping the infinite configurability of the interface.
rakpatel
11-10-2009, 10:04 PM
Hi riskable,
Great effort done. Intention is to have easy user friendly interface, like Mikrotik, Antcor, UBNT. We realy love to use RS with Web UI. Power stuff should have powerful interface. Ubnt interface is very good. Instead putting somthing popup for setting or sliding from one setting to another sub-setting it just great to have facility like windows explorer kind of thing or what ever you migh be planning. It is my humble suggestion to have some combination of UBNT existing firmware kind and some more feature. I am no suggesting copying .....Anyway great effort done and have goodluck for future development. We keep checking your update and also keep informing problems...
Regards
Great effort done. Intention is to have easy user friendly interface, like Mikrotik, Antcor, UBNT. We realy love to use RS with Web UI. Power stuff should have powerful interface. Ubnt interface is very good. Instead putting somthing popup for setting or sliding from one setting to another sub-setting it just great to have facility like windows explorer kind of thing or what ever you migh be planning. It is my humble suggestion to have some combination of UBNT existing firmware kind and some more feature. I am no suggesting copying .....Anyway great effort done and have goodluck for future development. We keep checking your update and also keep informing problems...
Regards
MaximumISP
11-11-2009, 06:30 AM
Riskable I would love to try it but
I cant get anything to flash to the rspro
for the life of me i dont know what im doing wrong
I need the for dumies step by step definitive guide
I cant get anything to flash to the rspro
for the life of me i dont know what im doing wrong
I need the for dumies step by step definitive guide
jzeller
11-12-2009, 07:26 AM
Riskable I would love to try it but
I cant get anything to flash to the rspro
for the life of me i dont know what im doing wrong
I need the for dumies step by step definitive guide
MaximumISP,
What steps are you using? I have it working on two RS Pro's now. Here is the steps I have been using:
1. Grab trunk
2. Grab PyCI source code from here: http://ubnt.com/downloads/RouterStationChallenge/PyCI/PyCI.zip
3. I extracted PyCI right in my trunk folder. "/home/jzeller/trunk/PyCI"
4. Follow the Building PyCI steps at http://www.ubnt.com/wiki/index.php/RouterStationChallenge_PyCI
NOTE: Make sure you have the required files/programs like Java or it won't compile correctly.
5. Follow the Building the Firmware Image steps at http://www.ubnt.com/wiki/index.php/RouterStationChallenge_PyCI.
NOTE: Ignore getting trunk as you have it already.
NOTE: From what I have seen there is no pyOpenSSL opkg available yet so you will need to install that package after you flashed the firmware to the router. It is available here: http://riskable.com/files/pyOpenSSL_0.9-1_ar71xx.ipk. If you get Internet access to the router after flashing you can run the command:
opkg install http://riskable.com/files/pyOpenSSL_0.9-1_ar71xx.ipk
This is necessary to login with https which is default, otherwise you need to modify the cherrypy config file to use http. Until this package is installed you cannot login to the interface. I think/hope we will get the source code soon for it so this step can be eliminated.
Instructions for changing the config file are here:
http://www.ubnt.com/forum/showpost.php?p=58073&postcount=14
6. Follow the remaining steps. I use the config file included in the source code. Just copy the pyci_firmware.config file to the ~/trunk folder.
7. Run make menuconfig and load an altername configuration file pyci_firmware.config. From there add in any additional packages. I found a couple of additional things I needed to round out my firmware. You can also just build this firmware and then add packages later with opkg.
8. VERY IMPORTANT: This creates a large flash file ~11MB. By default when you try to run make V=99 -j number of procs it will create files in the ~/trunk/bin folder but there is not a file for the RSPro as the limit is set to 8MB I believe or something like that. You need to modify a file that limits the size. The file is located at: ~/trunk/tools/firmware-utils/src/mkfwimage.c. Once inside that file you need to edit two lines. There is a patch out there but I just do it manually.
.name = "RS",
.kern_start = 0xbf030000,
.kern_entry = 0x80060000,
.firmware_max_length= 0x00F00000,
},
{
.name = "RSPRO",
.kern_start = 0xbf030000,
.kern_entry = 0x80060000,
.firmware_max_length= 0x00F00000,
Basically change the existing part in bold to this new number. This will allow an image of 14 MB. Caution: Don't get too large. The basic image is around 11MB. Once you save this run your make V=99 -j number of procs and you will now find the file you need in ~/trunk/bin.
I have attached a copy of the ~/trunk/tools/firmware-utils/src/mkfwimage.c. You will need to rename it to that, for upload purposes I had to change it. If this doesn't work for you let me know and I get you a link to a basic RS Pro image as suggested by Riskable.
Also, after you run the initial Build PyCI section. You will not need to do this again. Just run make menuconfig and adjust as necessary. Save config if wanted to another filename for tracking. Follow up with a make V=99 -j number of procs and you should be good to go.
This will generate a file in ~/trunk/bin called openwrt-ar71xx-ubnt-rspro-jffs2.bin. I happen to use this one. For flashing it to the router, I use the Linksys TFTP utility as it is very quick and easy. I have attached it as well. Follow steps below:
1. Connect computer to the WAN port of RS Pro. Set this interface to IP 192.168.1.2. By choosing this IP you will not run into conflicts after flashing as I change the router to 192.168.1.1 in make menuconfig
2. Hold reset button in while plugin in power. Continue to hold for at least 15 secs or if you have a console session going till it is waiting for tftp.
3. Open the TFTP client.
4. Point to 192.168.1.20.
5. Password "ubnt"
6. Browse to your .bin file.
7. Click on upgrade and away it goes.
This is obviously for Windows. Everybody may use other steps but this happens to work the easiest for me.
I cant get anything to flash to the rspro
for the life of me i dont know what im doing wrong
I need the for dumies step by step definitive guide
MaximumISP,
What steps are you using? I have it working on two RS Pro's now. Here is the steps I have been using:
1. Grab trunk
2. Grab PyCI source code from here: http://ubnt.com/downloads/RouterStationChallenge/PyCI/PyCI.zip
3. I extracted PyCI right in my trunk folder. "/home/jzeller/trunk/PyCI"
4. Follow the Building PyCI steps at http://www.ubnt.com/wiki/index.php/RouterStationChallenge_PyCI
NOTE: Make sure you have the required files/programs like Java or it won't compile correctly.
5. Follow the Building the Firmware Image steps at http://www.ubnt.com/wiki/index.php/RouterStationChallenge_PyCI.
NOTE: Ignore getting trunk as you have it already.
NOTE: From what I have seen there is no pyOpenSSL opkg available yet so you will need to install that package after you flashed the firmware to the router. It is available here: http://riskable.com/files/pyOpenSSL_0.9-1_ar71xx.ipk. If you get Internet access to the router after flashing you can run the command:
opkg install http://riskable.com/files/pyOpenSSL_0.9-1_ar71xx.ipk
This is necessary to login with https which is default, otherwise you need to modify the cherrypy config file to use http. Until this package is installed you cannot login to the interface. I think/hope we will get the source code soon for it so this step can be eliminated.
Instructions for changing the config file are here:
http://www.ubnt.com/forum/showpost.php?p=58073&postcount=14
6. Follow the remaining steps. I use the config file included in the source code. Just copy the pyci_firmware.config file to the ~/trunk folder.
7. Run make menuconfig and load an altername configuration file pyci_firmware.config. From there add in any additional packages. I found a couple of additional things I needed to round out my firmware. You can also just build this firmware and then add packages later with opkg.
8. VERY IMPORTANT: This creates a large flash file ~11MB. By default when you try to run make V=99 -j number of procs it will create files in the ~/trunk/bin folder but there is not a file for the RSPro as the limit is set to 8MB I believe or something like that. You need to modify a file that limits the size. The file is located at: ~/trunk/tools/firmware-utils/src/mkfwimage.c. Once inside that file you need to edit two lines. There is a patch out there but I just do it manually.
.name = "RS",
.kern_start = 0xbf030000,
.kern_entry = 0x80060000,
.firmware_max_length= 0x00F00000,
},
{
.name = "RSPRO",
.kern_start = 0xbf030000,
.kern_entry = 0x80060000,
.firmware_max_length= 0x00F00000,
Basically change the existing part in bold to this new number. This will allow an image of 14 MB. Caution: Don't get too large. The basic image is around 11MB. Once you save this run your make V=99 -j number of procs and you will now find the file you need in ~/trunk/bin.
I have attached a copy of the ~/trunk/tools/firmware-utils/src/mkfwimage.c. You will need to rename it to that, for upload purposes I had to change it. If this doesn't work for you let me know and I get you a link to a basic RS Pro image as suggested by Riskable.
Also, after you run the initial Build PyCI section. You will not need to do this again. Just run make menuconfig and adjust as necessary. Save config if wanted to another filename for tracking. Follow up with a make V=99 -j number of procs and you should be good to go.
This will generate a file in ~/trunk/bin called openwrt-ar71xx-ubnt-rspro-jffs2.bin. I happen to use this one. For flashing it to the router, I use the Linksys TFTP utility as it is very quick and easy. I have attached it as well. Follow steps below:
1. Connect computer to the WAN port of RS Pro. Set this interface to IP 192.168.1.2. By choosing this IP you will not run into conflicts after flashing as I change the router to 192.168.1.1 in make menuconfig
2. Hold reset button in while plugin in power. Continue to hold for at least 15 secs or if you have a console session going till it is waiting for tftp.
3. Open the TFTP client.
4. Point to 192.168.1.20.
5. Password "ubnt"
6. Browse to your .bin file.
7. Click on upgrade and away it goes.
This is obviously for Windows. Everybody may use other steps but this happens to work the easiest for me.
riskable
11-12-2009, 07:30 AM
Hi riskable,
Great effort done. Intention is to have easy user friendly interface, like Mikrotik, Antcor, UBNT. We realy love to use RS with Web UI. Power stuff should have powerful interface. Ubnt interface is very good. Instead putting somthing popup for setting or sliding from one setting to another sub-setting it just great to have facility like windows explorer kind of thing or what ever you migh be planning. It is my humble suggestion to have some combination of UBNT existing firmware kind and some more feature. I am no suggesting copying .....Anyway great effort done and have goodluck for future development. We keep checking your update and also keep informing problems...
Regards
I'm not sure what you mean when you're talking about the existing UBNT firmware... The firmware that ships with the RouterStation only has a web page that displays your wireless card(s) and MAC address(es). There's no configuration interface at all.
If you're talking about the AirOS interface I've never used it. So if that's what you're referring to you'll have to be more specific.
Great effort done. Intention is to have easy user friendly interface, like Mikrotik, Antcor, UBNT. We realy love to use RS with Web UI. Power stuff should have powerful interface. Ubnt interface is very good. Instead putting somthing popup for setting or sliding from one setting to another sub-setting it just great to have facility like windows explorer kind of thing or what ever you migh be planning. It is my humble suggestion to have some combination of UBNT existing firmware kind and some more feature. I am no suggesting copying .....Anyway great effort done and have goodluck for future development. We keep checking your update and also keep informing problems...
Regards
I'm not sure what you mean when you're talking about the existing UBNT firmware... The firmware that ships with the RouterStation only has a web page that displays your wireless card(s) and MAC address(es). There's no configuration interface at all.
If you're talking about the AirOS interface I've never used it. So if that's what you're referring to you'll have to be more specific.
riskable
11-12-2009, 08:09 AM
Riskable I would love to try it but
I cant get anything to flash to the rspro
for the life of me i dont know what im doing wrong
I need the for dumies step by step definitive guide
I just tried creating a PyCI RouterStation Pro image with the latest OpenWRT trunk. I don't have a RouterStation Pro to test it with but you could give it a try:
http://riskable.com/files/pyci_rspro-squashfs.bin
I went the extra mile and enabled SD/MMC support. Hopefully all you need to do is compile in that kernel module :)
I cant get anything to flash to the rspro
for the life of me i dont know what im doing wrong
I need the for dumies step by step definitive guide
I just tried creating a PyCI RouterStation Pro image with the latest OpenWRT trunk. I don't have a RouterStation Pro to test it with but you could give it a try:
http://riskable.com/files/pyci_rspro-squashfs.bin
I went the extra mile and enabled SD/MMC support. Hopefully all you need to do is compile in that kernel module :)
rct
11-12-2009, 08:37 AM
I don't have a RouterStation Pro to test it with)
Given all the good work you are doing I hope UBNT gets you a RouterStation Pro ASAP. It's a great platform that deserves great firmware.
--Rob
Given all the good work you are doing I hope UBNT gets you a RouterStation Pro ASAP. It's a great platform that deserves great firmware.
--Rob
MaximumISP
11-12-2009, 10:35 AM
Thanx Guys
Ok well that explains it I havent compiled anything
I have been trying to upload the images as they are
which explains my lack of success
I am no linux guru and havent ever compiled anything but
a to do list :) So forgive my stupidity
why must it be compiled ?
couldnt we just have a standard
pre compiled image ready to be flashed
Thnx
Ok well that explains it I havent compiled anything
I have been trying to upload the images as they are
which explains my lack of success
I am no linux guru and havent ever compiled anything but
a to do list :) So forgive my stupidity
why must it be compiled ?
couldnt we just have a standard
pre compiled image ready to be flashed
Thnx
riskable
11-12-2009, 12:43 PM
Thanx Guys
Ok well that explains it I havent compiled anything
I have been trying to upload the images as they are
which explains my lack of success
I am no linux guru and havent ever compiled anything but
a to do list :) So forgive my stupidity
why must it be compiled ?
couldnt we just have a standard
pre compiled image ready to be flashed
Thnx
The wiki has pre-compiled downloadable firmwares for the RouterStation. But that's why I made you a downloadable, pre-compiled firmware for a RouterStation pro here:
http://riskable.com/files/pyci_rspro-squashfs.bin
Just try flashing your RS Pro with that. It should work. Just remember to use https://192.168.1.20 and not http://192.168.1.20
Ok well that explains it I havent compiled anything
I have been trying to upload the images as they are
which explains my lack of success
I am no linux guru and havent ever compiled anything but
a to do list :) So forgive my stupidity
why must it be compiled ?
couldnt we just have a standard
pre compiled image ready to be flashed
Thnx
The wiki has pre-compiled downloadable firmwares for the RouterStation. But that's why I made you a downloadable, pre-compiled firmware for a RouterStation pro here:
http://riskable.com/files/pyci_rspro-squashfs.bin
Just try flashing your RS Pro with that. It should work. Just remember to use https://192.168.1.20 and not http://192.168.1.20
MaximumISP
11-13-2009, 02:16 AM
hi guys thanks for all the help
obviously trying to load a rs image on a rspro doesnt work at all lol
Ok so I got it flashed and can get to the login screen
but I cant get in with root or any other combination
browsing jzellers post above (thanks) shows to edit the config file
but I cant seem to login with it either what is the ssh user & pass please
as a side note I could not get the login box via the WAN port
I had to switch to the LAN port
obviously trying to load a rs image on a rspro doesnt work at all lol
Ok so I got it flashed and can get to the login screen
but I cant get in with root or any other combination
browsing jzellers post above (thanks) shows to edit the config file
but I cant seem to login with it either what is the ssh user & pass please
as a side note I could not get the login box via the WAN port
I had to switch to the LAN port
riskable
11-13-2009, 11:59 AM
hi guys thanks for all the help
obviously trying to load a rs image on a rspro doesnt work at all lol
Ok so I got it flashed and can get to the login screen
but I cant get in with root or any other combination
browsing jzellers post above (thanks) shows to edit the config file
but I cant seem to login with it either what is the ssh user & pass please
as a side note I could not get the login box via the WAN port
I had to switch to the LAN port
There's a bug with the login screen after a fresh reboot. Just enter root with some made-up password to get in. If you enter a blank password it won't work.
If all else fails, reboot... The scripts that build the jffs2 partition can cause some issues with Python after that first initial reboot too. So as long as you flash, wait 3 minutes, then reboot that should take care of any issues.
obviously trying to load a rs image on a rspro doesnt work at all lol
Ok so I got it flashed and can get to the login screen
but I cant get in with root or any other combination
browsing jzellers post above (thanks) shows to edit the config file
but I cant seem to login with it either what is the ssh user & pass please
as a side note I could not get the login box via the WAN port
I had to switch to the LAN port
There's a bug with the login screen after a fresh reboot. Just enter root with some made-up password to get in. If you enter a blank password it won't work.
If all else fails, reboot... The scripts that build the jffs2 partition can cause some issues with Python after that first initial reboot too. So as long as you flash, wait 3 minutes, then reboot that should take care of any issues.
FCC-PT
11-20-2009, 05:26 AM
I compiled with success a RSPro image, flashed into but no ping... no access no nothing!
I though I might done something wrong but... tested your image but guess what? Same thing, no ping no "https" access nothing what might be?!? Thank's riskable. :(
I though I might done something wrong but... tested your image but guess what? Same thing, no ping no "https" access nothing what might be?!? Thank's riskable. :(
riskable
11-20-2009, 09:52 AM
I compiled with success a RSPro image, flashed into but no ping... no access no nothing!
I though I might done something wrong but... tested your image but guess what? Same thing, no ping no "https" access nothing what might be?!? Thank's riskable. :(
UBNT was kind enough to give me a RouterStation Pro when I was at their headquarters last week. I flashed mine with that same image and I'm experiencing the same problem. I'll have the opportunity to investigate it and hopefully fix the issue later today. Once I get the serial port hooked up I'm sure I'll be able to figure it out in short order.
I though I might done something wrong but... tested your image but guess what? Same thing, no ping no "https" access nothing what might be?!? Thank's riskable. :(
UBNT was kind enough to give me a RouterStation Pro when I was at their headquarters last week. I flashed mine with that same image and I'm experiencing the same problem. I'll have the opportunity to investigate it and hopefully fix the issue later today. Once I get the serial port hooked up I'm sure I'll be able to figure it out in short order.
riskable
11-20-2009, 03:02 PM
OK, I just re-flashed my RS Pro from scratch using an image I *just* compiled... It seemed to flash just fine but after rebooting I couldn't ping 192.168.1.20. On a hunch I switched my laptop's ethernet cable from the WAN port to one of the switch ports on the RS Pro... That did the trick!
So the flash works fine but the network configuration is the opposite of a normal RouterStation... The LAN port gets 192.168.1.20 after flashing, not the WAN port.
The firmware I just compiled is no different from the one I posted earlier (just freshly re-compiled). So that should answer your problem.
BTW: The "can't login after reboot with root and no password" problem didn't crop up on the RS Pro. Maybe the OpenWRT folks fixed the Python/jffs2 issues in a recent trunk?
So the flash works fine but the network configuration is the opposite of a normal RouterStation... The LAN port gets 192.168.1.20 after flashing, not the WAN port.
The firmware I just compiled is no different from the one I posted earlier (just freshly re-compiled). So that should answer your problem.
BTW: The "can't login after reboot with root and no password" problem didn't crop up on the RS Pro. Maybe the OpenWRT folks fixed the Python/jffs2 issues in a recent trunk?
cbuechler
11-22-2009, 04:34 PM
Thanks for the RS Pro image, riskable. I can't get it to load though. Tried to put it via TFTP after putting the RS Pro into bootloader mode, and it goes through and writes for a while, but then the TFTP client shows:
sent DATA <block=18573, 512 bytes>
received ACK <block=18573>
sent DATA <block=18574, 201 bytes>
sent DATA <block=18574, 201 bytes>
sent DATA <block=18574, 201 bytes>
sent DATA <block=18574, 201 bytes>
sent DATA <block=18574, 201 bytes>
Transfer timed out.
while the console of the RS Pro shows:
TFTPD: Incoming connection from <IP of TFTP client>
Received: 9509577 bytes
Firmware Version: RSPRO.ar7100pro.OpenWrt.r18354
The TFTP transfer times out simultaneously with the "Firmware version" line showing up on the RS Pro console. The console is unresponsive at that point and rebooting it results in it booting into what was previously on the flash.
sent DATA <block=18573, 512 bytes>
received ACK <block=18573>
sent DATA <block=18574, 201 bytes>
sent DATA <block=18574, 201 bytes>
sent DATA <block=18574, 201 bytes>
sent DATA <block=18574, 201 bytes>
sent DATA <block=18574, 201 bytes>
Transfer timed out.
while the console of the RS Pro shows:
TFTPD: Incoming connection from <IP of TFTP client>
Received: 9509577 bytes
Firmware Version: RSPRO.ar7100pro.OpenWrt.r18354
The TFTP transfer times out simultaneously with the "Firmware version" line showing up on the RS Pro console. The console is unresponsive at that point and rebooting it results in it booting into what was previously on the flash.
ubnt-115
11-23-2009, 12:18 AM
New version of NETSHe (0.0.8) is released.
It has some fixes and code cleanups.
Source code is available here http://stasoft.net/files/rb-0.0.8.tar.gz
Image for Ubiquity RouterStation is available here http://stasoft.net/files/openwrt/ubiquity/NETSHe.bin
Build makefile is available here http://stasoft.net/files/openwrt/ubiquity/netshe-openwrt-build.tar.bz2 (See documentation how to use)
Also we've uploaded separately packages for Ubiquity RouterStation:
- php5_5.2.6-2_ar71xx.ipk (http://stasoft.net/files/openwrt/ubiquity/php5_5.2.6-2_ar71xx.ipk)
- php5-cgi_5.2.6-2_ar71xx.ipk (http://stasoft.net/files/openwrt/ubiquity/php5-cgi_5.2.6-2_ar71xx.ipk)
- netshe_0.0.8-1_ar71xx.ipk (http://stasoft.net/files/openwrt/ubiquity/netshe_0.0.8-1_ar71xx.ipk)
All this packages should be installed to launch NETSHe. Please, run /etc/init.d/bootstrap.ssxapp after installation
PS. eth0 has 192.168.1.20 as IP-address now
PPS. I've responses, that my compiled image does not initializes wifi-module right. Please, can anyone send me dmesg and lsmod output from RouterStation with worked Ubiquity wifi module ?
It has some fixes and code cleanups.
Source code is available here http://stasoft.net/files/rb-0.0.8.tar.gz
Image for Ubiquity RouterStation is available here http://stasoft.net/files/openwrt/ubiquity/NETSHe.bin
Build makefile is available here http://stasoft.net/files/openwrt/ubiquity/netshe-openwrt-build.tar.bz2 (See documentation how to use)
Also we've uploaded separately packages for Ubiquity RouterStation:
- php5_5.2.6-2_ar71xx.ipk (http://stasoft.net/files/openwrt/ubiquity/php5_5.2.6-2_ar71xx.ipk)
- php5-cgi_5.2.6-2_ar71xx.ipk (http://stasoft.net/files/openwrt/ubiquity/php5-cgi_5.2.6-2_ar71xx.ipk)
- netshe_0.0.8-1_ar71xx.ipk (http://stasoft.net/files/openwrt/ubiquity/netshe_0.0.8-1_ar71xx.ipk)
All this packages should be installed to launch NETSHe. Please, run /etc/init.d/bootstrap.ssxapp after installation
PS. eth0 has 192.168.1.20 as IP-address now
PPS. I've responses, that my compiled image does not initializes wifi-module right. Please, can anyone send me dmesg and lsmod output from RouterStation with worked Ubiquity wifi module ?
marcusburge
11-23-2009, 09:41 PM
ubnt-115, i upgraded to the latest release you just put out. everything worked well except for the wireless settings do not appear in the console, it may be the issue you described, although i'm not sure, as I'm running a routerstation with an XR9 900mhz card, but the settings are the same.
attached are the requested dmesg and lsmod, and a screenshot of the wifi0 settings page.
attached are the requested dmesg and lsmod, and a screenshot of the wifi0 settings page.
ubnt-115
11-24-2009, 12:13 AM
ubnt-115, i upgraded to the latest release you just put out. everything worked well except for the wireless settings do not appear in the console, it may be the issue you described, although i'm not sure, as I'm running a routerstation with an XR9 900mhz card, but the settings are the same.
attached are the requested dmesg and lsmod, and a screenshot of the wifi0 settings page.
Hello.
Many thanks. I uploaded new build of firmware today. It's available under link specified above.
attached are the requested dmesg and lsmod, and a screenshot of the wifi0 settings page.
Hello.
Many thanks. I uploaded new build of firmware today. It's available under link specified above.
rct
12-02-2009, 09:29 AM
New version of NETSHe (0.0.8) is released.
...
Image for Ubiquity RouterStation is available here http://stasoft.net/files/openwrt/ubiquity/NETSHe.bin
ubnt-115: Any chance of getting RouterStation Pro images posted too?
Thanks
--Rob
...
Image for Ubiquity RouterStation is available here http://stasoft.net/files/openwrt/ubiquity/NETSHe.bin
ubnt-115: Any chance of getting RouterStation Pro images posted too?
Thanks
--Rob
pturkey
12-07-2009, 02:31 PM
Ther is no way to log into this router!
I have flashed it many times.
All the usernames and passwords do not work.
Is ther a build that will work corrrectly?
If not I will look for something else.
I have flashed it many times.
All the usernames and passwords do not work.
Is ther a build that will work corrrectly?
If not I will look for something else.
rct
12-12-2009, 03:41 PM
Here's a summary of the steps necessary to get the PyCI image provided by riskable running on an RS Pro.
http://riskable.com/files/pyci_rspro-squashfs.bin
Summary of the steps to get it running:
Connect network to wan port, apply power while holding down the reset button. tftp pyci_rspro-squashfs.bin to 192.168.1.20
Wait until the RS pro reboots itself.
Change the network cable from the wan port to the first lan port. The new firmware has the lan port as 192.168.1.20 instead of the wan port. The wan port is set to DHCP but you won't be able to get into the box from the wan port.
Go to https://192.168.1.20/, Note SSL, Firefox and other browsers will complain about the invalid certificate. Accept the certificate for now.
Login with user name root. Type something into the password field. At this point there is no root password, but you have to type something in order to login. Note since there is no root password you can't ssh into the box!
Click PyCI menu, then System, then Users & Groups.
Click on root in the table of users. Then right click to get the context menu that has the option 'Change Password'. Pick a new root password. Now you should be able to get in using ssh as well as through the PyCI web interface.
The image also seems to have a simulated wireless card mac80211-hwsim that can cause some confusion when trying to configure a real wireless card. You can disable it by removed /etc/modules.d/60-mac80211-hwsim, or by opkg remove kmod-mac80211-hwsim.
I hope subsequent builds will have a default root password, the default of 'ubnt' to match the factory provided image will probably eliminate confusion.
Hope this helps,
--Rob
http://riskable.com/files/pyci_rspro-squashfs.bin
Summary of the steps to get it running:
Connect network to wan port, apply power while holding down the reset button. tftp pyci_rspro-squashfs.bin to 192.168.1.20
Wait until the RS pro reboots itself.
Change the network cable from the wan port to the first lan port. The new firmware has the lan port as 192.168.1.20 instead of the wan port. The wan port is set to DHCP but you won't be able to get into the box from the wan port.
Go to https://192.168.1.20/, Note SSL, Firefox and other browsers will complain about the invalid certificate. Accept the certificate for now.
Login with user name root. Type something into the password field. At this point there is no root password, but you have to type something in order to login. Note since there is no root password you can't ssh into the box!
Click PyCI menu, then System, then Users & Groups.
Click on root in the table of users. Then right click to get the context menu that has the option 'Change Password'. Pick a new root password. Now you should be able to get in using ssh as well as through the PyCI web interface.
The image also seems to have a simulated wireless card mac80211-hwsim that can cause some confusion when trying to configure a real wireless card. You can disable it by removed /etc/modules.d/60-mac80211-hwsim, or by opkg remove kmod-mac80211-hwsim.
I hope subsequent builds will have a default root password, the default of 'ubnt' to match the factory provided image will probably eliminate confusion.
Hope this helps,
--Rob
riskable
12-15-2009, 06:40 AM
Here's a summary of the steps necessary to get the PyCI image provided by riskable running on an RS Pro.
http://riskable.com/files/pyci_rspro-squashfs.bin
Summary of the steps to get it running:
Connect network to wan port, apply power while holding down the reset button. tftp pyci_rspro-squashfs.bin to 192.168.1.20
Wait until the RS pro reboots itself.
Change the network cable from the wan port to the first lan port. The new firmware has the lan port as 192.168.1.20 instead of the wan port. The wan port is set to DHCP but you won't be able to get into the box from the wan port.
Go to https://192.168.1.20/, Note SSL, Firefox and other browsers will complain about the invalid certificate. Accept the certificate for now.
Login with user name root. Type something into the password field. At this point there is no root password, but you have to type something in order to login. Note since there is no root password you can't ssh into the box!
Click PyCI menu, then System, then Users & Groups.
Click on root in the table of users. Then right click to get the context menu that has the option 'Change Password'. Pick a new root password. Now you should be able to get in using ssh as well as through the PyCI web interface.
The image also seems to have a simulated wireless card mac80211-hwsim that can cause some confusion when trying to configure a real wireless card. You can disable it by removed /etc/modules.d/60-mac80211-hwsim, or by opkg remove kmod-mac80211-hwsim.
I hope subsequent builds will have a default root password, the default of 'ubnt' to match the factory provided image will probably eliminate confusion.
Hope this helps,
--Rob
A couple of notes and updates...
* I'm going to add a "set root password" prompt when you login for the first time to make that process a bit simpler.
* The simulated wireless card driver will be removed from future builds.
* The port to Tornado is complete (has been for two weeks now but I've been traveling and haven't been able to test my most recent changes). Hopefully I'll have time this weekend to post a beta firmware.
* I've added the capability for PyCI to generate new SSL certificates on-demand. There's no GUI element to this but I'll be adding that shortly (pretty straighforward).
* There's some serious bugs in PyCI due to recent changes in trunk that I'm working on. That's why it has been so long since I posted an update. Here's what I need to fix before I post it publicly: DHCP configuration broke, wireless configuration broke with 802.11n-capable cards, and I also have to fix a bug with the ESC key in Escape From The Web (LOL).
For reference, I ordered one of those nice Netgate cases for my RouterStation Pro that just arrived at my house yesterday. So on my next trip I'll be bringing the RS Pro with me so I can actually test things.
FYI: I just updated the svn with the latest Tornado changes. So if you know what you're doing feel free to test it out!
http://riskable.com/files/pyci_rspro-squashfs.bin
Summary of the steps to get it running:
Connect network to wan port, apply power while holding down the reset button. tftp pyci_rspro-squashfs.bin to 192.168.1.20
Wait until the RS pro reboots itself.
Change the network cable from the wan port to the first lan port. The new firmware has the lan port as 192.168.1.20 instead of the wan port. The wan port is set to DHCP but you won't be able to get into the box from the wan port.
Go to https://192.168.1.20/, Note SSL, Firefox and other browsers will complain about the invalid certificate. Accept the certificate for now.
Login with user name root. Type something into the password field. At this point there is no root password, but you have to type something in order to login. Note since there is no root password you can't ssh into the box!
Click PyCI menu, then System, then Users & Groups.
Click on root in the table of users. Then right click to get the context menu that has the option 'Change Password'. Pick a new root password. Now you should be able to get in using ssh as well as through the PyCI web interface.
The image also seems to have a simulated wireless card mac80211-hwsim that can cause some confusion when trying to configure a real wireless card. You can disable it by removed /etc/modules.d/60-mac80211-hwsim, or by opkg remove kmod-mac80211-hwsim.
I hope subsequent builds will have a default root password, the default of 'ubnt' to match the factory provided image will probably eliminate confusion.
Hope this helps,
--Rob
A couple of notes and updates...
* I'm going to add a "set root password" prompt when you login for the first time to make that process a bit simpler.
* The simulated wireless card driver will be removed from future builds.
* The port to Tornado is complete (has been for two weeks now but I've been traveling and haven't been able to test my most recent changes). Hopefully I'll have time this weekend to post a beta firmware.
* I've added the capability for PyCI to generate new SSL certificates on-demand. There's no GUI element to this but I'll be adding that shortly (pretty straighforward).
* There's some serious bugs in PyCI due to recent changes in trunk that I'm working on. That's why it has been so long since I posted an update. Here's what I need to fix before I post it publicly: DHCP configuration broke, wireless configuration broke with 802.11n-capable cards, and I also have to fix a bug with the ESC key in Escape From The Web (LOL).
For reference, I ordered one of those nice Netgate cases for my RouterStation Pro that just arrived at my house yesterday. So on my next trip I'll be bringing the RS Pro with me so I can actually test things.
FYI: I just updated the svn with the latest Tornado changes. So if you know what you're doing feel free to test it out!
zchellpy
11-11-2010, 10:13 AM
Thanks u riskable for ur amazing gui. but what's this project are discontinued...??? and if i want to add package such as free-radius, just using packaging installer command like as in openwrt and after that what about dependecies .....???
Regards,
Adyn
Regards,
Adyn
FCC-PT
12-13-2010, 09:41 AM
I'm terrible sorry that this project is dead!
Regards
Regards
Languages translations made by vBET Translator 3.5.4