Sponsored Content
Full Discussion: Linux Firewall
Special Forums IP Networking Linux Firewall Post 82715 by ameya_shaligram on Tuesday 6th of September 2005 12:14:27 AM
Old 09-06-2005
Linux Firewall

ON A LINUX NETWORK, HOW DO I ASSIGN IP ADDRESSES TO OTHER TERMINALS AND AFTER THAT HOW I CAN DENY/GRANT ACCESS TO TERMINALS ON A LAN TO MY TERMINAL.PLEASE SPECIFY THE EXACT COMMANDS.kINDLY HELP ME
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how to configure a linux box as a firewall using iptables

I have already compiled the kernel and configured it to run as a firewall. My computer has 2 NICs and is on two seperate networks. I can ping both networks from my computer, but workstations on one network can not ping workstations on the other. What Scripts or commands do I need to install ? (2 Replies)
Discussion started by: Deuce
2 Replies

2. Cybersecurity

Linux Firewall

Does anyone know where I can find some Documentation on building a linux firewall. (4 Replies)
Discussion started by: aojmoj
4 Replies

3. Shell Programming and Scripting

linux firewall

could anybody please tell me the best fire wall for linux . (3 Replies)
Discussion started by: Raom
3 Replies

4. UNIX for Advanced & Expert Users

linux firewall / dns issue

I have set up a linux (red hat 9) box as my main internet router. I am also running a DNS server on it. What are the rules i have to implement to allow DNS queries through the firewall from outside so that the outside world can see my domains? (1 Reply)
Discussion started by: frankkahle
1 Replies

5. Cybersecurity

Help needed in IPTables firewall/router setup - Linux

HI all, I have setup IPTables firewall/Router and my home network, with address space 192.168.10.XXX Form my private network hosts, i can ping the gateway ( 192.168.10.101 ) , but the reverse is not happening. Can someone help me as of what i need to do, so that i can ping my private... (1 Reply)
Discussion started by: chandan_m
1 Replies

6. IP Networking

Configuring Linux as a firewall

i have a linux server runnig oracle applications. i need to access this server from putty using ssh through internet. i did by registering my static ip with the dnydns.org and i am able to connect to the server. but now there is no security to authenticate any user as any one knowing the... (6 Replies)
Discussion started by: u.n.i.x
6 Replies

7. UNIX for Advanced & Expert Users

Linux bridged firewall - monitor traffic & block IP

Hi All, I successfully configured a DEBIAN Lenny bridged firewall using ebtables. The bridged interface is br0. The ethernet interface are eth0 & eth1 respectively. All the traffic are transparently passing my firewall but i need to find & block temporarily the bandwidth abusers. Can... (1 Reply)
Discussion started by: coolatt
1 Replies

8. Shell Programming and Scripting

Good way to check firewall port on Linux centos 7

Hi, I need to know what kind of firewall settings does the linux box have? Is port 25 blocked in any way? Linux techx 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I'm coming from this thread. (1 Reply)
Discussion started by: mohtashims
1 Replies

9. Linux

Linux and SCO ppp, firewall issue?

I' m playng a little retrocomputing. I have setup a virtual machine with SCO unix(3.2v4.2) on qemu The machine start, the novell2000 card(ne2k_pci,ne2k_isa) unfortunately not,probably driver issue. So I try the slirp with this procedure On SCO netconfig add chain..sl ..etc On... (2 Replies)
Discussion started by: Linusolaradm1
2 Replies
Qpsmtpd::DSN(3pm)					User Contributed Perl Documentation					 Qpsmtpd::DSN(3pm)

