Thanks, all. Yes, I know how to do this from the GUI (we've got seven of
these in the field, all on Windows networks, none providing DHCP). I need to
do this via the CLI because I don't want to connect it to the network and
start issuing conflicting DHCP addresses. Since it is on our VM host, I also
don't have any spare NICs to assign it to a different, isolated network into
which I could plug my laptop. I am therefore going in via the console
(through vSphere).

 

I shall edit gui.network.conf, as I am very familiar with the file, and
would prefer to be able to hop back onto the GUI as soon as I can, and
revert the change if required.

 

Thanks again

 

Tom

 

 

From: Darrick Hartman [mailto:[email protected]] 
Sent: 19 April 2012 21:44
To: 'AstLinux Users Mailing List'
Subject: Re: [Astlinux-users] Disable DHCP from CLI

 

James,

 

Yes, editing the gui.network.conf file would be best, if that exists.  If
it's not there, using user.conf is recommended.  I will admit that a setting
in user.conf would over-ride anything in gui.foo.conf since the rc.conf file
is generated in alpha-numerical order from the files in /mnt/kd/rc.conf.d/

 

Darrick

 

From: James Babiak [mailto:[email protected]] 
Sent: Thursday, April 19, 2012 3:27 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Disable DHCP from CLI

 

True - my comment about stopping dnsmasq was meant as a temporary stopgap
solution so he could plug it in to the network without worrying about the
box responding to DHCP requests. IE: stop dnsmasq, plug in network cable,
assign IP, access web interface to make permanent changes - not as a
permanent solution.

Regarding your suggestion about using rc.conf or user.conf, wouldn't it be
better to edit the gui.network.conf file? This way it would be read by the
GUI when he logged into it and he could revert those changes if necessary
through it down the road. If he created a supplemental config file, he would
then need to manually edit/remove it later, and the web interface wouldn't
be in sync.

-James

On Thu, Apr 19, 2012 at 3:13 PM, Darrick Hartman <[email protected]>
wrote:

Tom,

This is a feature that we implemented for that very reason.  I installed
AstLinux on a network that had a Windows DHCP server.  A Windows network
works much better if it's allow to do DHCP.

In the rc.conf (/mnt/kd/rc.conf if you have a single file, or
/mnt/kd/rc.conf.d/user.conf if using the rc.conf.d directory) specify
NODHCP="ethX" where ethX is the network adapter on the LAN side.

James said this in his email, but he also said to stop dnsmasq.  I would not
leave that in a stopped state.  Stop dnsmasq as he described, make this
change, then issue the gen-rc-conf command at the CLI to re-create the
/tmp/etc/rc.conf file (which is linked to from /etc/rc.conf and generated at
startup).  Finally restart dnsmasq for the changes to take effect. (or
reboot).

The default behavior of providing dhcp leases is fine as long as the lan is
not shared by a Windows domain controller.

Darrick


-----Original Message-----
From: Tom Chadwin [mailto:[email protected]]
Sent: Thursday, April 19, 2012 10:23 AM
To: 'AstLinux Users Mailing List'
Subject: [Astlinux-users] Disable DHCP from CLI

Hello all

This must be quite a common request. How do I disable DHCP before I connect
Astlinux to a network? I obviously can't use the GUI, so how do I do it from
the command line? I won't tell you the nickname one of my colleagues gave
Astlinux after I mistakenly connected it to a live LAN once and it started
issuing DHCP addresses in conflict with our domain controllers.

Thanks

Tom

----------------------------------------------------------------------------
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
[email protected].

 

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].

Reply via email to