Hello, Bernd.
You wrote 12 января 2011 г., 1:03:14:
I'm not surprised that it doesn't work with autonegotian if autonegotian
is disabled.
If Linux does full-duplex without autonegotiation then _they_ do it wrong
and Hetzner shouldn't rely on wrong behavour.
As far as I understand, Linux
Hello, Pyun.
You wrote 12 января 2011 г., 1:45:26:
That had been supported for long time. Just remove full-duplex
media option in your manual configuration.
What do you mean by this? Without this media options it will be
100Mbit half-duplex when switch port want 100Mbit full-duplex. With
I'm not surprised that it doesn't work with autonegotian if autonegotian
is disabled.
If Linux does full-duplex without autonegotiation then _they_ do it wrong
and Hetzner shouldn't rely on wrong behavour.
As far as I understand, Linux does full-duplex without
autonegotiation because
Hello, Sthaug.
You wrote 12 января 2011 г., 12:14:14:
Manual configuration of FD for 100 Mbps is not in violation of the
standards. What the standards say (for 100 Mbps) is that *if* you have
one end configured for autonegotiation *and* the other end is manually
configured for full duplex,
On Tue, 11 Jan 2011, Pyun YongHyeon wrote:
On Tue, Jan 11, 2011 at 12:47:29PM +0300, Lev Serebryakov wrote:
media: Ethernet 100baseTX full-duplex (100baseTX half-duplex)
I can see what's going on here. Link partner used forced media
configuration, probably 100baseTX/full-duplex, and
Hi,
I am thinking about writing a wireless driver that simulates a wifi
device (a very simple one). I am interested in only testing 11s mesh.
After reading man page for NET80211
http://www.unix.com/man-page/freebsd/9/NET80211/
I see that there are only 5 functions in struct ieee80211com that
Hello, Freebsd-net.
Thanks to Pyun YongHyeon, who point me at fact, that rgephy(4) used
with re(4) does autonegotiation always and all other, who helps me
diagnose problem!
I've prepared patch, which adds tunable/sysctl for rgephy(4) which
allows not to sue autonegotiation by this PHY (at
On Wed, Jan 12, 2011 at 12:03:03PM +0300, Lev Serebryakov wrote:
Hello, Pyun.
You wrote 12 января 2011 г., 1:45:26:
That had been supported for long time. Just remove full-duplex
media option in your manual configuration.
What do you mean by this? Without this media options it will be
On Wed, Jan 12, 2011 at 10:36:09AM +, Bjoern A. Zeeb wrote:
On Tue, 11 Jan 2011, Pyun YongHyeon wrote:
On Tue, Jan 11, 2011 at 12:47:29PM +0300, Lev Serebryakov wrote:
media: Ethernet 100baseTX full-duplex (100baseTX half-duplex)
I can see what's going on here. Link partner used
Hello, Pyun.
You wrote 12 января 2011 г., 20:32:42:
That had been supported for long time. Just remove full-duplex
media option in your manual configuration.
What do you mean by this? Without this media options it will be
100Mbit half-duplex when switch port want 100Mbit full-duplex.
On Wed, Jan 12, 2011 at 08:56:19PM +0300, Lev Serebryakov wrote:
Hello, Pyun.
You wrote 12 января 2011 г., 20:32:42:
That had been supported for long time. Just remove full-duplex
media option in your manual configuration.
What do you mean by this? Without this media options it
Submitter-Id: current-users
Originator:Juergen Lock
Organization: me? organized??
Confidential: no
Synopsis: [run] [panic] [patch] Workaround for use-after-free panic
Severity:
Priority:
Category: kern
Class: sw-bug
Release: FreeBSD 8.1-RC2 amd64
2011/1/12 Lev Serebryakov l...@serebryakov.spb.ru:
Hello, Freebsd-net.
Thanks to Pyun YongHyeon, who point me at fact, that rgephy(4) used
with re(4) does autonegotiation always and all other, who helps me
diagnose problem!
I've prepared patch, which adds tunable/sysctl for rgephy(4)
On Wed, Jan 12, 2011 at 07:20:09PM +0300, Lev Serebryakov wrote:
Hello, Freebsd-net.
Thanks to Pyun YongHyeon, who point me at fact, that rgephy(4) used
with re(4) does autonegotiation always and all other, who helps me
diagnose problem!
I've prepared patch, which adds tunable/sysctl
On Wed, Jan 12, 2011 at 12:59:58PM -0800, Artem Belevich wrote:
2011/1/12 Lev Serebryakov l...@serebryakov.spb.ru:
Hello, Freebsd-net.
?Thanks to Pyun YongHyeon, who point me at fact, that rgephy(4) used
with re(4) does autonegotiation always and all other, who helps me
diagnose
On Wed, Jan 12, 2011 at 01:32:08PM -0800, Pyun YongHyeon wrote:
On Wed, Jan 12, 2011 at 07:20:09PM +0300, Lev Serebryakov wrote:
Hello, Freebsd-net.
Thanks to Pyun YongHyeon, who point me at fact, that rgephy(4) used
with re(4) does autonegotiation always and all other, who helps me
I'd like to report that we're running into this issue also, in our case
on systems that are based on the Intel S5520UR Server Board, running
8.1-RELEASE. If the ichwd driver is loaded we see the same messages,
and network communication via the igb nics is non-functional.
Have you had any
Hello guys,
I have used Proxim 8470 LAN cards. But I realized that this card is too old
to use TDMA on FreeBSD. I need new wireless LAN cards which are supported by
TDMA on FreeBSD and with an external port to connect directional antenna. Do
you recommend any cards? Actually, it is hard to find
The problem that Robin saw was due to having MSIX interrupts disabled on the
system, I doubt that
is going to be the issue for others.
Get the latest version of the igb code and see if that helps you as a first
step.
Jack
On Wed, Jan 12, 2011 at 6:43 PM, Charles Owens
Find out what the address is that's causing the problem. There's
plenty of places where unaligned mbuf's exist in the IP code and
aren't correctly realigned before being touched.
MIPS people - is address error an alignment problem?
Adrian
On 30 December 2010 21:47, Monthadar Al Jaberi
On Thu, Jan 13, 2011 at 11:08 AM, Adrian Chadd adr...@freebsd.org wrote:
Find out what the address is that's causing the problem. There's
plenty of places where unaligned mbuf's exist in the IP code and
aren't correctly realigned before being touched.
MIPS people - is address error an
I've encountered this before.
The mbuf's there aren't always aligned at this point.
Adrian
On 13 January 2011 14:17, Jayachandran C. c.jayachand...@gmail.com wrote:
On Thu, Jan 13, 2011 at 11:08 AM, Adrian Chadd adr...@freebsd.org wrote:
Find out what the address is that's causing the
On Thursday, January 13, 2011 04:44:03 Kyungsoo Lee wrote:
Hello guys,
I have used Proxim 8470 LAN cards. But I realized that this card is too old
to use TDMA on FreeBSD. I need new wireless LAN cards which are supported
by TDMA on FreeBSD and with an external port to connect directional
23 matches
Mail list logo