NAME
Qpsmtpd::DSN - Enhanced Mail System Status Codes - RFC 1893 DESCRIPTION
The Qpsmtpd::DSN implements the Enhanced Mail System Status Codes from RFC 1893. USAGE
Any qpsmtpd plugin can access these status codes. All sub routines are used the same way: use Qpsmtpd::DSN; ...; return Qpsmtpd::DSN->relaying_denied(); or return Qpsmtpd::DSN->relaying_denied("Relaying from $ip denied"); or return Qpsmtpd::DSN->relaying_denied(DENY,"Relaying from $ip denied"); If no status message was given, it will use the predefined one from the RFC. If the first argument is numeric, it will use this as a return code, else the default return code is used. See below which default return code is used in the different functions. The first example will return (DENY, "Relaying denied"); the others (DENY, "Relaying from $ip denied"); which will be returned to qpsmtpd. In those sub routines which don't start with addr_, sys_, net_, proto_, media_, sec_ I've added a default message which describes the status better than the RFC message. ADDRESS STATUS
addr_unspecified X.1.0 default: DENYSOFT no_such_user, addr_bad_dest_mbox X.1.1 default: DENY addr_bad_dest_system X.1.2 default: DENY addr_bad_dest_syntax X.1.3 default: DENY addr_dest_ambigous X.1.4 default: DENYSOFT addr_rcpt_ok X.1.5 default: OK addr_mbox_moved X.1.6 default: DENY addr_bad_from_syntax X.1.7 default: DENY addr_bad_from_system X.1.8 default: DENY MAILBOX STATUS
mbox_unspecified X.2.0 default: DENYSOFT mbox_disabled X.2.1 default: DENY ...but RFC says: The mailbox exists, but is not accepting messages. This may be a permanent error if the mailbox will never be re-enabled or a transient error if the mailbox is only temporarily disabled. mbox_full X.2.2 default: DENYSOFT mbox_msg_too_long X.2.3 default: DENY mbox_list_expansion_problem X.2.4 default: DENYSOFT MAIL SYSTEM STATUS
sys_unspecified X.3.0 default: DENYSOFT sys_disk_full X.3.1 default: DENYSOFT sys_not_accepting_mail X.3.2 default: DENYSOFT sys_not_supported X.3.3 default: DENYSOFT Selected features specified for the message are not supported by the destination system. This can occur in gateways when features from one domain cannot be mapped onto the supported feature in another. sys_msg_too_big X.3.4 default DENY NETWORK AND ROUTING STATUS
net_unspecified X.4.0 default: DENYSOFT net_directory_server_failed, temp_resolver_failed X.4.3 default: DENYSOFT net_system_congested X.4.5 default: DENYSOFT net_routing_loop, too_many_hops X.4.6 default: DENY, but RFC says: A routing loop caused the message to be forwarded too many times, either because of incorrect routing tables or a user forwarding loop. This is useful only as a persistent transient error. Why do we want to DENYSOFT something like this? MAIL DELIVERY PROTOCOL STATUS
proto_unspecified X.5.0 default: DENYSOFT proto_invalid_command X.5.1 default: DENY proto_syntax_error X.5.2 default: DENY proto_rcpt_list_too_long, too_many_rcpts X.5.3 default: DENYSOFT proto_invalid_cmd_args X.5.4 default: DENY proto_wrong_version X.5.5 default: DENYSOFT MESSAGE CONTENT OR MESSAGE MEDIA STATUS
media_unspecified X.6.0 default: DENYSOFT media_unsupported X.6.1 default: DENY media_conv_prohibited X.6.2 default: DENY media_conv_unsupported X.6.3 default: DENYSOFT media_conv_lossy X.6.4 default: DENYSOFT SECURITY OR POLICY STATUS
sec_unspecified X.7.0 default: DENYSOFT sec_sender_unauthorized, bad_sender_ip, relaying_denied X.7.1 default: DENY sec_list_dest_prohibited X.7.2 default: DENY sec_conv_failed X.7.3 default: DENY sec_feature_unsupported X.7.4 default: DENY sec_crypto_failure X.7.5 default: DENY sec_crypto_algorithm_unsupported X.7.6 default: DENYSOFT sec_msg_integrity_failure X.7.7 default: DENY perl v5.14.2 2009-04-02 Qpsmtpd::DSN(3pm)
All times are GMT -4. The time now is 01:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy