Hello everyone,
I assigned a 00:00:00:00:00:00 MAC address to one of my interfaces on a machine
and tried to ping the peer machine. The ping did go through fine.
I can the see the request and reply packets on the packet capture. I am
wondering if that is legitimate and if not, who is supposed t
Hello everyone,
I tried to destroy a lagg interface (created using laggproto none) and I see
the system crash.
Steps to reproduce:
Kldload if_lagg
Ifconfig lagg0 create
ifconfig lagg0 up laggproto none laggport ql0 laggport ql1 192.168.100.1
netmask 255.255.255.0
ifconfig lagg0 destroy
uname -
side thought, can an incoming packet be classified as "invalid MAC
address" if it has the same MAC address of the host?
Thanks again
Adarsh
-Original Message-
From: Chuck Swiger [mailto:cswi...@mac.com]
Sent: Wednesday, March 14, 2012 3:57 PM
To: Adarsh Joshi
Cc: freebsd-net@f
Hello,
Is there a command or log message where I can find out the bus width and PCIe
version number on which my adapter is put on?
I did take a look at pciconf and devinfo and also the dmesg logs but could not
find anything.
I know it is visible on lspci on linux systems.
Thanks
Adarsh
:
3.3 V is provided
PME signal is supported
Bus Address: :01:00.0
Adarsh
-Original Message-
From: Chuck Swiger [mailto:cswi...@mac.com]
Sent: Tuesday, March 27, 2012 10:31 AM
To: Adarsh Joshi
Cc: freebsd-net@freebsd.org
Subject: Re: bus width and PCIe
Hi,
I am trying to configure lacp lagg interfaces with 2 systems connected back to
back as follows:
Ifconfig lagg0 create
Ifconfig lagg0 laggproto lacp laggport ql0 laggport ql1 192.168.100.1 netmask
255.255.255.0
Sometimes, the lag interface comes up correctly but sometimes the laggport
flag
not see a single packet on 1 of the
interface except for LACPDUs and other LACP control packets.
Thanks
Adarsh
-Original Message-
From: Jason Hellenthal [mailto:jhellent...@dataix.net]
Sent: Tuesday, July 10, 2012 12:10 AM
To: Adarsh Joshi
Cc: freebsd-net@freebsd.org
Subject: Re: lacp lagg
anks
Adarsh
From: Andrew Boyer [mailto:abo...@averesystems.com]
Sent: Tuesday, July 10, 2012 5:57 AM
To: Adarsh Joshi
Cc: freebsd-net@freebsd.org
Subject: Re: lacp lagg port flags do not show correctly resulting in poor
traffic distribution/performance
On Jul 9, 2012, at 8:38 PM, Adarsh Joshi w
2:38:30 bsd-15 kernel:
actor.state=3d
Jul 10 02:38:30 bsd-15 kernel: partner=(8000,00-0E-1E-08-05-20,01D3,8000,000C)
Jul 10 02:38:30 bsd-15 kernel:
partner.state=1d
Jul 10 02:38:30 bsd-15 kernel: maxdelay=0
Jul 10 02:38:33 bsd-15 kernel: lacp_transit_expire
^C
Let me know if you need more info.
Thanks
Adar
I tried to configure lagg with the latest source from SVN head and it did not
help.
Regards
Adarsh
-Original Message-
From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On
Behalf Of Adarsh Joshi
Sent: Tuesday, July 10, 2012 10:53 AM
To: Andrew Boyer
Cc: freebsd
Andrew,
Thanks for the response. Yes, the link is working fine. I am able to see
LACPDUs on tcpdump.
regards
Adarsh
From: Andrew Boyer [abo...@averesystems.com]
Sent: Friday, July 27, 2012 8:11 AM
To: Adarsh Joshi
Cc: freebsd-net@freebsd.org
Subject: Re
Hi,
Is there a way to check pending callouts?
I mean, like a command or utility, or do I have to panic the kernel and check
it at the debugger prompt?
regards
Adarsh
This message and any attached documents contain information from QLogic
Corporation or its who
12 matches
Mail list logo
