Hello Nick,
Now I've sorted other things out in my computer system and can now devote
all energy to getting webdav server to work.
First - My router's manual addresses wireless separation with these
phrases:
NOTE
STEP 1 STEP 2
Security Settings for Wireless Networks
Use the Wireless > Basic Settings > Security Settings page to configure
security for the selected wireless network. All devices on this network
(SSID) must use the same security mode and settings to work correctly.
Cisco recommends using the highest level of security that is supported by
the devices in your network.
To open this page: From the Wireless > Basic Settings page, select a
network and then click Edit Security Mode.
To configure a network with WPA Enterprise, WPA2 Enterprise, or WPA2
Enterprise Mixed security mode, you must first add a RADIUS Server
configuration. See Using the Cisco RV220W With a RADIUS Server, page 146.
If needed, select a different network in the Select SSID list. Enter these
settings for the selected network:
*
*
Wireless Isolation within SSID--Check Enable to prevent clients on this
wireless network from accessing devices on other wireless networks. To
allow access, click Disable.
Security--Choose a security mode:
-
- Disabled--Any device can connect to the network. Not recommended.
-
- Wired Equivalent Privacy (WEP)-- Weak security with a basic encryption
method that is not as secure as WPA. WEP may be required if your network
devices do not support WPA; however, it is not recommended.
-
- Wi-Fi Protected Access (WPA) Personal--WPA is part of the wireless
security standard (802.11i) standardized by the Wi-Fi Alliance and was
intended as an intermediate measure to take the place of WEP while the
802.11i standard was being prepared. It supports TKIP/AES encryption. The
personal authentication is the Preshared Key (PSK) that is an alphanumeric
passphrase shared with the wireless peer.
-
- WPA Enterprise--Allows you to use WPA with RADIUS server
authentication.
-
- WPA2 Personal--WPA2 is the implementation of security standard
specified in the final 802.11i standard. It supports AES encryption and
this option uses PSK based authentication.
-
- WPA2 Personal Mixed--Allows both WPA and WPA2 clients to connect
simultaneously using PSK authentication.
Cisco RV220W Administration Guide
56
Configuring the Wireless Network 3
Basic Settings
STEP 3
-
- WPA2 Enterprise--Allows you to use WPA2 with RADIUS server
authentication.
-
- WPA2 Enterprise Mixed--Allows both WPA and WPA2 clients to connect
simultaneously using RADIUS authentication.
* Encryption Type--An option is chosen automatically, based on the selected
security mode.
-
- TKIP+AES is used for WPA Personal, WPA Enterprise, WPA2 Personal
Mixed, and WPA2 Enterprise Mixed.
-
- AES is used for WPA2 Personal and WPA2 Enterprise. If you chose WPA
Enterprise or WPA2 Enterprise Mixed, no further settings are
required. You can save the settings.
If you chose WPA Personal, WPA2 Personal, or WPA2 Personal Mixed, enter
these settings:
-
WPA Key--Enter the pre-shared key for WPA/WPA2 PSK authentication. The
clients also need to be configured with the same password. As you type the
password, a message indicates the strength. For a stronger password, enter
at least eight characters including a variety of character types (numbers,
upper- and lowercase letters, and symbols).
-
Unmask Password--Check the box if you want to see the key as typed.
Otherwise, the password is masked.
-
Key Renewal--Enter the number of seconds after which the Cisco RV120W
will generate a new key. These keys are internal keys exchanged between the
Cisco RV120W and connected devices. The default value (3600 seconds) is
usually adequate unless you are experiencing network problems.
If you chose WEP, enter these settings:
STEP 4
*
*
Authentication--Choose the option that is supported by your network
devices: Open
System or Shared Key. In either case, the client must provide the correct
shared key (password) in order to connect to the wireless network.
Encryption--Choose 64-bit or 128-bit. 64-bit WEP has a 40-bit key, and
128-bit WEP has a 104-bit key. A larger key provides stronger encryption,
because the key is more difficult to crack.
Cisco RV220W Administration Guide
57
Configuring the Wireless Network 3
Basic Settings
STEP 5
-
WEP passphrase (Optional)--Enter an alphanumeric phrase (longer than
eight characters for optimal security) and click Generate Key to
generate four unique WEP keys in the WEP Key fields below. Otherwise, you
can manually enter one or more keys in the fields.
-
WEP Key 1-4--If you did not use the WEP Passphrase to generate keys,
enter one or more valid keys. Select a key to use as the shared key that
devices must have in order to use the wireless network. The length of the
key must be 5 ASCII characters (or 10 hexadecimal characters) for 64-bit
WEP and 13 ASCII characters (or 26 hexadecimal characters) for 128-bit WEP.
Valid hexadecimal characters are "0" to "9" and "A" to "F".
Click Save to save your settings, or click Cancel to reload the page
with the current settings. Click Back to return to the Wireless > Basic
Settings page.
If you need to configure the settings for another network, select it
from the Select SSID list, and then repeat this procedure.
The above is more or less written in Greek to me.
However, I've chosen Wireless and then chosen my networks name and then
edit. The next page in the setup is
*AP Profiles *
SSID: My networks name
Broadcast SSID: there's a box to tick which is ticked and it says
"enabled"
Security: WPA2 Personal
Encryption: AES
WPA Password: (a long one)
*WEP Index and Keys*
Authentication: Open system
Encryption: 64 bit WEP
I've pasted the input and output from my terminal window:
Last login: Thu Feb 27 14:57:17 on ttys000
gunnarwin-pc:~ gunnarnordenstam$ ping 192.168.1.105
PING 192.168.1.105 (192.168.1.105): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
ping: sendto: No route to host
(and so it goes on for ever)
It's the same result whether I have enabled or disabled Broadcast SSID.
then I tried http://192.168.1.105:8080 in Firefox which gave this result:
preload <http://192.168.1.105:8080/preload>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:10 CET 2014
factory <http://192.168.1.105:8080/factory>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:48:52 CET 2014
sdcard <http://192.168.1.105:8080/sdcard>(edit with
office)<http://192.168.1.105:8080/#>
Wed Feb 26 12:05:18 CET 2014
storage <http://192.168.1.105:8080/storage>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:10 CET 2014
config <http://192.168.1.105:8080/config>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:10 CET 2014
cache <http://192.168.1.105:8080/cache>(edit with
office)<http://192.168.1.105:8080/#>
Tue Feb 25 23:05:34 CET 2014
acct <http://192.168.1.105:8080/acct>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:10 CET 2014
vendor <http://192.168.1.105:8080/vendor>(edit with
office)<http://192.168.1.105:8080/#>
Fri Jan 03 18:50:29 CET 2014
d <http://192.168.1.105:8080/d>(edit with office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
etc <http://192.168.1.105:8080/etc>(edit with
office)<http://192.168.1.105:8080/#>
Fri Jan 03 18:55:52 CET 2014
efs <http://192.168.1.105:8080/efs>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:26 CET 2014
mnt <http://192.168.1.105:8080/mnt>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:10 CET 2014
selinux <http://192.168.1.105:8080/selinux>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:10 CET 2014
ueventd.smdk4x12.rc <http://192.168.1.105:8080/ueventd.smdk4x12.rc>(edit
with office) <http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
ueventd.rc <http://192.168.1.105:8080/ueventd.rc>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
system <http://192.168.1.105:8080/system>(edit with
office)<http://192.168.1.105:8080/#>
Fri Jan 03 18:55:42 CET 2014
sys <http://192.168.1.105:8080/sys>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:10 CET 2014
sbin <http://192.168.1.105:8080/sbin>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
proc <http://192.168.1.105:8080/proc>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
lpm.rc <http://192.168.1.105:8080/lpm.rc>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
lib <http://192.168.1.105:8080/lib>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
init.usb.rc <http://192.168.1.105:8080/init.usb.rc>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
init.trace.rc <http://192.168.1.105:8080/init.trace.rc>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
init.smdk4x12.usb.rc <http://192.168.1.105:8080/init.smdk4x12.usb.rc>(edit
with office) <http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
init.smdk4x12.rc <http://192.168.1.105:8080/init.smdk4x12.rc>(edit with
office) <http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
init.selinux_restore.sh
<http://192.168.1.105:8080/init.selinux_restore.sh>(edit
with office) <http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
init.rc <http://192.168.1.105:8080/init.rc>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
init.container.rc <http://192.168.1.105:8080/init.container.rc>(edit with
office) <http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
init <http://192.168.1.105:8080/init>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
fstab.smdk4x12 <http://192.168.1.105:8080/fstab.smdk4x12>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
file_contexts <http://192.168.1.105:8080/file_contexts>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
default.prop <http://192.168.1.105:8080/default.prop>(edit with
office)<http://192.168.1.105:8080/#>
Thu Jan 01 01:00:00 CET 1970
data <http://192.168.1.105:8080/data>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:13 CET 2014
root <http://192.168.1.105:8080/root>(edit with
office)<http://192.168.1.105:8080/#>
Thu Nov 28 13:01:54 CET 2013
dev <http://192.168.1.105:8080/dev>(edit with
office)<http://192.168.1.105:8080/#>
Thu Feb 27 07:47:11 CET 2014
I suppose the above denotes some form of contact.
Many thanks for your help. This is far beyond me and I suppose many others
on this site too.
/Gunnar
On 26 February 2014 12:30, Nick Drage <nickd-***@public.gmane.org> wrote:
>
>
> On Wed, Feb 19, 2014 at 01:58:42PM +0100, Gunnar Nordenstam wrote:
> > Hello Nick Drage,
>
> Hi - but bear in mind this email is still on the mailing list :)
>
>
> > I'm back in my home and I've started trying to get the synchronization
> > to work between my S3 and my Windows partition on my MAC.
> >
> > First I logged on to my Cisco Router and checked the settings under
> > Wireless Profile Configuration.
> >
> > It says Broadcast SSID enabled.
>
> Confirm that an option called "wireless isolation" *isn't* enabled, or
> similar.
>
> Apologies if I've asked you to check that before, and you already have,
> this is a complex problem with complex threads of email behind it.
>
>
> > When I tried to ping - it didn't ping
> >
> > Last login: Wed Feb 19 11:16:48 on ttys000
> > Gunnar-Nordenstam-2013:- gunnarnordenstam$ ping 192.168.1.105:8080
> > ping: cannot resolve 192.168.1.105:8080: Unknown host
>
> Ah, you'll need to use the command:
>
> ping 192.168.1.5
>
> The ":8080" is the port number on that IP address used by the WebDAV
> server, the ping command only tests connectivity to hosts, not to ports
> on those hosts.
>
>
> > Gunnar-Nordenstam-2013:- gunnarnordenstam$ ping
> http://192.168.1.105:8080
> > ping: cannot resolve http://192.168.1.105:8080: Unknown host
>
> Ah, "http://" is for URLs, and shows the protocol to be used to connect
> to a resource. In this case you're just testing basic connectivity.
> With the WebDAV server running try putting
>
> http://192.168.1.105:8080
>
> into a browser and see if you can access anything.
>
>
> > So as you said there is a connectivity problem. Are there more
> > potential configuration issues on a Cisco Small Business Router RV220W
> > ?
>
> Probably not - let's get the connectivity tests sorted and take it from
> there.
>
>
> > I have an old Linksys Wireless G Broadband Router. Should I try to
> > change back to that one? There are probably fewer fancy settings that
> > I don't understand.
>
> Let's keep that option as a "weapon of last resort"; I think it's a
> better idea to wrangle with most complex equipment that gives you more
> information and control than simpler equipment that makes complex
> decisions on your behalf.
>
>
> --
> "Individual parental responsibility has a much better hope
> of looking after our children than pretending that we can block something
> when we cannot."
>
>
>