Very Interesting.
On the switch I can set the port flow-control to on, off or
desirable. The following is the blurb on those configuration options:
Gigabit Ethernet Flow Control Keyword Functions, Keywords : Function
receive on: The port uses flow control dictated by the neighbor port.
receive desired: The port uses flow control if the neighbor port uses
it, and does not use flow control if the neighbor port does not use it.
receive off: The port does not use flow control, regardless of
whether flow control is requested by the neighbor port.
send on: The port sends flow-control frames to the neighbor port.
send desired: The port sends flow-control frames to the neighbor port
if the neighbor port asks to use flow control.
send off: The port does not send flow-control frames to the neighbor
port.
However, irrespective of what I configure the port flow-control to on
the switch (and then reboot the OpenBSD host, to be sure of correct
interface initialisation) I cannot be ifconfig to report {tx|rx}pause.
Is this likely to be a driver problem, or is there some broken flash
code on the bge NIC (which I could possible update) ?
/Pete
On 14. feb. 2007, at 22.42, Mark Kettenis wrote:
From: Pete Vickers <[EMAIL PROTECTED]>
Date: Wed, 14 Feb 2007 13:33:25 +0100
# ifconfig bge0
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:17:a4:45:f5:25
groups: egress
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet6 fe80::217:a4ff:fe45:f525%bge0 prefixlen 64 scopeid 0x1
inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x
This suggests flow control has *not* been negotiated. With msk(4), I
get:
borodin$ ifconfig msk0
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:16:cb:a2:87:67
groups: egress
media: Ethernet autoselect (1000baseT full-
duplex,rxpause,txpause)
status: active
inet6 fe80::216:cbff:fea2:8767%msk0 prefixlen 64 scopeid 0x1
inet 192.168.0.17 netmask 0xffffff00 broadcast 192.168.0.255
