Re: PPP and Route Delete

2011-01-11 Thread Luiz Otavio O Souza
On Jan 10, 2011, at 2:25 PM, Melissa Jenkins wrote: I've been working on migrating a PPTP server from FreeBSD 7.1 to FreeBSD 8.1. The server is configured using PopTop (from ports) and PPP (/usr/sbin) rather than MPD. (Before anybody tells me to use MPD we can't because it doesn't

Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Lev Serebryakov
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)

Re: PPP and Route Delete

2011-01-11 Thread Melissa Jenkins
On 11 Jan 2011, at 09:13, Luiz Otavio O Souza wrote: On Jan 10, 2011, at 2:25 PM, Melissa Jenkins wrote: I've been working on migrating a PPTP server from FreeBSD 7.1 to FreeBSD 8.1. The server is configured using PopTop (from ports) and PPP (/usr/sbin) rather than MPD. (Before anybody

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Yamagi Burmeister
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

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Lev Serebryakov
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

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Bjoern A. Zeeb
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

Re: em driver, 82574L chip, and possibly ASPM

2011-01-11 Thread Mike Tancsa
On 12/24/2010 5:44 PM, Jan Koum wrote: hi Ivan and Mike, wanted to follow up and see if you found a solid long-term solution to this bug. we are still seeing this problem in our 8.2 environment with ASPM already disabled. here is what we have: 1. motherboard is SuperMicro X8SIE-LN4F

Re: em driver, 82574L chip, and possibly ASPM

2011-01-11 Thread Ivan Voras
On 11/01/2011 15:04, Mike Tancsa wrote: On 12/24/2010 5:44 PM, Jan Koum wrote: hi Ivan and Mike, wanted to follow up and see if you found a solid long-term solution to this bug. we are still seeing this problem in our 8.2 environment with ASPM already disabled. here is what we have: 1.

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Yamagi Burmeister
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,

RE: PPP and Route Delete

2011-01-11 Thread Li, Qing
The self-pointing route 10.0.5.1 should have multiple references set on it, and that route won't be deleted from the routing table until the last reference is removed. You can verify that by checking the netstat output, the Ref column after tun1 has been created. The above has been verified

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Brian Reichert
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 switches'

Re: PPP and Route Delete

2011-01-11 Thread Melissa Jenkins
The self-pointing route 10.0.5.1 should have multiple references set on it, and that route won't be deleted from the routing table until the last reference is removed. You can verify that by checking the netstat output, the Ref column after tun1 has been created. The above has been

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread 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 switches' ports are limited to 100Mbit

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Lev Serebryakov
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 l...@serebryakov.spb.ru ___

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Artyom Viklenko
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

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Lev Serebryakov
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 pay for

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread 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 ok capabilities:

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Lev Serebryakov
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 it

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Artyom Viklenko
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:

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Brian Reichert
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

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Pyun YongHyeon
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 switches'

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Bjoern A. Zeeb
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

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Marius Strobl
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 was just

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Lev Serebryakov
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

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Lev Serebryakov
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

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Bernd Walter
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... May be linux

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Bernd Walter
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

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread Pyun YongHyeon
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 is

IPFW firewall NAT and active FTP

2011-01-11 Thread Brett Glass
I'm working with a customer who has a FreeBSD 8.0 firewall, set up with firewall NAT in IPFW. It uses one-to-one static NAT to redirect FTP sessions originating on the outside to an FTP server on the inside. The FTP server is accessible via text-based FTP clients, but not via Web-based clients

Re: Supermicro Bladeserver

2011-01-11 Thread Steven Hartland
Out of interest what change was that? - Original Message - From: Vogel, Jack jack.vo...@intel.com To: TAKAHASHI Yoshihiro n...@freebsd.org; jfvo...@gmail.com Cc: freebsd-net@freebsd.org; freebsd-sta...@freebsd.org Sent: Monday, January 10, 2011 9:17 PM Subject: RE: Supermicro

Re: Supermicro Bladeserver

2011-01-11 Thread Robin Sommer
On Wed, Jan 12, 2011 at 03:13 -, you wrote: Out of interest what change was that? As what seems to have been a left-over from a debugging session a long time ago, I had MSI disabled in loader.conf. That's not supported by the driver. So simply reenabling that solved my problem. Robin --

Re: IPFW firewall NAT and active FTP

2011-01-11 Thread Artyom Viklenko
12.01.2011 01:06, Brett Glass пишет: I'm working with a customer who has a FreeBSD 8.0 firewall, set up with firewall NAT in IPFW. It uses one-to-one static NAT to redirect FTP sessions originating on the outside to an FTP server on the inside. The FTP server is accessible via text-based FTP

Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug)

2011-01-11 Thread sthaug
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