routing problem

Alaor Barroso de Carvalho Neto alaorneto at
Fri Nov 23 04:59:21 PST 2007

OK guyz, I did some tests and I found the error, like you said, it's a
config problem with the routes, I thought the routed daemon would care of it
for me but it seems like it don't. Please I ask you to forget the scenario I
said before, now what i have is:

The dns server is now with the IP But to turn things more easy
I installed it in the FreeBSD box that is gonna be my gateway and proxy
machine, so the problem isn't about the dns anymore.

I work in a school and I have now this sccenario two local networks,
192.168.1/24, an administrative network and 192.168.2/24, an academic
network, plus I must have access to a network of other school with the ip
10.10/16, because they share their database serverwith us. So the FreeBSD
machine have four network cards:

em0 external world XXX.XXX.XXX.XXX
rl0 adm
rl1 acad
rl3 database

They are all separated networks. What I want: 192.168.2 should only access
the internet, shouldn't have access to 192.168.1 or 10.10/16.
192.168.1should access the internet and
10.10/16, but shouldn't access the academic network. 10.10/16 should access
only the 192.168.1 network, but it's not a problem if they had access to
internet too.

How I would set up my rc.conf with my static routes?

Thankz for the attention you're having with me guyz, hugs!

2007/11/21, Steve Bertrand <iaccounts at>:
> Alaor Barroso de Carvalho Neto wrote:
> > Sorry,
> >  searchdomain xxxx.xxxx.xxxx.xxxx
> > nameserver
> >
> > not as I've said before.
> What about:
> # dig @
> Also, I don't know if it has any impact, but my resolv.conf shows just
> 'search' as opposed to searchdomain. Perhaps you could fix
> that to see if it helps.
> Steve

Alaor Neto
CEFET Campos/UNED Macaé
Coordenação de Tecnologia da Informação
(22) 9217-3198 / (22) 2773-6530 ramal 2035

More information about the freebsd-questions mailing list