[Cialug] Firewall question

[Tom Sellers]

I understand the issue that you are bringing up and I tend to agree.  Not
being an expert on wireless routers by any means I do not completely
understand the internal workings.  Before I ever started this process I had
noticed that my Netgear rr worked someone odd in my mind.  However
everything operated normally from a user point of view however.

Here is what I mean.  My original Netgear router was set up as 192.168.1.1
which is the default out of the box.  I keyed in two DNS server IP
addresses as primary and secondary and the gateway IP defaulted to
192.168.1.1 as well.  If I would check a Windows client IP it would show
the gateway, DNS, and DHCP servers all as 192.168.1.1.

My setup seems to be working from a client machine viewpoint right now and
the way that I have gone about making it work is as follows.  The inside of
the firewall has a fixed IP of 192.168.9.254 as stated.  It is physically
connected to the WAN port of the secondary router.  The secondary router is
setup with a fixed IP of 192.168.9.1 and a gateway address is set up as
192.168.9.254.  I can ping out to the internet.  I can get name resolution
on the secondary network as well.  Is the firewall doing its job?  I don't
know!  I continue to look into that but do not know how to adequately test
it.


On Wed, Mar 8, 2017 at 12:50 PM, David Champion <dchamp1337 at gmail.com>
wrote:

> Your default route on LMINT is 192.168.9.1 which is your Router/AP,
> shouldn't it be 192.168.9.254 which is your Firewall's LAN IP?
>
> -dc
>
> On Tue, Mar 7, 2017 at 3:15 PM, Tom Sellers <tsellers2009 at gmail.com>
> wrote:
>
> > Here are the two things you asked about above.
> >
> >
> >
> > On Tue, Mar 7, 2017 at 12:45 PM, Barry Von Ahsen <vonahsen at gmail.com>
> > wrote:
> >
> > > could you also share
> > >
> > > iptables -n -L -t nat
> > >
> > > and
> > >
> > > cat  /proc/sys/net/ipv4/ip_forward
> > >
> > >
> > >
> > >
> > >
> > >
> > > -barry
> > >
> > >
> > > > On Mar 6, 2017, at 7:01 PM, Tom Sellers <tsellers2009 at gmail.com>
> > wrote:
> > > >
> > > > Here is the screen shot of the command ran on the firewall server.
> > > >
> > > > On Mon, Mar 6, 2017 at 5:24 PM, Nicolai <nicolai-cialug at chocolatine.
> > org>
> > > > wrote:
> > > >
> > > >> On Mon, Mar 06, 2017 at 04:57:45PM -0600, Tom Sellers wrote:
> > > >>
> > > >>> Is there a way to look at the existing firewall setup?
> > > >>
> > > >> Yes.  As root, type:
> > > >>
> > > >> iptables -L -n
> > > >>
> > > >> Read the manual page to see what each option does.
> > > >>
> > > >> To get the best help, copy/paste the output here.
> > > >>
> > > >>> I am open to a different firewall option that would run on an older
> > > piece
> > > >>> of hardware since most of my hardware is not very up to date.
> > > >>
> > > >> Just so you know, simple NAT routers and firewalls require minimal
> > > >> resources.  Just about any old box with 2+ network cards should
> work.
> > > >>
> > > >> Nicolai
> > > >> _______________________________________________
> > > >> Cialug mailing list
> > > >> Cialug at cialug.org
> > > >> http://cialug.org/mailman/listinfo/cialug
> > > >>
> > > > <Screenshot from 2017-03-06 20_54_21.png>___________________
> > > ____________________________
> > > > Cialug mailing list
> > > > Cialug at cialug.org
> > > > http://cialug.org/mailman/listinfo/cialug
> > >
> > > _______________________________________________
> > > Cialug mailing list
> > > Cialug at cialug.org
> > > http://cialug.org/mailman/listinfo/cialug
> > >
> >
> > _______________________________________________
> > Cialug mailing list
> > Cialug at cialug.org
> > http://cialug.org/mailman/listinfo/cialug
> >
> >
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>