Hello, Freebsd-net.
Very large and famous (due to very attractive prices) hosting
provider Hetzner.de discards FreeBSD support on dedicated servers,
because these servers can niot negotiate 100Mbit/DUPLEX when
switches' ports are limited to 100Mbit (1Gbit connection costs
additional money) o
On Tue, 11 Jan 2011, Lev Serebryakov wrote:
Very large and famous (due to very attractive prices) hosting
provider Hetzner.de discards FreeBSD support on dedicated servers,
because these servers can niot negotiate 100Mbit/DUPLEX when
switches' ports are limited to 100Mbit (1Gbit connection cost
Hello, Yamagi.
You wrote 11 января 2011 г., 13:30:23:
> Hi,
> I've got several Hetzner EQ4 and on all these machines FreeBSD 8.1 runs
> just fine. I've never seen this strange negotiation problem myself. But
> maybe I was just lucky and got working mainboard and nic combinations.
> So if further i
On Tue, 11 Jan 2011, Yamagi Burmeister wrote:
Very large and famous (due to very attractive prices) hosting
provider Hetzner.de discards FreeBSD support on dedicated servers,
because these servers can niot negotiate 100Mbit/DUPLEX when
switches' ports are limited to 100Mbit (1Gbit connection co
On Tue, 11 Jan 2011, Bjoern A. Zeeb wrote:
I've got several Hetzner EQ4 and on all these machines FreeBSD 8.1 runs
just fine. I've never seen this strange negotiation problem myself. But
maybe I was just lucky and got working mainboard and nic combinations.
So if further information is needed, I
On Tue, Jan 11, 2011 at 12:47:29PM +0300, Lev Serebryakov wrote:
> Hello, Freebsd-net.
>
> Very large and famous (due to very attractive prices) hosting
> provider Hetzner.de discards FreeBSD support on dedicated servers,
> because these servers can niot negotiate 100Mbit/DUPLEX when
> switch
Hello, Brian.
You wrote 11 января 2011 г., 19:38:25:
>> Very large and famous (due to very attractive prices) hosting
>> provider Hetzner.de discards FreeBSD support on dedicated servers,
>> because these servers can niot negotiate 100Mbit/DUPLEX when
>> switches' ports are limited to 100Mbi
Hello, Brian.
You wrote 11 января 2011 г., 22:29:13:
> basic mode: 100 Mbit, full duplex
> link partner: 100baseTx-HD
It looks VERY strange. How could id be?
--
// Black Lion AKA Lev Serebryakov
___
freebsd-net@freebsd.org mailing list
http:/
11.01.2011 21:29, Lev Serebryakov пишет:
Hello, Brian.
You wrote 11 января 2011 г., 19:38:25:
Very large and famous (due to very attractive prices) hosting
provider Hetzner.de discards FreeBSD support on dedicated servers,
because these servers can niot negotiate 100Mbit/DUPLEX when
s
Hello, Marius.
You wrote 11 января 2011 г., 22:36:44:
>> I've discussed this problem in local (Russian-speaking) FreeBSD
>> community, and there are several people in DC 13 who HAVE these
>> problems and found different solutions, but all non-technical ones:
>> order gigabit connectivity, or pa
On Tue, 11 Jan 2011, Artyom Viklenko wrote:
11.01.2011 21:29, Lev Serebryakov ?:
r...@rescue ~ # mii-tool -v eth0
eth0: 100 Mbit, full duplex, link ok
product info: vendor 00:07:32, model 17 rev 2
basic mode: 100 Mbit, full duplex
basic status: link ok
capabilities: 1000baseT
Hello, Artyom.
You wrote 11 января 2011 г., 22:39:33:
>>link partner: 100baseTx-HD
> ^
> Looks very strange for me... 'HD' means half-duplex?
Yep, I've noticed that too...
> May be linux driver defaults to full-duplex if autoneg fails?..
Or disabled... And
11.01.2011 21:48, Bjoern A. Zeeb пишет:
On Tue, 11 Jan 2011, Artyom Viklenko wrote:
11.01.2011 21:29, Lev Serebryakov ?:
r...@rescue ~ # mii-tool -v eth0
eth0: 100 Mbit, full duplex, link ok
product info: vendor 00:07:32, model 17 rev 2
basic mode: 100 Mbit, full duplex
basic status: link
On Tue, Jan 11, 2011 at 09:39:33PM +0200, Artyom Viklenko wrote:
> 11.01.2011 21:29, Lev Serebryakov ?:
> Looks very strange for me... 'HD' means half-duplex?
>
> May be linux driver defaults to full-duplex if autoneg fails?..
I've seen some Linux drivers fail back to half-duplex under these
On Tue, Jan 11, 2011 at 12:47:29PM +0300, Lev Serebryakov wrote:
> Hello, Freebsd-net.
>
> Very large and famous (due to very attractive prices) hosting
> provider Hetzner.de discards FreeBSD support on dedicated servers,
> because these servers can niot negotiate 100Mbit/DUPLEX when
> switch
On Tue, 11 Jan 2011, Artyom Viklenko wrote:
11.01.2011 21:48, Bjoern A. Zeeb :
On Tue, 11 Jan 2011, Artyom Viklenko wrote:
11.01.2011 21:29, Lev Serebryakov ?:
r...@rescue ~ # mii-tool -v eth0
eth0: 100 Mbit, full duplex, link ok
product info: vendor 00:07:32, model 17 rev 2
basic mode:
On Tue, Jan 11, 2011 at 01:53:30PM +0300, Lev Serebryakov wrote:
> Hello, Yamagi.
> You wrote 11 ?? 2011 ?., 13:30:23:
>
> > Hi,
> > I've got several Hetzner EQ4 and on all these machines FreeBSD 8.1 runs
> > just fine. I've never seen this strange negotiation problem myself. But
> > maybe I w
Hello, Artyom.
You wrote 11 января 2011 г., 22:57:17:
> Is it possible to see status from corresponding port on Juniper switch?
> Config part for this port on the switch would be also very interesting.
I (as customer with server which has problem) could ask techsupport
tomorrow. But, maybe, they
Hello, Pyun.
You wrote 11 января 2011 г., 23:00:07:
> rgephy(4) currently always use auto-negotiation to work-around link
> establishment issues reported in past.
I think, it is the root of the problem. Autonegotiation is DISABLED on
these ports. I think, some additional mediaopt (like
force-hal
On Tue, Jan 11, 2011 at 10:50:49PM +0300, Lev Serebryakov wrote:
> Hello, Artyom.
> You wrote 11 ?? 2011 ?., 22:39:33:
>
> >>link partner: 100baseTx-HD
> > ^
> > Looks very strange for me... 'HD' means half-duplex?
> Yep, I've noticed that too...
>
> > Ma
On Tue, Jan 11, 2011 at 10:37:31PM +0300, Lev Serebryakov wrote:
> Hello, Brian.
> You wrote 11 ?? 2011 ?., 22:29:13:
>
> > basic mode: 100 Mbit, full duplex
> > link partner: 100baseTx-HD
> It looks VERY strange. How could id be?
This is normal if the link partner doesn't do autonego
On Wed, Jan 12, 2011 at 12:31:10AM +0300, Lev Serebryakov wrote:
> Hello, Pyun.
> You wrote 11 января 2011 г., 23:00:07:
>
> > rgephy(4) currently always use auto-negotiation to work-around link
> > establishment issues reported in past.
> I think, it is the root of the problem. Autonegotiation
> > May be linux driver defaults to full-duplex if autoneg fails?..
>
> I've seen some Linux drivers fail back to half-duplex under these
> circumstances.
>
> It may very well depend on driver version and hardware (firmware)?
>
> I admit, I don't know what layer is responsible for handling
> aut
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
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 (100baseTX )
I can see what's going on here. Link partner used forced media
configuration, probably 100baseTX/full-duplex, and re(4)'s
resolved link is 100b
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
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 (100baseTX )
> >
> >I can see what's going on here. Link partner used forced media
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-
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
32 matches
Mail list logo
