Nope, doesn't help ... I've been doing this for years now, and its all
scripted, to make sure that I don't make a mistake like that ... its a
reproducible issue with 4.x and the EM drivers ... or, rather, the
4-STABLE ones ... in fact, I have three servers with em devices, one of
them I *haven't* upgraded to the latest, since I knew if I did, the
problem itself would creep onto that machine ... the other two are running
reasonably "new" (for 4.x, of course) -STABLE kernels, and both exhibit
the problem ...
I'm not overly concerned, it just takes 30-60 minutes for everything to
usually time out and become visible on the 'Net again ... and, starting in
April, we're going to be upgrading our servers to 6.x ... just figured I'd
make sure there wasn't some command I was overlooking that I could give it
a kick with, until then ...
Thx though ...
On Sat, 25 Mar 2006, Grant Peel wrote:
Hi Marc,
I don't pretend to know anything about Address Resolution and Routing, but
one thing I know (through many hours of frustration), is that an aliased
address (in your case, somehting like em0:23), IF the ip address being
aliases, belongs in the same subnet as anotherone on the same machine, the
second one must use a 255 subnet ( /0 ?).
example:
em0 192.168.0.1 255.255.255.0
em0_0 192.168.0.2 255.255.255.255
...
em0_23 10.10.10.10 255.255.255.192
em0_43 10.10.10.11 255.255.255.255
em0_59 10.10.10.15 255.255.255.255
Hope this helps, if not soory about the waste of time!
-Grant
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
