Thu Jul 31, 2014 7:46 pm
Oh, it took almost a day for my message to appear here, so I've been trying to figure this out myself meanwhile. Here is one attempt:
Assuming that the server side is ok, I tried resetting the client side and have my laptop connected here. So I connect to default address 192.168.88.1 with WinBox and let the default configuration be.
Now lets give a shot to "Quick Set". I switch the mode to "PTP Bridge" Client/CPE and now I get the server side SSD listed in a window below - great! Since I have set nv2 to use secure connection, I type in the WPA password and hit connect.
Odd enough, the link does not set up. Wireless status remains to be "searching for network". That's not good, so I goto see the settings in Wireless -> Interfaces and open the wlan1-gateway. Under NV2 tab the "Preshared Key" field remains empy and "Security" checkbox unticked? So I type in the WPA password again and tick the "Security" and apply the settings. Now I can see the link has been established! Rock on!
At this point I open a new instance of WinBox and let it search for devices. Although rest of my network resides in a different subnet, it can still find my main router and server side SXT. So it's all ok now?
Now I want to have the client side SXT to use the same IP address space with rest of my network, so I change it to a next free address (via "Quick Set") and hit OK. Obviously WinBox disconnects and I have to change my LAN adapter address to reflect this network settings.
As a quick test, I open a console to continuously ping my SXT client side address, that returns in less than 1ms. Great! However it timeouts if I try to ping any address from the Server side. Hmm... WinBox search still lists other routerboards, but any connection attempt by IP address fails to "no response" after waiting a long time. If I try to connect by MAC address, it return almost immediately to "no response".
Interesting enough, now the WinBox fails to connect to this client side SXT almost every time (I'm still plugged directly into it with my laptop) and after a short amount of time it disconnects. Same happens if I try web-GUI. However, as I previously set the console to ping the SXT, it still keeps returning flawlessly in less than 1ms and never drops a packet!
So, lets see how things look from server side: I attempt to ping the client SXT which fails, and is pretty much what I expeted. However, if I unplug the cable from my laptop (that was still connected to client SXT), the ping begins to return to server side!
Aaargh....
I have tried different IP addresses, just to be sure that these are not overlapping, but no luck. Interesting enough, when I set the client SXT the bridge will work at first - but only for a minute or so. I can access the Internet but after that it remains like this.
Man, someone please shred some light in here...