Hi all,
This review could be the solution to my problem?
http://svnweb.freebsd.org/base?view=revision&revision=273736
Best regards,
On 01/12/2014 19:29, Pieper, Jeffrey E wrote:
Hi Marcelo,
A couple of questions - you are using 1310nm fiber on ix0, correct? The
difference seems to be that i
Hello,
I'm running FreeBSD 9.3-RELEASE up-to-date, on two HP Proliant G6 server blades
in the same enclosure. One with VLANs in the uplink, the other without VLANs.
They use bxe driver.
bxe0: mem 0xfb00-0xfb7f,0xfa80-0xfaff irq 28 at device 0.0
on pci2
bxe0: PC
Have you tried disabling all the various flags VLAN flags on the NIC?
On 03/12/2014 15:46, Patrick Proniewski wrote:
Hello,
I'm running FreeBSD 9.3-RELEASE up-to-date, on two HP Proliant G6 server blades
in the same enclosure. One with VLANs in the uplink, the other without VLANs.
They use bx
I did and it failed, but maybe I've not used the right syntax:
# ifconfig bxe0 -vlanmtu
ifconfig: -vlanmtu: Invalid argument
man bxe makes me think that this driver won't allow this kind of changes.
On 3 déc. 2014, at 16:59, Steven Hartland wrote:
> Have you tried disabling al
On Dec 3, 2014, at 5:05 PM, Patrick Proniewski wrote:
> I did and it failed, but maybe I've not used the right syntax:
>
> # ifconfig bxe0 -vlanmtu
> ifconfig: -vlanmtu: Invalid argument
>
> man bxe makes me think that this driver won't allow this kind of changes.
Although there's
On 3 déc. 2014, at 17:09, Borja Marcos wrote:
> On Dec 3, 2014, at 5:05 PM, Patrick Proniewski wrote:
>
>> I did and it failed, but maybe I've not used the right syntax:
>>
>> # ifconfig bxe0 -vlanmtu
>> ifconfig: -vlanmtu: Invalid argument
>>
>> man bxe makes me think that this driv
On Dec 3, 2014, at 5:21 PM, Patrick Proniewski wrote:
> On 3 déc. 2014, at 17:09, Borja Marcos wrote:
>
>> On Dec 3, 2014, at 5:05 PM, Patrick Proniewski wrote:
>>
>>> I did and it failed, but maybe I've not used the right syntax:
>>>
>>> # ifconfig bxe0 -vlanmtu
>>> ifconfig: -vlanmt
hi,
try dropping the MSS of the connection down.
I wonder if you're hitting some frame size cap when transmitting -
adding a VLAN header adds a few bytes to the size of the frame. If the
NIC is enforcing some maximum frame transmit size then it may be
failing to transmit things.
-adrian
On 3
Looks like bxe does support setting vlanhwtso so might want to try
disabling that one just in case.
On 03/12/2014 16:05, Patrick Proniewski wrote:
I did and it failed, but maybe I've not used the right syntax:
# ifconfig bxe0 -vlanmtu
ifconfig: -vlanmtu: Invalid argument
man b
On Wed, 3 Dec 2014, Martin Hanson wrote:
I got a small Intel Atom N280 box I wanted to use as a PF firewall.
It has one Intel NIC that gets registered as "bge0",
That would be Broadcom.
then it has three
USB->NIC dongles with the ASIX AX88179 chipset which gets registered
as "ue0", "ue1" an
Hi
I got a small Intel Atom N280 box I wanted to use as a PF firewall.
It has one Intel NIC that gets registered as "bge0", then it has three
USB->NIC dongles with the ASIX AX88179 chipset which gets registered
as "ue0", "ue1" and "ue2".
I have set each device to a static IP during boot.
The pr
On 03 déc. 2014, at 17:25, Borja Marcos wrote:
> I forgot, sorry. Sometimes you need to set the interface to down and up again
> to make sure changes to flags such as LRO and TSO have been applied :/
>
> TSO can be disabled in a global way using a sysctl variable: net.inet.tcp.tso
what is the p
Hey Net -
In probably a poor, cheap choice, I picked up a TP-Link TL-SG2008 Desktop Smart
Switch, which supports LACP/802.3ad. I’m currently running 10.1-STABLE r274577
on the machine I’m testing with. I’m testing right now with just 1 port (two
ports didn’t work either.).
Hardware is Super
>> This is a major problem as the device *still* has the right name and the
>> right IP, but it is as though it has been physically removed from the
>> slot and changed place.
>>
>> Is it somehow possible to deal with this problem?
>>
>> pciconf doesn't display those devices.
>
> usbconfig wil
On 03 déc. 2014, at 17:25, Borja Marcos wrote:
> TSO can be disabled in a global way using a sysctl variable: net.inet.tcp.tso
That's it! I've set net.inet.tcp.tso to 0 in /etc/sysctl.conf, rebooted ->
Problem solved:
# sysctl net.inet.tcp.tso
net.inet.tcp.tso: 0
# scp F
I have tried setting this up in /usr/local/etc/devd/devd.conf and used "devd
-d" to re-read rules.
attach 100 {
device-name "ue0";
match "vendor" "0x0b95";
match "product" "0x1790";
match "sernum" "249b0de00c";
action "ifconfig $device-name inet
On Wed, 3 Dec 2014, Martin Hanson wrote:
I have tried setting this up in /usr/local/etc/devd/devd.conf and used "devd
-d" to re-read rules.
attach 100 {
device-name "ue0";
match "vendor" "0x0b95";
match "product" "0x1790";
match "sernum" "249b0de00c";
act
On Thu, 4 Dec 2014, Martin Hanson wrote:
It might need a delay before the device is ready. Running devd in the
foreground like that will show all the detected events.
Indeed that helped.
This is what I got with the output of messages. I don't know how to either give
the device another uniqu
> It might need a delay before the device is ready. Running devd in the
> foreground like that will show all the detected events.
Indeed that helped.
This is what I got with the output of messages. I don't know how to either give
the device another unique name or somehow intercept what is happe
>> This is what I got with the output of messages. I don't know how to either
>> give the device another unique name or somehow intercept what is happening
>> so that I can set the device name.
>>
>> notify 1000 {
>> match "system" "USB";
>> match "subsystem" "INTERFACE";
>> match "
>
> I would use three of these sections, one with the serial number of each
> interface. So:
>
> action "ifconfig $device-name name wan inet ..."
> action "ifconfig $device-name name dmz inet ..."
> action "ifconfig $device-name name lan inet ..."
>
> Then the interface names can be easily used in
I am actually one step closer.
With the following I can get the device-name "axge0", but I don't know how to
create
a usable NIC interface name for that.
attach 1000 {
device-name "axge[0-9]+";
match "vendor" "0x0b95";
match "product" "0x1790";
match "sernum" "249B0DE00C";
On Thu, 4 Dec 2014 06:01:06 +0100, Martin Hanson wrote:
(Warren Block wrote:)
> I would use three of these sections, one with the serial number of each
> interface. So:
>
> action "ifconfig $device-name name wan inet ..."
> action "ifconfig $device-name name dmz inet ..."
> action "ifconfig $devic
23 matches
Mail list logo
