It is not normally recommended to open port 135 to the internet
If you need outlook - exchange connectivity either use a vpn or rpc
over https
John
Tyrone Miles wrote:
Does anyone have easy directions to allow exchange (Outlook port 135)
through my Vyatta router?
I need traffic to go
Hi Alain,
Take a look at this post:
http://mailman.vyatta.com/pipermail/vyatta-users/2007-November/002406.html
It looks like you're running into bug 2502, which has been fixed in our
most recent set of updates and will no longer be an issue in the next
release.
The link above has more
I also would change rules 20 and 21 such that it's SOURCE port 22, and
not destination port 22. This would apply if you are trying to permit
inbound ssh requests from those specific hosts.
John
Robyn Orosz wrote:
Hi Alain,
Take a look at this post:
Yes, I've had it enabled and working before. The traffic needs to hit a
firewall rule before it'll be logged; you may also need to adjust the global
log level down from it's current default of warning to informational or lower.
Justin
On Feb 1, 2008 2:12 PM, Go Wow [EMAIL PROTECTED] wrote:
last question
because the answer wasn't specific to Vyatta.
Beau Walker - CCNA, Linux+
--
*From:* Go Wow [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, January 29, 2008 3:10 PM
*To:* Beau Walker
*Subject:* Re: [Vyatta-users] Firewall: block internal telnet
Okay
I believe you'd have to set up a firewall on each PC to block telnet
access from the local subnet, or start using VLANs.
The telnet traffic will connect to your internal systems just by going
through your switches with the current configuration. The router will
never even see the traffic.
+
From: Go Wow [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 3:10 PM
To: Beau Walker
Subject: Re: [Vyatta-users] Firewall: block internal telnet
Okay how can I block ssh on router i.e. 192.168.10.45 using firewall, I
want to give access of ssh
This is my firewall config, look in rule 2 192.168.10.2 is my gateway, I
added thinking that my internal LAN users would still have access to
internet but there arent having can someone tell me why? or give me some
pointers please.
firewall {
log-martians: enable
send-redirects:
And I have added it to eth0 for in and local traffic only.
On 30/01/2008, Go Wow [EMAIL PROTECTED] wrote:
This is my firewall config, look in rule 2 192.168.10.2 is my gateway, I
added thinking that my internal LAN users would still have access to
internet but there arent having can someone
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
-Original Message-
From: Adrian F. Dimcev [mailto:[EMAIL PROTECTED] ]
Sent: Sunday, December 23, 2007 8:01 AM
To: Todd Worden
Cc: vyatta-users@mailman.vyatta.com
Subject: RE: [Vyatta-users] Firewall implicit deny all
Hi Todd,
If you define a firewall instance wan2lan as OUT on eth0
: [Vyatta-users] Firewall implicit deny all
Hi Todd,
If you define a firewall instance wan2lan as OUT on eth0 then the
implicit deny you've mentioned only applies to eth0 and only to packets
exiting interface eth0 that are not matched by any of your firewall
rules from that instance.
Per interface
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
Hi Tony,
The firewall configuration syntax only allows 1 source address within each
rule, so for your example you can specify 3 rules, one for each IP address you
want to block.
An-Cheng
Tony Cratz wrote:
Hello:
I'm new to Vyatta any before I start to do an install and
screw
18 matches
Mail list logo
