Hi Andrew>First off, I passed, which makes me a Cisco Certified
>Network Associate. Guess I could say I'm well pleased. >All
>the work over Christmas and New Year was worthwhile.
I'm delighted for you. Many congrats.
>The router provides a useful first line of defence >against
>hacking. I presume you're doing NAT on the router and use
>a private address range (usually 192.168.x.x) on your
>internal network. With this setup, it's not possible for
>someone on the outside to make a connection to your PC.
>Therefore, the ZoneAlarm alerts disappear.
That's what appears to be happening. I'm still very new to this but the router sets itself to 192.169.0.1 then assigns whatever it wants to, to the PCs on the network, though they're always 192.168.0. something
>Some provisos
>apply here which is why I suggested filtering on the
>routers external interface for any packets that appear to
>have addresses in your private address range.
I understand the logic of what you're saying but don't know how to do this. I don't even know if I can with this router.
>If you're interested in more detail then shout and I'll >do
>my best to fill in the blanks. Specifically, if you want
>to make services available to the outside world then
>you'll need to set up static port translations on the
>router.
At this stage I don't need to make any services available so perhaps it's not necessary anyway. However, you may rest assured that I'll take advantage of your knowledge if I need to in the future 
.
Paul
10 mls SE of EGLL
Printer-friendly
version of this topic
Bookmark this topic
(Registered users only)
FSFORUM
![[Crew]](http://www.flightadventures.com/Forum/htdocs/dcforum/Images/1bar.gif)
![[Sysop]](http://www.flightadventures.com/Forum/htdocs/dcforum/Images/3bar.gif)
![[Guest]](http://www.flightadventures.com/Forum/htdocs/dcforum/Images/key-s.gif)
![[Admin]](http://www.flightadventures.com/Forum/htdocs/dcforum/Images/4bar.gif)