From owner-freebsd-questions Mon Jul 19 16: 4:24 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mailmtx.acnet.net (mailmtx.acnet.net [170.76.16.130]) by hub.freebsd.org (Postfix) with ESMTP id 0CD4F14CD5 for ; Mon, 19 Jul 1999 16:04:12 -0700 (PDT) (envelope-from denp@acnet.net) Received: from denpmfe ([170.76.16.29]) by mailmtx.acnet.net (Post.Office MTA v3.5.3 release 223 ID# 0-52476U50000L50000S0V35) with SMTP id net for ; Mon, 19 Jul 1999 18:02:08 -0500 Message-Id: <4.1.19990719175537.009b7900@mailmtx.acnet.net> X-Sender: denp@mailmtx.acnet.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 19 Jul 1999 18:02:04 -0500 To: freebsd-questions@FreeBSD.ORG From: Ivan Villalobos Subject: FreeBSD + Cisco Access Lists Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I did not know where to post this to, I hope someone can help me or clarify this for us. We just started adding some FreeBSD servers to our network, but we are just facing a problem. When we put an access list on a cisco router, blocking all incoming ICMP traffic to the FreeBSD server, the server (a DNS server) is not able to resolve any name, when we take the access list out, it works. It would appear at first glance that there is a problem in the access list, but the other DNS server, running Solaris x86 2.6 work just fine, same access list. What is more, this FreeBSD installation is replacing an old Solaris x86 server, that worked just fine with the same access list. My question is: is there anything special in the TCP/IP code that might be affecting our installation of FreeBSD?, the release we are running is 3.2-RELEASE. Any idea, suggestion will be GREATLY appreciated. Best regards. Ivan Villalobos AcNet USA, Inc. Network Services NOC. McAllen, TX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message