Possible regression in ifconfig under7.0 - removes valid default route

I believe there "may be" a regression in the behaviour of ifconfig or
possibly just something I've never experienced before.

Basically when changing the IP of one of our machines, it suddenly
became inaccessible. After some investigation it turned out the machine
was inaccessible from anything other than the local VLAN and continued
diagnostics determined that the process of changing the IP had also
removed the default route.

This was clearly unexpected behaviour as the new IP was on the same
VLAN as the old IP and hence no routing table updates should be
required.

I don't have any older machines to test this on but I believe we have
done this procedure in the past without any such issues so wanted to
raise it here to see if anyone else has had experience with it.

Even if this isn't a regression it may well be something worth fixing
as its quite unexpected behaviour which could render a machine totally
inaccessible.

Regards
Steve

================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.

In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@xxxxxxxxxxxxxxxx

_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Possible regression in ifconfig under7.0 - removes valid default route
    ... This is a bug in my mind, but it's not a regression. ... I don't have any older machines to test this on but I believe we have ... In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. ... Net Consonance: consonant endings by net philanthropy, ...
    (freebsd-stable)
  • Re: UDP-U stream performance regression on 32-rc1 kernel
    ... performance regression from 10% to 20% on our Tulsa and some NHM ... time with the patch while it only consumes 0.5% cpu time without the ... hackbench on Nehalem and core2 machines. ... Pls. check /proc/cpuinfo to make sure cpu 0 and cpu 15 are not in the ...
    (Linux-Kernel)
  • Re: UDP-U stream performance regression on 32-rc1 kernel
    ... performance regression from 10% to 20% on our Tulsa and some NHM ... time with the patch while it only consumes 0.5% cpu time without the ... hackbench on Nehalem and core2 machines. ...
    (Linux-Kernel)
  • Re: [PATCH]PCI:disable resource decode in PCI BAR detection
    ... If, after a while, you think the change should go into the -stable tree, ... I think it shouldn't - this change will almost certainly cause a regression. ... disabled during BAR probe, like interrupt controllers, power management ... if it's going to cause a regression with machines that currently ...
    (Linux-Kernel)
  • Re: A9Home SharedCLibrary
    ... 26bit machines initially but there would be a whole host of things that ... can cause unexpected behaviour without legacy support. ... the 32bit soft SCL should only be used on 32bit machines. ...
    (comp.sys.acorn.misc)