Running a 3c509C in a non-routable address space being set up in rc.conf as follows: ifconfig_xl1="inet 192.168.0.254 netmask 0xfffff00" This setup defaults to a broadcast address of 240.168.0.255 which I believe is bogus - it should be 192.168.0.255 - this seems to confuse programs like 'samba' that need broadcasting to work correctly. Fix: Use the following line in rc.conf: ifconfig_xl1="inet 192.168.0.254 netmask 0xfffff00 broadcast 192.168.0.255"
Responsible Changed From-To: freebsd-bugs->wpaul Over to the NIC guru
Tim Daneliuk <tundra@tundraware.com> wrote: >>Description: >Running a 3c509C in a non-routable address space being set up in >rc.conf as follows: > >ifconfig_xl1="inet 192.168.0.254 netmask 0xfffff00" ^^^^^^^^^ I believe that this should be 0xffffff00. (Note: 8 characters after the '0x') With the input you have given (which is bogus), the results seem to be appropriate (though probably not meaningful). Please try correcting this and report back on the results. -Tony.
State Changed From-To: open->closed I too hastily assigned this PR. The originator has a typo, the netmask should be 0xffffff00, or more easily understood by humans, 255.255.255.0.
Responsible Changed From-To: wpaul->dougb I erred in A) not reading the PR more carefully, and B) bothering wpaul with it. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27862
Tony Fleisher wrote: > > Tim Daneliuk <tundra@tundraware.com> wrote: > >>Description: > >Running a 3c509C in a non-routable address space being set up in > >rc.conf as follows: > > > >ifconfig_xl1="inet 192.168.0.254 netmask 0xfffff00" > ^^^^^^^^^ > I believe that this should be 0xffffff00. > (Note: 8 characters after the '0x') > With the input you have given (which is bogus), > the results seem to be appropriate (though probably not meaningful). > > Please try correcting this and report back on the results. > > -Tony. Many apologies (I am such a moron) ... old age and long hours are my only excuse. The correct mask, does, of course work properly. <Slinking off in embarassment...> -- ------------------------------------------------------------------------------ Tim Daneliuk tundra@tundraware.com