Re: tap(4) and host-only networking between host and guest

Hi Victor, On Wed, Nov 4, 2015 at 10:45 AM, Victor Sudakov wrote: > Victor Sudakov wrote: >> Julian Elischer wrote: >> > > >> > > I am experimenting with bhyve which uses tap(4) for network access. >> > > >> > > I don't want to bridge tap0 with any of the hosts's real NICs. How can >> > > I creat

[Differential] [Changed Subscribers] D1711: Changes to the callout code to restore active semantics and also add a test-framework and test to validate thecallout code (and potentially for use by other

neel added a subscriber: neel. REVISION DETAIL https://reviews.freebsd.org/D1711 To: rrs, gnn, rwatson, imp, hselasky, adrian, sbruno, lstewart Cc: neel, erj, freebsd-net ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listin

Re: e1000 serdes link flap

So, I will soon do some updates to the e1000 > drivers anyway > and as part of that I will sync the shared code base with the latest, this > should address > the issue... OK? Sounds good. best Neel > > Cheers, > > Jack > > > > On Mon, Jan 28, 2013 at 8:14 P

Re: e1000 serdes link flap

Hi Jack, On Wed, Jan 23, 2013 at 2:58 PM, Ryan Stone wrote: > On Wed, Jan 23, 2013 at 2:13 AM, Neel Natu wrote: >> >> Hi, >> >> I am running into a problem in head with the e1000 link state >> detection logic attached to a 82571EB serdes controller. >>

e1000 serdes link flap

Hi, I am running into a problem in head with the e1000 link state detection logic attached to a 82571EB serdes controller. The symptom is that the link state keeps flapping between "up" and "down". After I enabled the debug output in 'e1000_check_for_serdes_link_82571()' this is what I see: e10