If I was in your boat I would ditch ICS completely.
Replace the current router with a wireless N modem router.

Connect everything to the new wireless router.

If a wired connection to everything is no longer possible I would go for wireless or homeplugs.

ICS just is not needed and is limited. I've used it and found it a nightmare in terms of port forwarding etc. Sounds a very complicated and confussing setup

In reply to a post by rt2000:

Thanks for all the replies.

Okay, the router works fine and is stable so no issues there. The ICS is something I set up years ago when I decided to give internet access to all the computers (dial up connection then later ISDN at that time). At that stage the whole thing worked via an 8 port switch. Since broadband/adsl all I've had to do is change the incoming equipment ie. the router. Everything else works just fine and as they say, if it ain't broke don't fix it

To fill in any other points (wish i could see all the replies right now!) there are 2 spare ports on the router but both used on an at-hoc basis. I have spare capacity on the switch's to add a WAP unit which I want on the LAN side so I can assign it a private address to fit in with the rest of the PC's/printers etc. on the LAN.

Hoping I've covered most replies there from memory. Thanks again to all

Ron

Looking at this situation I would do the following.

Replace current router with a wireless modem router such as the netgear dgn2000

Then plug the switch into an available port on the new wireless router. Plug the current ethernet things into the switch / router

Laptop = wireless.

Something like http://s7.postimage.org/i3jjd5agr/my_setup.png

No sharing via the pc etc

Edited by ukhardy07 (Mon 30-Apr-12 16:57:52)

I tend to get a sticky label and stick management IP details underneath the router.

By having your AP not on the IP network, there may be some security benefit, as in people cannot attempt to hack it through vulnerabilities if they end up on the wireless network, e.g. poor choice of security key

You've lost me there Andrew.

1.A label stuck under a router, is a good way to remember IP details of it, and security phrase. Assuming you trust people who are in your property.

2. By having the AP on an IP in the LAN's subnet, the possibility is higher, that someone who does get into the wireless network could then access said AP.

Clearer? If not I'll climb back into my javascript hole

In reply to a post by RobertoS:

I suppose that is a good idea for ongoing configuration/maintenance of the wireless security, rather than (I assume) messing about with a direct ethernet connection to it from the PC? Though it should be possible to pick up the current IP address from the router if it wasn't fixed?

Depends on the main router and how confusing its web interface can be - for example some Thomson products.

Apple Airport Express is quite a cheap way to add WiFi capabilities, although its only single stream N - and it doesn't need a fixed IP, the management tool (Windows and Mac, not Linux) finds it by the MAC address on the network.

If you want a high performance dual band N device (40mhz only at 5ghz / 20mhz at 2.4ghz) then the Airport Extreme is pretty impressive, and you can set it to WAP mode.

Again many thanks for all the responses.

I think the general trend is towards a wireless router so I will investigate that I think. I'm in dispute with myself now as to weather to take the LAN off internet access now I'm giving things further thought. In the main there is only one machine that is used online in the main anyway. So this post has at least made me think of a longer term plan and given the wireless router route ... sorry about the pun ... it is available for the laptop and the phone too should I need access.

Again, many thanks for all the replies and thoughts. Very much appreciated

Ron

In reply to a post by MrSaffron:

1.A label stuck under a router, is a good way to remember IP details of it, and security phrase. Assuming you trust people who are in your property.

2. By having the AP on an IP in the LAN's subnet, the possibility is higher, that someone who does get into the wireless network could then access said AP.

Clearer? If not I'll climb back into my javascript hole

Point 1 wasn't my problem .

Point 2 still has me stuck. I don't understand how the AP has access to the modem (component), via the router (component), if it doesn't have an IP address in the subnet range of the router. So if the router is 192.168.1.254 for example, how does an AP with either no IP address or a preset IP address of say 192.168.0.100 get through?

It doesn't, think of the AP as a piece of cable or an unmanaged hub/switch - it's just putting packets from the air onto the wire. It doesn't care what's in the packets as it runs at layer 2 (IP addresses are a layer higher at layer 3).

If you want to manage / configure the AP, you need to have an IP address that's reachable - but this is only to access the AP itself, it has no effect on the wireless traffic passing through it.

Thanks . I think I get that. My ISO-layer knowledge disappeared years ago. I used to know the gist it but it wasn't necessary in my day-to-day life even then. I retain enough to see what you mean .