SEO

Hello,

this is a Sparcstation 20 with one additional le device (501-2015).

During boot I see:

configuring IPv4 interfaces:ifconfig: #hostname.le0: bad address
le0ifconfig: #hostname.le1: bad address
le1.

bash-2.03# cat hostname.le0
#hostname.le0
Dupre1
bash-2.03# cat hostname.le1
#hostname.le1
Dupre2

bash-2.03#cat hosts

127.0.0.1 localhost loghost Dupre
10.0.0.1 Dupre1
10.0.0.2 Dupre2

bash-2.03# cat netmasks
<snip>
10.0.0.0 255.0.0.0

bash-2.03# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index
1
inet 127.0.0.1 netmask ff000000
le0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.0.0.1 netmask ff000000 broadcast 10.255.255.255
ether 8:0:20:76:2c:cc
le1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 10.0.0.2 netmask ff000000 broadcast 10.255.255.255
ether 8:0:20:76:2c:cd

(had to add an entry for le1 in /etc/init.d/network: /sbin/ifconfig
le1 ether 8:0:20:76:2c:cd - found this on google, but seems it was
necessary in this file and not in another)


Where could I have configured something wrong? I do not really
understand this.

For some help, I would be very thankful. I can give additional
information, but I dont know what else I could add here

Claus

claus@ultima-dragons.org writes:
>Hello,
>
>this is a Sparcstation 20 with one additional le device (501-2015).
>
>During boot I see:
>
>configuring IPv4 interfaces:ifconfig: #hostname.le0: bad address
> le0ifconfig: #hostname.le1: bad address
> le1.
>
>bash-2.03# cat hostname.le0
>#hostname.le0
>Dupre1

Do not do this. Do not try to comment out lines in the hostname.*
files with a '#' character. The startup script that reads those
files does not support comments.

You should have only the one line with the hostname or IP address
in the file.

-Greg
--
Do NOT reply via e-mail.
Reply in the newsgroup.

In article <6pqd801e080snm3m475j0o4vn6hf9riv7g@4ax.com>, Claus Dragon <claus@ultima-dragons.org> writes:
> Hello,
>
> this is a Sparcstation 20 with one additional le device (501-2015).
>
> During boot I see:
>
> configuring IPv4 interfaces:ifconfig: #hostname.le0: bad address
> le0ifconfig: #hostname.le1: bad address
> le1.
>
> bash-2.03# cat hostname.le0
> #hostname.le0
> Dupre1
> bash-2.03# cat hostname.le1
> #hostname.le1
> Dupre2
>
> bash-2.03#cat hosts
>
> 127.0.0.1 localhost loghost Dupre
> 10.0.0.1 Dupre1
> 10.0.0.2 Dupre2
>
> bash-2.03# cat netmasks
> <snip>
> 10.0.0.0 255.0.0.0
>
> bash-2.03# ifconfig -a
> lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index
> 1
> inet 127.0.0.1 netmask ff000000
> le0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
> inet 10.0.0.1 netmask ff000000 broadcast 10.255.255.255
> ether 8:0:20:76:2c:cc
> le1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
> inet 10.0.0.2 netmask ff000000 broadcast 10.255.255.255
> ether 8:0:20:76:2c:cd
>
> (had to add an entry for le1 in /etc/init.d/network: /sbin/ifconfig
> le1 ether 8:0:20:76:2c:cd - found this on google, but seems it was
> necessary in this file and not in another)
>
>
> Where could I have configured something wrong? I do not really
> understand this.
>
> For some help, I would be very thankful. I can give additional
> information, but I dont know what else I could add here
>
> Claus


Have a file hostname.le0 with
Dupre1
and a file hostname.le1 with
Dupre2

If the hostname.* files are present and correct (no #comments)
then /etc/init.d/network does the ifconfig.

Delete your extra ifconfig entries in /etc/init.d/network.


--
Michael Tosch
IT Specialist
HP Managed Services Germany
Phone +49 2407 575 313
Mail: michael.tosch:hp.com

A limerick packs laughs anatomical
Into space that is quite economical.
But the good ones I've seen
So seldom are clean,
And the clean ones so seldom are comical.

Claus Dragon <claus@ultima-dragons.org> writes:

>configuring IPv4 interfaces:ifconfig: #hostname.le0: bad address
> le0ifconfig: #hostname.le1: bad address
> le1.

>bash-2.03# cat hostname.le0
>#hostname.le0
>Dupre1

You can't have comments in the "hostname.*" files.


Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Words to the wise, Casper H.S. Dik <Casper.Dik@Sun.COM> wrote:

>Claus Dragon <claus@ultima-dragons.org> writes:
>
>>configuring IPv4 interfaces:ifconfig: #hostname.le0: bad address
>> le0ifconfig: #hostname.le1: bad address
>> le1.
>
>>bash-2.03# cat hostname.le0
>>#hostname.le0
>>Dupre1
>
>You can't have comments in the "hostname.*" files.
>

this message goes out to all three of you:

thanks for the information, I was not aware that there were files
where you are not allowed to use comments

Claus

Claus Dragon wrote:

>
> thanks for the information, I was not aware that there were files
> where you are not allowed to use comments
>

Comments tend to cause havoc in binary files, as well :-) In fact it's
probably true to say that comments are the exception rather than the
rule, taken all possible types of file!

--
Tony

Words to the wise, Tony Walton <tony.walton@s_u_n.com> wrote:

> > thanks for the information, I was not aware that there were files
> > where you are not allowed to use comments
> >
>
>Comments tend to cause havoc in binary files, as well :-) In fact it's
>probably true to say that comments are the exception rather than the
>rule, taken all possible types of file!

Hm, funny thing is that i have not read anyone mentioning anything
about that before ... like, dont use comments in most files ...

but still thanks for that further hint, i will try to remember it.