From: Edmundo Carmona <eantoranz@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: rules for dhcp server
Date: Tue, 20 Sep 2005 08:40:52 -0400 [thread overview]
Message-ID: <65aa6af90509200540681f65b8@mail.gmail.com> (raw)
In-Reply-To: <a0f69e5050920053621fc6fa5@mail.gmail.com>
check with netstat to see what port dhcpd is listening to.
something like
netstat -lutpn | grep dhcp
will do.
On 9/20/05, Askar <askarali@gmail.com> wrote:
> hi list
>
> I'm configuring a firewall on dhcp server, i'm a bit confuse which port to
> allow on INPUT that users (clients) get IP from the server
>
> from /etc/sevices...
>
> bootps 67/tcp dhcps #Bootstrap Protocol Server
> bootps 67/udp dhcps #Bootstrap Protocol Server
> bootpc 68/tcp dhcpc #Bootstrap Protocol Client
> bootpc 68/udp dhcpc #Bootstrap Protocol Client
> dhcpv6-client 546/tcp #DHCPv6 Client
> dhcpv6-client 546/udp #DHCPv6 Client
> dhcpv6-server 547/tcp #DHCPv6 Server
> dhcpv6-server 547/udp #DHCPv6 Server
>
> lot of other services do runnig on this machine, however i'm very clear
> about all other services, ie which port to allow etc
> All the client machines are running MS. Therefore any other good suggestion
> will be appreciated to machine the network efficient.
>
> regards
>
> Askar
> --
> Unix is very simple, but it takes a genius to understand the simplicity.
> (Dennis Ritchie)
>
next prev parent reply other threads:[~2005-09-20 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 12:36 rules for dhcp server Askar
2005-09-20 12:40 ` Edmundo Carmona [this message]
2005-09-20 13:46 ` /dev/rob0
2005-09-21 4:32 ` Askar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65aa6af90509200540681f65b8@mail.gmail.com \
--to=eantoranz@gmail.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox