> 
> > I think the patch from the arp SA has broken routing for a few people.
> > 
> >          ---Mike
> 
> Any suggestions?  This is my backup server.  I would like to resolve this
> as soon as possible.  I don't want to have to re-install to 4.8-RELEASE.
> 
> The machine was running 4.8-RELEASE-p3 fine last week (and not 4.8-RELEASE
> as I indicated below).  Is it possible to blow away /usr/src and cvsup to
> 4.8-RELEASE-p3 rather than 4.8-RELEASE-p8?
> 

Ok.  I grabbed src/sys/netinet/if_ether.c from a 4.8-RELEASE-p7 box,
rebuilt and installed the kernel, and rebooted and it looks ok so far.
*phew*

 - Michael Hogsett

> 
> > At 02:11 PM 24/09/2003, Mike Hogsett wrote:
> > 
> > >I have a machine that has been running 4.8-RELEASE for months flawlessly.
> > >I recently CVSup'd to RELENG_4_8 (now running 4.8-RELEASE-p8).
> >
> > >The machine is losing routes.  Specifically its default route and a route
> > >to the lan of one of its own interfaces.  I can manually add the default
> > >route back, but it only lasts about 20 seconds until it mysteriously
> > >disappears.
> > >
> > >The machine has an Intel 1000baseSX card that is sub-interfaced using
> > >VLANs.  There are 9 vlan interfaces in use (vlan0 through vlan8).
> > >
> > >It consistently loses its default route and the route to the lan
> > >`connected' to vlan8.
> > >
> > >Any suggestions how I can diagnose what is happening?
> > >
> > >Thanks!
> > >
> > >  - Michael Hogsett
> > >_______________________________________________
> > >[EMAIL PROTECTED] mailing list
> > >http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > >To unsubscribe, send any mail to "[EMAIL PROTECTED]
> g"
> _______________________________________________
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to