Broadcast 0.0.0.0 ?

diederick76 · 2011-06-19 09:20:31

Hi,

After getting a deprecation warning about the way I configured networking in my rc.conf, I changed part of that file to this:

interface=eth0
address=192.168.1.101
netmask=255.255.255.0
gateway=192.168.1.1

#eth0="eth0 192.168.1.101 netmask 255.255.255.0 broadcast 192.168.1.255"
#INTERFACES=(eth0)
#gateway="default gw 192.168.1.1"
#ROUTES=(gateway)

I have commented out my deprecated setup. When I restart /etc/rc.d/network and do ifconfig, the output start with this:

eth0      Link encap:Ethernet  HWaddr 48:5B:39:42:FF:77  
          inet addr:192.168.1.101  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::4a5b:39ff:fe42:ff77/64 Scope:Link

As you can see, there is something wrong with the Broadcast address. In the old way, there was a way to specify the broadcast address. I don't know how to do that with the new way. Is there a way to do this, or am I doing something else wrong?

Thanks for any help on this.

falconindy · 2011-06-19 12:54:37

Its not always needed, but you'll be able to configure broadcast in the next release of initscripts.

http://projects.archlinux.org/initscrip … c2e7c378c9

George.Harmony · 2011-06-19 15:15:30

Well that really bites cause it looks like I am one of the people who needs this. Guess I'll stay with the old method until this is fixed

falconindy · 2011-06-19 15:27:54

Or apply the patch...

diederick76 · 2011-06-19 19:43:58

falconindy wrote:

Its not always needed, but you'll be able to configure broadcast in the next release of initscripts.
http://projects.archlinux.org/initscrip … c2e7c378c9

If the new tool cannot fully replace the old one yet, why deprecate the old one? It worked perfectly afaik. A warning would have been nice before I made the switch.

George.Harmony · 2011-06-19 19:58:32

diederick76 wrote:

falconindy wrote:
Its not always needed, but you'll be able to configure broadcast in the next release of initscripts.
http://projects.archlinux.org/initscrip … c2e7c378c9
If the new tool cannot fully replace the old one yet, why deprecate the old one? It worked perfectly afaik. A warning would have been nice before I made the switch.

I concur. As I missed this post before posting my question regarding this issue I won't say their wasn't one but I definitely looked around before making the change in my systems to this new method.

I would be happy to change to netcfg if it didn't have dependencies of wpa_supplicant and wireless tools. Either way I swtiched back to the old way and will wait for the updated scripts.

@falconindy: Thanks for the suggestion but I'm lazy and don't want to apply the patch. I'll just wait and put up with my mpd server being a little slow to respond to ssh's. Everything else seems to work fine on my desktop with the old version. My mpd server was installed after the change so it is the only system I can't regress on without installing some of the old tools.

falconindy · 2011-06-19 20:26:38

diederick76 wrote:

falconindy wrote:
Its not always needed, but you'll be able to configure broadcast in the next release of initscripts.
http://projects.archlinux.org/initscrip … c2e7c378c9
If the new tool cannot fully replace the old one yet, why deprecate the old one? It worked perfectly afaik. A warning would have been nice before I made the switch.

That's why its deprecated, and not removed. Not to mention that the "replacement" is netcfg.

Arch Linux

#1 2011-06-19 09:20:31

Broadcast 0.0.0.0 ?

#2 2011-06-19 12:54:37

Re: Broadcast 0.0.0.0 ?

#3 2011-06-19 15:15:30

Re: Broadcast 0.0.0.0 ?

#4 2011-06-19 15:27:54

Re: Broadcast 0.0.0.0 ?

#5 2011-06-19 19:43:58

Re: Broadcast 0.0.0.0 ?

#6 2011-06-19 19:58:32

Re: Broadcast 0.0.0.0 ?

#7 2011-06-19 20:26:38

Re: Broadcast 0.0.0.0 ?

Board footer