keyvan wrote: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