Re: 8.1-RELEASE em watchdog timeout broken?

> "whenever my desktop PC" > > Now this is where u FAIL. Use dubuntu or windows7 on desktop not FBSD > and don't try again. > > Jax Perhaps I wasn't clear. The desktop PC (which runs WinXP) is connected directly to the em0 port on my FreeBSD server. No Ethernet switch in-between. I connect it

Re: 8.1-RELEASE em watchdog timeout broken?

The watchdog is working in all the internal testing that we've done, if there's some corner case here then I need more info to reproduce it. I'm confused about what's what, which machine is your desktop and what is the 'other' system? For instance, we had a loud complaint about the watchdog here a

Re: 8.1-RELEASE em watchdog timeout broken?

"whenever my desktop PC" Now this is where u FAIL. Use dubuntu or windows7 on desktop not FBSD and don't try again. Jax On Wed, Aug 4, 2010 at 4:02 AM, Scott Johnson wrote: > Under 8.0-RELEASE I would get warnings from em(4) in /var/log/messages about > > "watchdog timeouts" on em0 whenever m

8.1-RELEASE em watchdog timeout broken?

Under 8.0-RELEASE I would get warnings from em(4) in /var/log/messages about "watchdog timeouts" on em0 whenever my desktop PC connected to em0 was powered off. This was fine, except for the annoying warnings. Under 8.1-RELEASE I no longer get the warnings, and any time my desktop is powered o

Re: CARP over LAGG

Hello, This should be possible. I do have 7.2 systems which have lagg0 on em0/em1 VLANs over lagg0 and carp over those VLANs. So I guess carp over lagg0 should no be a problem. lagg0: flags=8943 metric 0 mtu 1500 options=19b ether 00:30:48:c8:2f:50 media: Ethernet autos

Re: vlan(4) interfaces have wrong interface type in sockaddr_dl address

On Tue, Aug 03, 2010 at 12:17:27PM -0400, John Baldwin wrote: > On Tuesday, August 03, 2010 10:29:11 am John Baldwin wrote: > > Currently vlan(4) interfaces have an interface type of IFT_ETHER instead of > > IFT_L2VLAN in the sockaddr_dl that is returned by getifaddrs(3). If you do > > a > > ro

Re: vlan(4) interfaces have wrong interface type in sockaddr_dl address

On Tuesday, August 03, 2010 10:29:11 am John Baldwin wrote: > Currently vlan(4) interfaces have an interface type of IFT_ETHER instead of > IFT_L2VLAN in the sockaddr_dl that is returned by getifaddrs(3). If you do a > route lookup for a route that goes across a vlan then the sockaddr_dl > gene

CARP over LAGG

Hello. On a couple of 7.2 systems, I've got some carp interfaces build upon a physical interface (em0 or igb0) and everything works fine. On both box I've tried aggregating two interfaces (resp. em0+em1 and igb0+igb1) into a lagg0 interface, using LACP. However, in this case CARP will stop wo

vlan(4) interfaces have wrong interface type in sockaddr_dl address

Currently vlan(4) interfaces have an interface type of IFT_ETHER instead of IFT_L2VLAN in the sockaddr_dl that is returned by getifaddrs(3). If you do a route lookup for a route that goes across a vlan then the sockaddr_dl generated for the routing message will specify IFT_L2VLAN (you can see i

freebsd-net@freebsd.org

Hi all, (apologies for any duplicates you receive and please trim the CC list appropriately if you reply to this email) We're pleased to announce the release of a substantial set of new and updated BSD licenced software for TCP experimentation and research using FreeBSD: - "CAIA-Hamilton Delay"