Originally posted by: iDazzler
Hi Gang,
I'm back with one last question. Do I have to have a physical connection (e.g. pc on webramp port ) to webramp to access the system console? I read in the docs but still remain confused. I have been unplugging my jack from my Wireless Router and Plugging it back into the webramp and then changing my ip on the pc that's on the webramp port to 192.168.168.2 ( or any number above 1 e.g. 192.168.168.21...) and putting in the subnet mask and default gateway.
Am I missing something? I'm sure it's got to be simple. Talk about a crash course in networking!
XYZ,
About your instructor's tip if I understand you correctly it would look like this on a wireless router:
DSL/CABLE Modem --- Wireless Router ---WebRamp( Firewall) --PCs
Have you tried it? Any feedback would be appreciated....
Thanks in advance...
the way you laid it out is how my instructor recommends it... and i guess i'll eventually change my setup. my setup has a minor flaw, in that the reflexive access list on 806 opens a hole for a brief period of time, and eventhough this scenario is pretty unlikely, if i'm connected to a device on a proxy, someone else behind that proxy can get access. it was a bit beyond me how someone could actually penetrate the network, but i guess i'll learn that later on.
okay... i'm a bit confused. i thought you said the wireless device was an access point. now you're saying it's a router. that really changes things. i guess i should have picked this up when you mentioned a double NAT. you shouldn't need a direct connection between your console and your webramp.
internet<----->webramp<----->wireless router<----->internal network
internally, you're dealing with 2 networks. what i did when i had the webramp and the linksys device was to create a static route from one network to the other.
you know what, i'm looking at my webramp's static routes right now, and i do have a static route to my internal network... but i don't know why i put one in, because any non-intiated access will still be blocked... but you might want to try a static route. have the external interface on the wireless router act as the gateway to get into your internal network.
give it a try and see what happens.