Hello all.
I am a new suse user. Have been using pclinuxos for about 5 years now. Due to the fact that their ICS module in pclinuxos no longer works I have decided to look around for alternatives. Today I installed suse 11.2 32-bit from a network install. After some googling and searching the forums here, I have found a thred with this link ICS - openSUSE ]. Following the instructions, i first downloaded the dhcp-server via the software manager. When I got to the part where I was to set the dhcp settings in YaST - > Network Services - > DHCP server, I found that the Network Services in yast did not have the DHCP server module. When I attempted to start the DHCPD from YaST - > Network Services - > System Services, it returned error 6 [not configured]. So my question is, is there a GUI utility which will configure the DHCP-Server daemon, or must I do it via the cli? And if set from the cli, is there a gui module I should avoid to prevent the settings from being overwritten?
If it’s a full-blown router that you’re trying to build, then I suppose you need a DHCP server. But it’s not at all mandatory – you can just hook the SuseBox to the internet supply (e.g. your broaband modem, whatever) then use fixed IP in the others machines and hook them through to the SuseBox.
syampillai: Just what I needed, i configured DHCPD with the module.
Unfortunately, Following the instructions on the ICS - openSUSE ] link Did not work. I am sure i omitted some pertinent detail. All of the * relevant settings are listed below:
YaST -> System -> Network Settings -> Routing: Enable Ip Fowarding: Checked.
YaST -> System -> Network Settings -> Global: Traditional Method with ifup
Enable IPv6
DHCP Client identifier:[blank]
Hostname to send: Auto
Change Default Route via DHCP: checked
YaST - > Security & Users - > Firewall - > Interfaces: eth0: Internal Zone
eth1: External Zone
YaST - > Network Services - > DHCP server - > Global Settings - > Domain Name: chowzworld.net
Primary Name Server Ip: 24.217.0.5 [from resolv.conf]
Secondary Name Server Ip: 24.217.201.67 [from resolv.conf]
Default Gateway (router): 192.168.0.254
It seems to me that I have all the settings correct, but I am obviously missing something. If anybody can provide any assistance, I would greatly appreciate it. If there is any additional info which you need with regards to my settings please advise me of them so that I can post that info as well.
Best Regards, CHOW
p.s. @ swerdna: Love your site, much useful info there. I am going to manually set my client box in the interim until I get the bugs out of the DHCPD.*
>
> Thaks for the help all.
>
> syampillai: Just what I needed, i configured DHCPD with the module.
>
> Unfortunately, Following the instructions on the ‘ICS - openSUSE’
> (http://en.opensuse.org/ICS) ] link Did not work. I am sure i omitted
> some pertinent detail. All of the * relevant settings are listed
> below:
>
>>
>>
>> ethernet settings: eth0: ip: 192.168.0.254, mask: /24, hostname:
>> gateway
>> eth1: DHCP4
>>
>> YaST -> System -> Network Settings -> Routing: Enable Ip Fowarding:
>> Checked.
>> YaST -> System -> Network Settings -> Global: Traditional Method with
>> ifup
>> Enable IPv6
>> DHCP Client identifier:[blank]
>> Hostname to send: Auto
>> Change Default Route via DHCP: checked
>>
>> YaST - > Security & Users - > Firewall - > Interfaces: eth0: Internal
>> Zone
>> eth1: External Zone
>>
>> YaST - > Security & Users - > Firewall - > Masquerading: Masqureade
>> Networks: Checked.
>>
>> YaST - > Network Services - > DHCP server - > Card Selection: eth1
>> selected.
>>
>> YaST - > Network Services - > DHCP server - > Global Settings - >
>> Domain Name: chowzworld.net
>> Primary Name Server Ip: 24.217.0.5 [from resolv.conf]
>> Secondary Name Server Ip: 24.217.201.67 [from resolv.conf]
>> Default Gateway (router): 192.168.0.254
>
> It seems to me that I have all the settings correct, but I am obviously
> missing something. If anybody can provide any assistance, I would
> greatly appreciate it. If there is any additional info which you need
> with regards to my settings please advise me of them so that I can post
> that info as well.
>
> Best Regards, CHOW
>
> p.s. @ swerdna: Love your site, much useful info there. I am going to
> manually set my client box in the interim until I get the bugs out of
> the DHCPD.
>
chow-stl;
Can you post the contents of: /etc/dhcpd.conf.
You can use substitute values for any privileged information and to save space
all lines starting with #, i.e. comments. Setting up the DHCP client really
only involves editing the above file and starting the service.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
*
>
> Thanks for the reply venzkep. My dhcpd.conf file is as follows:
>
> option domain-name “chowzworld.net”;
> option domain-name-servers 24.217.0.5, 24.217.201.67;
> option routers 192.168.0.254;
> ddns-update-style none;
> default-lease-time 14400;
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.2 192.168.0.255;
> default-lease-time 14400;
> max-lease-time 8639999913600;
> }
>
> I hope this is the info you needed. Not sure if i included anything
> ‘personal’. it all looks pretty pedestrian to me.
>
> Thanks for the help.
>
> Regards, CHOW
>
>
CHOW;
Try narrowing down the range of your subnet to something like:
range 192.168.0.2 192.168.0.200;
192.168.0.255 is the broadcast address and should not be assigned,
192.168.0.254 is your router and not assigned. The router should be a static
address on your local NIC and not dished out by dhcp. The dhcp server
usually starts with the largest address in the range, thus it is likely to
dish up your broadcast address and router address to other machines.
It would do no harm to add to the subnet section:
option broadcast-address 192.168.0.255;
The max-lease-time you have set seems kind of large to me, I’m not sure just
what the largest value can be but I suggest you change it to something more
like:
max-lease-time 259200;
I would also suggest you move the “options router” statement inside the subnet
definition.
You can edit the file with either:
kdesu kwrite /etc/dhcpd.conf
or
gnomesu gwrite /etc/dhcpd.conf
Configure your local NIC to use the fixed address 192.168.0.254/24 and then
start dhcpd with Yast>System>System Services. Enable it for run level 3 and
5.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
> On Sun January 10 2010 12:16 am, chow-stl wrote:
>
>>
>> Thanks for the reply venzkep. My dhcpd.conf file is as follows:
<snip>
chow-stl;
Addition to last post:
Be sure to open the UDP ports 67,68 (bootps, bootpc) on the Internal zone of
your Suse-firewall.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Thanks again for the assistance venzkep. I think I followed all of your instructions to the letter and it still is not working. For review I am posting the modified dhcpd.conf file to inusure I followed your instructions correctly. Of course there could be some stray typo or other such error on my part and I appreciate your time in reviewing my setup.
>
> Thanks again for the assistance venzkep. I think I followed all of your
> instructions to the letter and it still is not working. For review I am
> posting the modified dhcpd.conf file to inusure I followed your
> instructions correctly. Of course there could be some stray typo or
> other such error on my part and I appreciate your time in reviewing my
> setup.
>
> option domain-name “chowzworld.net”;
> option domain-name-servers 24.217.0.5, 24.217.201.67;
> ddns-update-style none;
> default-lease-time 14400;
> subnet 192.168.0.0 netmask 255.255.255.0 {
> option broadcast-address 192.168.0.255;
> option routers 192.168.0.254;
> range 192.168.0.2 192.168.0.200;
> default-lease-time 14400;
max-lease-time 259200;
}
>
> In addition I did change the firewall settings your noted (port 67,
> 68).
>
> Thanks again for your efforts.
>
> Best Regards, CHOW
>
>
chow-stl;
You have not close the braces. See my edit above. Install the doc rpm for
dhcpd and look at:
/usr/share/doc/packages/dhcp-server
There are a number of examples for the dhcpd.conf that are well documented.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
>
> even tough i never used this the only odd thing in it for me is this { -
> the curly bracket:
> subnet 192.168.0.0 netmask 255.255.255.0 {
>
>
dmera;
The braces are needed to define the options that apply to that particular
subnet, versus global settings. They do, of course, need to be closed.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green