The agony of the language barrier, and not having local support at remote locations grrrrrr
Thanks again From: [email protected] To: [email protected] Subject: Re: [NTSysADM] Router as AP-FIXED Date: Thu, 3 Jul 2014 15:44:45 +0000 I was gonna say... Sent from my iPhone On Jul 3, 2014, at 11:39 AM, "J- P" <[email protected]> wrote: Ok, so as I expected, the connections were wrong- I just wanted to make sure I wasnt loosing my marbles They had the wifi/ap connected to latop only- sigh Thanks all From: [email protected] To: [email protected] Subject: RE: [NTSysADM] Router as AP Date: Thu, 3 Jul 2014 11:22:37 -0400 This is where it fails Internet ---> Firewall/VPN Router (DHCP) No communication between FW/VPN and Wifi/AP, and I suspect it is because there is no place to designate the default gateway on AP I'm actually asking them to send me photos of what is plugged in where, ---> Wifi AP and Wired Clients ---> Wireless Clients Jean-Paul Natola From: [email protected] To: [email protected] Subject: Re: [NTSysADM] Router as AP Date: Thu, 3 Jul 2014 15:07:42 +0000 Here’s how your network layout should look like Internet ---> Firewall/VPN Router (DHCP) ---> Wifi AP and Wired Clients ---> Wireless Clients The wifi AP should have its DHCP server turned completely off and have been assigned a static IP on its LAN interface that doesn’t conflict with your router (sounds like you have the latter done already). Hook it up using the LAN ports and it should basically become an AP instead of a router. You can also make your life a lot easier and just go buy a dedicated AP, but this will let you use what you’ve got. On Jul 3, 2014, at 10:54 AM, J- P <[email protected]> wrote: I have 3 options on the AP DHCP DHCP RELAY NONE should I go relay, and set the Remote DHCP server , Or just disable it all together? Jean-Paul Natola From: [email protected] To: [email protected] Subject: Re: [NTSysADM] Router as AP Date: Thu, 3 Jul 2014 14:14:48 +0000 Serve DHCP on the new VPN router and not the WiFi AP. The AP will just bridge wireless to wired. On Jul 3, 2014, at 10:02 AM, J- P <[email protected]> wrote: Hi all, I have a site where the original wifi/router (cisco RV 120 w) was replaced due to the inability to establish a VPN. We now have a new router in place and it is working fine, however, the new router doesn't have a wifi, so my intent was to just plug in the on the lan so they can have wifi. Here is the setup ISP> WAN port on New VPN router (ip 10.0.4.1) > LAN port on Cisco wifi > Cisco set to 10.0.4.200, dhcp server enabled , range 10.0.4.201-10.0.4.220, The issue I'm facing is that I do not have the ability to specify the default gateway on Cisco (at least I cant see it in the GUI) , as a result when client connects to the wifi it gets an IP of 10.0.4.221 but the gateway it gets is the IP of the cisco (10.0.4.200) as a result they have no internet access. And to add insult to injury , this is in the remote office with the worst connection (256k sat) So trouble shooting has been miserable to say the least- The only upside is that the laptop I'm remoting into has a 3/4g USB key , so it isn't as painful, however the per mb charge is going through the roof. I have this same setup in another office, with the exception that linksys router (providing wifi) has dd-wrt and I am able to specify the gateway.
