First of all let me just say ver11.0 is pretty darn cool and I am enjoying it so far. This is the only stump me issue I have found with it so far.
I am running on a core 2 duo 2.2G with 2G ram.
openSuSE11.0 2.6.25.18-0.2 (default)
resume=/dev/sda1 splash=silent showopts acpi=off
2 nics, only one is active until I figure this out.
In YaST setting up DHCP server, everything looks ok until the end when trying to activate dhcp server. I get dhcp server error:
cat: write error: Broken pipe
Name “main::parSed-file” used only once: possible typo at
/usr/lib/YaST2/servers_non_y2/ag_dhcpd_conf line 12 (#1)
(w once) Typographical errors often show up as unique variables names. If you had a good reason for having a unique name, then just mention it again somehow to suppress the message.
NOTE: This warning detects symbols that have been used only once so $c, @c, %c, *c, 8c sub c{}, c() and c (the filehandle or format) are considered the same; if a program uses $c only once but also uses any of the others it will not trigger this warning.
I am only running these servers at this time:
http
ftp
samba
nfs
vnc
This system is for LAN use mainly and an occasional tunnel in from across town to the ftp or vnc over the web. I can run another dhcp server in my router, but I am working toward getting rid of it all together and just using SuSE to handle it all in one box. That is why I have two nics installed at this point. If I can not get dhcp to run then this box will never replace my router. For the time being all other nodes other than my test node are static assigned to avoid the family from griping that they can not get online.
Any input would on this would be great since I have searched the forum with no luck on this issue.
Well, I guess I should pay more attention to Disable smiles in text option in my posting. Duh…I have only been an admin of a bbs for 7 years. Geese you’d think I’d pick up a thing or two in that time.
The smile tung out face is representing the
The line should read:
Name “main:arSed-file” used only once: possible typo at
I also turned the fire wall on and got this one included below the first when I retried after the enable of that such firewall.
Use of uninitialized value $open_firewall in numeric ne (!=) at
/usr/share/YaST2/modules/DhcpServer.pm line 1307 (#1)
(W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a “” or a 0, but maybe it was a mistake.
To supress this warning assign a defined value to your variables.
To help you figure out what was undefined, perl will try to tell you the
name of the variable (if any) that was undefined. In some cases it cannot
do this, so it also tells you what opperation you used that undefined value
in. Note, however, that perl optimizes your program and the operation
displayed in the warning may not necessarily appear literally in you
program. For example, “that $foo” in usually optimized into "that ", $foo, and the warning will refer to the concatentation (.) operator, even though there is no . in your program.
Still racking my brain, I feel as if I am going to have to look at code for this one to correct my issues.
Well here is my update. I modified both files indicated in my error message and it looks like they both just had a typo in them. Since my modifications those errors are gone but I get this instead.
cat: write error: Broken pipe
Should I go get a mop? You know I hate plumbing with a passion. I alway say I would rather get a root canal instead, at least you can get gas during that procedure.
On Sun November 30 2008 11:26 pm, Cyberphillics wrote:
>
> Well here is my update. I modified both files indicated in my error
> message and it looks like they both just had a typo in them. Since my
> modifications those errors are gone but I get this instead.
>
> ________________________________________________________________
>
> cat: write error: Broken pipe
>
> ________________________________________________________________
>
> Should I go get a mop? You know I hate plumbing with a passion. I
> alway say I would rather get a root canal instead, at least you can get
> gas during that procedure.
>
> Any takers on an idea about this now?
>
>
Cyberphillics;
I’ve never used YAST for setting up a dhcp server, but instead have done it
the old fashion way. Here is how to do it manually.
Make sure the package dhcp-server is installed. You can check this in a
terminal window with:
rpm -q dhcp-server
If it is not installed, you need to install it; and this will probably let you
continue with YAST. So I assume it is installed and YAST still fails.
As root you can manually edit /etc/dhcpd.conf. You will need to configure
a number of "option"s, range etc. The version that comes with Suse is fairly
well documented in the comments, but there is additional information/examples
located in the documents. (/usr/share/doc/packages/dhcp-server)
Go to YAST->System-> System services and enable “dhcpd”
If the “broken pipe” error persists, I’d reinstall the dhcp-server package.
You do not need a mop, but perhaps you should hang a “bit bucket” at the
break.
> On Sun November 30 2008 11:26 pm, Cyberphillics wrote:
>
>>
>> Well here is my update. I modified both files indicated in my error
>> message and it looks like they both just had a typo in them. Since my
<snip>
>> Any takers on an idea about this now?
>>
>>
> Cyberphillics;
>
> I’ve never used YAST for setting up a dhcp server, but instead have done it
> the old fashion way. Here is how to do it manually.
>
> 1) Make sure the package dhcp-server is installed. You can check this in a
> terminal window with:
> rpm -q dhcp-server
> If it is not installed, you need to install it; and this will probably let
> you
> continue with YAST. So I assume it is installed and YAST still fails.
>
> 2) As root you can manually edit /etc/dhcpd.conf. You will need to
> configure
> a number of "option"s, range etc. The version that comes with Suse is
> fairly well documented in the comments, but there is additional
> information/examples
> located in the documents. (/usr/share/doc/packages/dhcp-server)
>
> 3) Go to YAST->System-> System services and enable “dhcpd”
>
> If the “broken pipe” error persists, I’d reinstall the dhcp-server package.
>
> You do not need a mop, but perhaps you should hang a “bit bucket” at the
> break.
Almost forgot, you need to open UDP/TCP ports 67 & 68 in the Firewall. (I’m
not positive the TCP ports need to be open, try first with just the UDP ports
open)
