Newb question setting up webserver on Debian

Hello all,
I have has look aorund the forums via google, and it seems every
forum topic answers only ever one piece of the puzzle. So.... I'd like
to know how many pieces to the puzzle.

I'm currently setting up a static IP on my LAN for my webserver.

ifconfig eth0 192.168.1.129

or...

pico /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.129
netmask 255.255.255.0
broadcast 192.168.1.255

C-o C-x

/etc/init.d/networking restart

*************************************************
I'm using the router as the DNS for the local network (3 windows
machines), so every so often something on the Linux box asks for a new
IP lease ( and gets set back to 192.168.1.100). Turn off dhclient3?

ps -A | grep -e dhclient3
kill -9 <the PID numbers>

Will this break anything? Is there a better way to kill dhclient3? The
man page doesn't say anything.

*************************************************
Now change the configuration file for the website (default in this
case):
pico /etc/apache2/sites-available/default
<make changes as required, save and exit>

************************************************** *

Is there anything I've forgotten, missed, or should do differently?

Regards,
Timbo

On 5ÔÂ31ÈÕ, ÏÂÎç11ʱ43·Ö, macoovacany <macoovac...@gmail.com> wrote:
> Hello all,
> I have has look aorund the forums via google, and it seems every
> forum topic answers only ever one piece of the puzzle. So.... I'd like
> to know how many pieces to the puzzle.
>
> I'm currently setting up a static IP on my LAN for my webserver.
>
> ifconfig eth0 192.168.1.129
>
> or...
>
> pico /etc/network/interfaces
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> allow-hotplug eth0
> iface eth0 inet static
> address 192.168.1.129
> netmask 255.255.255.0
> broadcast 192.168.1.255
>
> C-o C-x
>
> /etc/init.d/networking restart
Anything wrong here?
It works as expected, isn't it?
>
> *************************************************
> I'm using the router as the DNS for the local network (3 windows
> machines), so every so often something on the Linux box asks for a new
> IP lease ( and gets set back to 192.168.1.100). Turn off dhclient3?
>
> ps -A | grep -e dhclient3
> kill -9 <the PID numbers>
>
> Will this break anything? Is there a better way to kill dhclient3? The
> man page doesn't say anything.
>
How about removing dhcp3-client package?

> *************************************************
> Now change the configuration file for the website (default in this
> case):
> pico /etc/apache2/sites-available/default
> <make changes as required, save and exit>
>
Any question here?
> ************************************************** *
>
> Is there anything I've forgotten, missed, or should do differently?
>
> Regards,
> Timbo

Regards,
Kun

On Jun 2, 5:54 am, kun niu <haoniu...@gmail.com> wrote:
> On 5ÔÂ31ÈÕ, ÏÂÎç11ʱ43·Ö, macoovacany <macoovac....@gmail.com> wrote:
>
> > Hello all,
> > I have has look aorund the forums via google, and it seems every
> > forum topic answers only ever one piece of the puzzle. So.... I'd like
> > to know how many pieces to the puzzle.
>
> > I'm currently setting up a static IP on my LAN for my webserver.
>
> > ifconfig eth0 192.168.1.129
>
> > or...
>
> > pico /etc/network/interfaces
>
> > auto lo
> > iface lo inet loopback
>
> > auto eth0
> > allow-hotplug eth0
> > iface eth0 inet static
> > address 192.168.1.129
> > netmask 255.255.255.0
> > broadcast 192.168.1.255
>
> > C-o C-x
>
> > /etc/init.d/networking restart
>
> Anything wrong here?
> It works as expected, isn't it?
>
> > *************************************************
> > I'm using the router as the DNS for the local network (3 windows
> > machines), so every so often something on the Linux box asks for a new
> > IP lease ( and gets set back to 192.168.1.100). Turn off dhclient3?
>
> > ps -A | grep -e dhclient3
> > kill -9 <the PID numbers>
>
> > Will this break anything? Is there a better way to kill dhclient3? The
> > man page doesn't say anything.
>
> How about removing dhcp3-client package?
>
>
>
> > *************************************************
> > Now change the configuration file for the website (default in this
> > case):
> > pico /etc/apache2/sites-available/default
> > <make changes as required, save and exit>
>
> Any question here?
> > ************************************************** *
>
> > Is there anything I've forgotten, missed, or should do differently?
>
> > Regards,
> > Timbo
>
> Regards,
> Kun

Hi Kun ,


I think you can use this command also .
pkill -9 dhclient3
which will kill all the processes with the dhclient3.


Regards.
zaffar

The question I was trying to ask was should I kill the dhclient, and
what else depends on it?

Timbo

macoovacany <(E-Mail Removed)> writes:

> The question I was trying to ask was should I kill the dhclient, and
> what else depends on it?

If you're setting your IP address by hand, you can't have dhclient
trying to do it as well. But you're far better off having dhclient do
it, and that has nothing at all to do with setting up a web server.

On Jun 3, 12:39*pm, Joe Pfeiffer <pfeif...@cs.nmsu.edu> wrote:
> macoovacany <macoovac...@gmail.com> writes:
> > The question I was trying to ask was should I kill the dhclient, and
> > what else depends on it?
>
> If you're setting your IP address by hand, you can't have dhclient
> trying to do it as well. But you're far better off having dhclient do
> it, and that has nothing at all to do with setting up a web server.

Static IP from the router to the server. Router is DNS.

So, no problem killing dhclient?

Timbo

macoovacany <(E-Mail Removed)> writes:

> On Jun 3, 12:39*pm, Joe Pfeiffer <pfeif...@cs.nmsu.edu> wrote:
>> macoovacany <macoovac...@gmail.com> writes:
>> > The question I was trying to ask was should I kill the dhclient, and
>> > what else depends on it?
>>
>> If you're setting your IP address by hand, you can't have dhclient
>> trying to do it as well. But you're far better off having dhclient do
>> it, and that has nothing at all to do with setting up a web server.
>
> Static IP from the router to the server. Router is DNS.
>
> So, no problem killing dhclient?

I don't know what "Static IP from the router to the server" means -- if
it means the router is also a DHCP server, and that's how the web server
is getting its IP address, then you need dhclient running (I guess
different people use the term "static" IP address differently -- in my
case, all the machines in the house have static addresses, but they all
get them from a single DHCP server so there's only one place I have to
worry about them).

Otherwise, yes you can kill it.

>
> I don't know what "Static IP from the router to the server" means -- if

Ahhh.... from what you've said, got it exactly correct.

Tim