You shouldn't need the out rule; until a firewall is applied,
everything is accepted.
However, the simple rule is protocol any action accept. That should
do it if you
want to be thorough :-)
Justin
On Jan 28, 2008 7:28 AM, Nathan McBride [EMAIL PROTECTED] wrote:
Hey guys,
I just installed
You're right it looks exactly like that bug.
When I do a show version all I get is:
Baseline Version: vc3
Booted From: disk
Because of the similarity I would assume I haven't gotten the latest
yet. How should I go about updating it?
When i do just 'aptitude' it gives me a confusing ncurse
Nate,
Are you using version 2.3? It seems like you might be experiencing bug
2502:
http://bugzilla.vyatta.com/show_bug.cgi?id=2502
This bug was resolved with the 2.3.1 release, so you may want to upgrade
if you haven't already.
If you're already using the latest version and still getting
Nate,
There is a walkthrough on the upgrade process in the Vyatta wiki,
http://www.vyatta.com/twiki/bin/view/Community/HowToUpdate
However, I think this fix may not have been published to the community
edition repositories yet.
You may need to use the workaround and create the state-matching
Nathan,
The keyword is all instead of any.
Cheers,
John
- Original Message -
From: Nathan McBride [EMAIL PROTECTED]
To: Vyatta-users@mailman.vyatta.com
Sent: Monday, January 28, 2008 9:12:41 AM (GMT-0800) America/Los_Angeles
Subject: Re: [Vyatta-users] Firewall question.
Also, when I
Hi Josh,
There is no firewall by default on Vyatta.
Your firewall rule does not prevent packets from external to your
Vyatta itself.
You can apply the firewall instance as in, out and local per interface.
You have used in, meaning that packets entering that interface will be
filtered by the
Hello!
I have a small issue with my firewall.
When I use nmap it show all ports are open when I scan any vif address.
The interface is closed with the exception of port 22 on the main
interface IP.
I added the following to the eth1 interface as firewall local which is
connected to the
