Firmware compatible to Wireless Space?

[fvdw]

nice

I will sent you a trial standalone kernel by pm later this evening.
To test it you can use the fvdw-sl console running under windows to load and start it.
if the standalone kernel works we can go to next step to get the firmware running on it.

To run in the fvdw-sl console choose action load standalone kernel and pretend if you have nwsp2,5big2 ..
Befor starting the console. Connect your wireless space to the lan and keep it switched of. Switch it on when the fvdw-sl console is waiting for u-boot (read the instructions)

[Redstorm]

:thinking

nice

I will sent you a trial standalone kernel by pm later this evening.
... (read the instructions)

Hello!
do you eventually need a second zero cost "white mouse" for testing?
Wireless Space 1 TB brand new available.
More than 30 years in debugging ( everything begun with a Z80 CPM system...long long ago)
available and ready for test.

Have a nice evening :thinking

Redstorm

[fvdw]

Hi redstorm

thanks for your offer, yes i want to make use of it, I have sent a kernel to keyvan but never got a reply. I will search that post and sent you a trial kernel.
Think it needs update to latest version. Will be tomorrow or friday evening

[fvdw]

I found the pm and I have forwarded it to you. Think it is still useable to see of the kernel setup i made for the wireless space works

please post your experiences here

[Redstorm]

Dear Friend, it seems that I am too much "freshman" here to getyour PM and the associated firmware file.
As I said, i just bought an "factory refurbished Wirel Space 1TB by Lacie", and I have, atm, time to invest in checking functions and enough band on my ADSL to interface remotely with my office, maybe via SonicWALL :lmao VPN, maybe directly.

One of my plans is to use it a Remote Backup site using Rsync, :hammerhead but we will see what comes out.

Not to override rules of the Forum, may I suggest that you send a "wetransfer" zipped file to my disposable address "redstorm@gmx.us"

You will be noticed of my download, and I will keep you posted on this thread about further developments, blocking and non blocking issues.

Have a nice day

Redstorm

[Jocko]

Hi Redstorm,

Now you should be able to use your pm.

enough band on my ADSL to interface remotely with my office

.

Currently, in our firmware, you can use several secure ways to get this :
-use a private cloud with webdav on a https protocol (this way allows to through any proxy or firewall if the port 443 is opened :-D )
-use a SFTP server
-use a FTP(E)S server
-use a VPN server: only pptp server is fully implemented but you have all tools to do a openVPN server.

[keyvan]

Tried the standalone kernel and from what I can tell from the tftp server output, the kernel is loaded, but I can not connect to the Wireless Space with telnet (connection attempt times out using the IP address of the device prior to loading the standalone kernel).

Throughout this trial, I have the Wireless Space connected to my LAN using the LAN(1-3) of the device. Tried using the WAN port of the WS with no luck. The standalone kernel didn't seem to load when using the WAN port.

Also, my WS is not in Router mode, ie. the device is simply being used as a NAS, hence connected to my LAN using LAN ports, no wireless, no WAN etc...

Let me know if you need more info.

P.S. Sorry for the late reply... Work and life have kept me busy :)

[fvdw]

Hi thanks for testing.

first be sure that your firewall settings doesn't block telnet client connections

(connection attempt times out using the IP address of the device prior to loading the standalone kernel).

what IP's do you use in your LAN ?
if they start with 192.168.1. or 192.168.0. then you should use 192.168.1.252 respectively 192.168.0.252 for the telnet client to connect. It will also try to get a dynamic one from your dhcp server in your network, also that one you can try.

If the connection times out you should try again after a few minutes, it could be that the kernel needs more time to load then 12 seonds. This can happen if there are issues with the for instance the sata driver.

[keyvan]

No luck,

I use the 196.168.1.x IP range with subnet mask 255.255.255.0. The WS has the static IP 192.168.1.5. I don't see a DHCP Lease entry on my DHCP server for WS while booting the standalone kernel. I tried both 192.168.1.5 and 192.168.1.252 after several minutes after booting the standalone kernel all without success.

I don't think any firewall or security settings are interfering with my connection attempts.

[Redstorm]

No luck,

I use the 196.168.1.x IP range with subnet mask 255.255.255.0. The WS has the static IP 192.168.1.5. I don't see a DHCP Lease entry on my DHCP server for WS while booting the standalone kernel. I tried both 192.168.1.5 and 192.168.1.252 after several minutes after booting the standalone kernel all without success.

I don't think any firewall or security settings are interfering with my connection attempts.

In the meantime I got enough quiet to make the test.
boundary Conditions: Wireless Space IP fixed to 192.168.0.1 Pc directly connected without switches or firewall.
Fired up the console software, and after switching off the WS1, selected both way the kernel and external kernel, with the file you sent me unzipped in the tftp directory.
Switched on the WSpace
Both ways i a m sure that, looking at the console, I saw the kernel "sucked in" the WS1: a lot of hashes fogging the screen.
after the recommended tipe lapse of more than 12 seconds, the Telenet console fired up , directed to the SAME IP ADDRESS where the tftp was sending the data.
As dumb as an engineer in love! :lmao
No response, no sign of intelligence both ways: first and second choice of kernel upload.
I just took the time to ping 192.168.0.1, the IP assigned to TFTP Target, but nothing come out. Unresponsive.
also switching off by pushbutton useless: pulling the cord, both times, the good old way.
What else can I do?
Any suggestion or recommendation will be very much appreciated. :dontknow
I have a SonicWALL Firewall getting dust on a scaffholding: i may use to have a good ARP map, having both parts connected on the LAN side, maybe using 192.168.0.1/24 as subnet. Also I may use to capture all the packets travelling to/from MAC Address of WSpace :pound It's a TZ190 with Enhanced Firmware.
Have a nice afternoon , here in Italy is definitely time to go to have a good sleep.
Regards
Redstorm