New network stack fails to route broadcast packets, breaking DHCP

[anevilyak]

When attempting to start the DHCP server after the recent routing change, the DHCP packets fail to send with "No route to host" returned...syslog with route tracing enabled as follows:

KERN: bfs: bfs_open_dir:1483: Invalid Argument KERN: 3com: init_hardware(0x94832918) KERN: 3com: no hardware found. KERN: etherpci: init_driver init_driver: etherpci not found KERN: ipro100: init_hardware(0x9482fee4) KERN: ipro100: no hardware found. KERN: ipro1000: init_hardware(0x9484e784) KERN: ipro1000: no hardware found. KERN: marvell_yukon: init_hardware(0x94835c1c) KERN: marvell_yukon: no hardware found. KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/net/net_stack KERN: nforce: init_hardware(0x94835c98) KERN: nforce, found NVIDIA nForce4 CK804 MCP9 Networking Adapter at 13 KERN: nforce: init_driver(0x94835c98) KERN: [nforce] (nfe) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1, 0x2) KERN: [nforce] (nfe) bus_alloc_resource(1, [0], 0x0, 0xffffffff, 0x1, 0x6) KERN: if_initname(0x90ec5c00, nfe, 3) KERN: [nforce] nforce: /dev/net/nforce/0 KERN: [nforce] () Found MII: ukphy KERN: [nforce] () OUI 0x005043, model 0x000c, rev. 2 KERN: [nforce] () Adding entry for Ethernet none KERN: Adding entry for Ethernet 10baseT/UTP KERN: 10baseTAdding entry for Ethernet 10baseT/UTP <full-duplex> KERN: , 10baseT-FDXAdding entry for Ethernet 100baseTX KERN: , 100baseTXAdding entry for Ethernet 100baseTX <full-duplex> KERN: , 100baseTX-FDXAdding entry for Ethernet 1000baseTX KERN: , 1000baseTAdding entry for Ethernet 1000baseTX <full-duplex> KERN: , 1000baseT-FDXAdding entry for Ethernet autoselect KERN: , auto KERN: ifmedia_set: target EthernetKERN: autoselect KERN: ifmedia_set: setting to Ethernet autoselect KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/net/nforce KERN: rtl8139: init_hardware(0x94dcaec0) KERN: rtl8139: no hardware found. KERN: via_rhine: init_hardware(0x94dcb218) KERN: via_rhine: no hardware found. KERN: register_domain(1, internet) KERN: unregister_domain(0x90f17940, 1, internet) KERN: register_domain(1, internet) KERN: get_device_interface: ask "network/devices/ethernet/v1" for loop KERN: get_device_interface: ask "network/devices/loopback/v1" for loop KERN: remove route from domain internet: dest 204.204.204.204, mask <none>, gw <none>, flags 200004 KERN: add route to domain internet: dest 127.0.0.1, mask 255.0.0.0, gw <none>, flags 0 KERN: add route to domain internet: dest 127.0.0.1, mask <none>, gw <none>, flags 200004 KERN: bfs: bfs_open_dir:1483: Invalid Argument KERN: get_device_interface: ask "network/devices/ethernet/v1" for /dev/net/nforce/0 KERN: ipv4_datalink_init(/dev/net/nforce/0) KERN: add route to domain internet: dest <none>, mask <none>, gw <none>, flags 880 KERN: [net/nforce/0] compat_open(0x2) KERN: ifmedia_ioctl: switching nfe to Ethernet autoselect KERN: /dev/net/nforce/0: media change, media 0x22 quality 1000 speed 10000 KERN: register_domain(4, link) KERN: test address 255.255.255.255 for routes... KERN: remove route from domain internet: dest 204.204.204.204, mask <none>, gw <none>, flags 200004 KERN: add route to domain internet: dest 169.254.0.92, mask 255.255.0.0, gw <none>, flags 0 KERN: add route to domain internet: dest 169.254.0.92, mask <none>, gw <none>, flags 200004

[axeld]

Can you add the output of "ifconfig", too?

[axeld]

Never mind, I could reproduce this on real hardware as well with the ipro1000 driver; the driver reported no link early, and found the link too late for DHCP (it worked fine in VMware, though). Fixed in hrev24459.