FreeBSD 9.2 - does not appear to support the 'dc' PCMCIA NIC driver

[Kent Kuriyama]

I have a Netgear FA511 PCMCIA NIC that worked fine under 9.1.  Under 9.2 I
get the following message:

Oct  6 21:38:11 monitor4 kernel: dc0:  port 0x1100-0x11ff irq 19 at device 0.0 on cardbus0
Oct  6 21:38:11 monitor4 kernel: dc0: attaching PHYs failed

This used to work under 9.1, does anyone know what happened?  Thanks.

Kent
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: D-Link DUBE100 USB NIC does not work

[Victor Sudakov]

Waitman Gobble wrote:
> >
> > It is written in axe(4) and in the HCL for 9.1 that D-Link DUBE100 is
> > supported.  I have bought one and the system shows it as
> >
> > ugen0.3:  at usbus0, cfg=0 md=HOST spd=HIGH 
> > (480Mbps) pwr=ON (200mA)
> >
> > What am I doing wrong? Why does it not attach a driver to it? Should I
> > do something else besides plugging the device in for the network
> > interface to appear?
> >
> > I am running stable/9 (9.2-BETA2 at the moment).
> 
> Hi, did you see the axe(4) man page? 

Yes. I mentioned it in my message.

> Did you put if_axe_load="YES" in
> loader.conf or build kernel with axe support?

The GENERIC kernel already has "device axe"

[sudakov@vas ~] grep axe /sys/amd64/conf/GENERIC
device  axe # ASIX Electronics USB Ethernet
[sudakov@vas ~] 

[root@vas ~] kldload if_axe
kldload: can't load if_axe: Exec format error
[root@vas ~] dmesg | grep axe
module axe already present!
interface axe.1 already present in the KLD 'kernel'!
[root@vas ~] 

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: D-Link DUBE100 USB NIC does not work

[Waitman Gobble]

On Aug 3, 2013 8:05 AM, "Victor Sudakov"  wrote:
>
> Dear Colleagues,
>
> It is written in axe(4) and in the HCL for 9.1 that D-Link DUBE100 is
> supported.  I have bought one and the system shows it as
>
> ugen0.3:  at usbus0, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=ON (200mA)
>
> What am I doing wrong? Why does it not attach a driver to it? Should I
> do something else besides plugging the device in for the network
> interface to appear?
>
> I am running stable/9 (9.2-BETA2 at the moment).
>
> TIA for any input.
>
> --
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> sip:suda...@sibptus.tomsk.ru

Hi, did you see the axe(4) man page? Did you put if_axe_load="YES" in
loader.conf or build kernel with axe support?

Hope that helps.

Waitman Gobble
San Jose California USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

D-Link DUBE100 USB NIC does not work

[Victor Sudakov]

Dear Colleagues,

It is written in axe(4) and in the HCL for 9.1 that D-Link DUBE100 is
supported.  I have bought one and the system shows it as 

ugen0.3:  at usbus0, cfg=0 md=HOST spd=HIGH 
(480Mbps) pwr=ON (200mA)

What am I doing wrong? Why does it not attach a driver to it? Should I
do something else besides plugging the device in for the network
interface to appear?

I am running stable/9 (9.2-BETA2 at the moment).

TIA for any input.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: How to create vlan (four NIC into one) using lagg

[Boris Astardzhiev]

Hi Xu Zhe,

If I were you I would first of all check cables. They might be the cause.
Secondly, if cables are good, to me this report very much resembles a PR I
reported a
few weeks ago - http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/179926
Check its set and look at the patch I submitted. It's a pity there's no
response to it.

Greetings,
Boris


On Thu, Jul 25, 2013 at 3:55 PM, Xu Zhe  wrote:

> Hi, all,
>
> I am trying to use lagg to bind four 1Gb NIC into 4Gb one. I was testing
> this using two machines running FreeBSD 8.2, each of the machine has
> four 1Gb ethernet card, and connected correspondingly, means:
>
> MACHINE1 MACHINE2
> em0 <->em0
> em1 <->em1
> em2 <->em2
> em3 <->em3
>
> Then I created vlan called 'lagg0' on each machine using:
>
> ifconfig lagg0 create
> ifconfig lagg0 laggproto lacp laggport em0 laggport em1 laggport em2
> laggport em3
> ifconfig lagg0 1.1.1.1/24
> ifconfig lagg0 up
>
> And do this on MACH2 too, only change IP from 1.1.1.1 to 1.1.1.2.
>
> But I cannot ping each other, since none of the link is both active:
>
> MACHINE1
> # ifconfig lagg0
> lagg0: flags=8843 metric 0 mtu 1500
>
> options=219b
> ether 00:08:9b:d4:91:64
> inet 1.1.1.1 netmask 0xff00 broadcast 1.1.1.255
> media: Ethernet autoselect
> status: active
> laggproto lacp
> laggport: em3 flags=1c
> laggport: em2 flags=18
> laggport: em1 flags=18
> laggport: em0 flags=18
>
> MACHINE2
> # ifconfig lagg0
> lagg0: flags=8843 metric 0 mtu 1500
>
> options=219b
> ether 00:08:9b:d3:72:60
> inet 1.1.1.2 netmask 0xff00 broadcast 1.1.1.255
> media: Ethernet autoselect
> status: active
> laggproto lacp
> laggport: em3 flags=18
> laggport: em2 flags=1c
> laggport: em1 flags=1c
> laggport: em0 flags=1c
>
> So, em3 is active on MACHINE1 but not active on MACH2, while em0-em2 are
> active on MACH2 but not on MACHI1.
>
> What might be the problem?
>
> Thanks!
> Peter
> ___
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

How to create vlan (four NIC into one) using lagg

[Xu Zhe]

Hi, all,

I am trying to use lagg to bind four 1Gb NIC into 4Gb one. I was testing
this using two machines running FreeBSD 8.2, each of the machine has
four 1Gb ethernet card, and connected correspondingly, means:

MACHINE1 MACHINE2
em0 <->em0
em1 <->em1
em2 <->em2
em3 <->em3

Then I created vlan called 'lagg0' on each machine using:

ifconfig lagg0 create
ifconfig lagg0 laggproto lacp laggport em0 laggport em1 laggport em2
laggport em3
ifconfig lagg0 1.1.1.1/24
ifconfig lagg0 up

And do this on MACH2 too, only change IP from 1.1.1.1 to 1.1.1.2.

But I cannot ping each other, since none of the link is both active:

MACHINE1
# ifconfig lagg0
lagg0: flags=8843 metric 0 mtu 1500
options=219b
ether 00:08:9b:d4:91:64
inet 1.1.1.1 netmask 0xff00 broadcast 1.1.1.255
media: Ethernet autoselect
status: active
laggproto lacp
laggport: em3 flags=1c
laggport: em2 flags=18
laggport: em1 flags=18
laggport: em0 flags=18

MACHINE2
# ifconfig lagg0
lagg0: flags=8843 metric 0 mtu 1500
options=219b
ether 00:08:9b:d3:72:60
inet 1.1.1.2 netmask 0xff00 broadcast 1.1.1.255
media: Ethernet autoselect
status: active
laggproto lacp
laggport: em3 flags=18
laggport: em2 flags=1c
laggport: em1 flags=1c
laggport: em0 flags=1c

So, em3 is active on MACHINE1 but not active on MACH2, while em0-em2 are
active on MACH2 but not on MACHI1.

What might be the problem?

Thanks!
Peter
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: I'm having big problems with Broadcom NIC (gbe0) on HP ProLiant DL380p 128GB Ram, NIC model HP Ethernet 1Gb 4-port 331FLR, after installed it cannot use a ping command, sometime it can do that but

[Jason Birch]

On Tue, Jun 11, 2013 at 8:08 PM, Surat Sodchuen wrote:

> thank for your kindness
> i tired that your suggestion but cannot resolve problem.
> for more information ...
> FreeBSD 9.1-Release on HP ProLiant DL380p Gen8 128GB of Ram
> every time when booting process it seem freezing about 15 seconds
>
> dmesg look like this
> .
> .
> .
> ACPI Warning: invalid length for Pm1aControlBlock: 32, using default 16
> (20110527/tbfadt-638)
> ACPI Warning: invalid length for Pm1aControlBlock: 32, using default 16
> (20110527/tbfadt-638)
> .
> .
> .
> pci0:3:0:0: failed to read VPD data.
> bge0:  mem
> 0xfabf-0xfabf,
> .
> .
> .
> bge0: link state changed to DOWN
> bge0: link state changed to UP
> bge0: link state changed to DOWN
> bge0: link state changed to UP
> bge0: link state changed to DOWN
> bge0: link state changed to UP
> bge0: link state changed to DOWN
> bge0: link state changed to UP
> bge0: link state changed to DOWN
> bge0: link state changed to UP
> bge0: link state changed to DOWN
> bge0: link state changed to UP
> bge0: link state changed to DOWN
> bge0: link state changed to UP
> bge0: link state changed to DOWN
> bge0: link state changed to UP
> bge0: link state changed to DOWN
> bge0: link state changed to UP
> -
>
> when i use a ping command it seem freezing, then after press Enter it show
> --> bge0 watchdog timeout -- resetting
> i think what happen!!! i use FreeBSD on every 4 of DL380 Gen5, but they
> are OK.
>
> on screen now .. showing message
> bge0: 2 link states coalesced
> bge0: 2 link states coalesced
> bge0: 2 link states coalesced
> bge0: 2 link states coalesced
> bge0: 2 link states coalesced
> bge0: 2 link states coalesced
> bge0: 2 link states coalesced
>

Forwarding to mailing list to keep it in the loop.

It looks like others have run into this issue, and there is an associated
bug report: http://www.freebsd.org/cgi/query-pr.cgi?pr=171121

That link contains an explanation of why my suggestion did not help, and a
suggestion to check the firmware of the controllers.. It also looks like
there's a later version of the bge driver by Pyun YongHyeon that didn't
make it into 9.1-RELEASE that might resolve your issue, were you to compile
it yourself.

Regards,
JB
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Mellanox NIC names changed, each kldunload/kldload mlx4ib module

[Garrett Cooper]

On Jun 9, 2013, at 5:35 AM, Alex Liptsin wrote:

> Hi.
> 
> I work with FreeBSD9.1 and Mellanox devices.
> Every time I unload / load mlx4ib module, NIC names of mellanox devices (ibX) 
> are renamed.
> Can I prevent it?
> 
> [root@h-qa-032 mlx4]# ifconfig
> ib8: flags=8002 metric 0 mtu 65520
>options=80018
>lladdr 80.28.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.31
>nd6 options=29
> ib9: flags=8002 metric 0 mtu 65520
>options=80018
>lladdr 80.28.0.49.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.32
>nd6 options=29
> 
> [root@h-qa-032 mlx4]# kldunload mlx4ib
> 
> [root@h-qa-032 mlx4]# kldload -v mlx4ib
> Loaded mlx4ib, id=9
> 
> [root@h-qa-032 mlx4]# ifconfig
> ib10: flags=8002 metric 0 mtu 65520
>options=80018
>lladdr 80.30.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.31
>nd6 options=29
> ib11: flags=8002 metric 0 mtu 65520
>options=80018
>lladdr 80.30.0.49.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.32
>nd6 options=29


You're probably running into a driver bug because OFED/ipoib was never 
meant to be unloaded (assuming you're using my sources). Check the 
detach/destroy routines to make sure that it's properly detaching everything 
and updating indexes in the network stack before it unloads the driver.
Cheers,
-Garrett

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Mellanox NIC names changed, each kldunload/kldload mlx4ib module

[Alex Liptsin]

Hi.

I work with FreeBSD9.1 and Mellanox devices.
Every time I unload / load mlx4ib module, NIC names of mellanox devices (ibX) 
are renamed.
Can I prevent it?

[root@h-qa-032 mlx4]# ifconfig
ib8: flags=8002 metric 0 mtu 65520
options=80018
lladdr 80.28.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.31
nd6 options=29
ib9: flags=8002 metric 0 mtu 65520
options=80018
lladdr 80.28.0.49.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.32
nd6 options=29

[root@h-qa-032 mlx4]# kldunload mlx4ib

[root@h-qa-032 mlx4]# kldload -v mlx4ib
Loaded mlx4ib, id=9

[root@h-qa-032 mlx4]# ifconfig
ib10: flags=8002 metric 0 mtu 65520
options=80018
lladdr 80.30.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.31
nd6 options=29
ib11: flags=8002 metric 0 mtu 65520
options=80018
lladdr 80.30.0.49.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.32
nd6 options=29

Regards,
Alex Liptsin
Software Quality Assurance Engineer | Mellanox Technologies Ltd.
Office: +972 (74) 7236141
Mobile: +972(54) 7833986
Fax: +972(74) 7236161
Email: al...@mellanox.com<mailto:al...@mellanox.com>
Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: I'm having big problems with Broadcom NIC (gbe0) on HP ProLiant DL380p 128GB Ram, NIC model HP Ethernet 1Gb 4-port 331FLR, after installed it cannot use a ping command, sometime it can do that but

[Jason Birch]

Please include your question as email content, not subject.

http://serverfault.com/questions/361673/hp-nc107i-bcm5723-on-freebsd-9
Indicates
you may be able to set

hw.bge.allow_asf="0"

in /boot/loader.conf. Try this, and if the problem persists, please reply
with more information (FreeBSD version, etc).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

I'm having big problems with Broadcom NIC (gbe0) on HP ProLiant DL380p 128GB Ram, NIC model HP Ethernet 1Gb 4-port 331FLR, after installed it cannot use a ping command, sometime it can do that but sho

[Surat Sodchuen]

Surat Sodchuen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Marwel NIC watchdog timeout

[Leslie Jensen]

...spelling correction

Should be Marvell



2013-05-13 09:48, Leslie Jensen skrev:


I'm having some problems with my Marvell NIC (msk0) and loss of connection.

I found a solution where one could use the settings below:

In

/etc/sysctl.conf

net.inet.tcp.tso=0

And in

/boot/loader.conf

hw.msk.msi_disable=1


This seems to work but the trade-off is that I now only have 100 mbit.
Without the above settings I did have Gigabit but lost the connection.

Is there any way I can get back to Gigabit and still have a stable
connection?

Thanks

/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscr...@freebsd.org"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Marwel NIC watchdog timeout

[Leslie Jensen]

I'm having some problems with my Marwel NIC (msk0) and loss of connection.

I found a solution where one could use the settings below:

In

/etc/sysctl.conf

net.inet.tcp.tso=0

And in

/boot/loader.conf

hw.msk.msi_disable=1


This seems to work but the trade-off is that I now only have 100 mbit. 
Without the above settings I did have Gigabit but lost the connection.


Is there any way I can get back to Gigabit and still have a stable 
connection?


Thanks

/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Access packets directly from NIC

[Jack Mc Lauren]

>I believe that easiest way is using tcpdump.
>Also you should specify what you mean by 'accessing packets': is it
>the need to view raw packet data, or what? :)

Yes, i need to view raw packets and check their protocol, e.g. whether they are 
ICMP packets or something else ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access packets directly from NIC

[Jack Mc Lauren]

>I believe that easiest way is using tcpdump.
>Also you should specify what you mean by 'accessing packets': is it
>the need to view raw packet data, or what? :)

Yes, i need to view raw packets and check their protocol, e.g. whether they are 
ICMP packets or something else ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access packets directly from NIC

[Robert Bonomi]

> From owner-freebsd-questi...@freebsd.org  Wed Oct 31 06:29:57 2012
> From: =?UTF-8?B?0JLQuNGC0LDQu9C40Lkg0KLRg9GA0L7QstC10YY=?=
>  
> Date: Wed, 31 Oct 2012 13:29:05 +0200
> Subject: Re: Access packets directly from NIC
> To: Jack Mc Lauren 
> Cc: FreeBSD Global Users Mailing List 
>
> 2012/10/31 Jack Mc Lauren :
> > Hello FreeBSD users !
> >
> > How can i access and check packets directly from NIC ?
> >
> > Regards, Jack
>
> I believe that easiest way is using tcpdump. Also you should specify what 
> you mean by 'accessing packets': is it the need to view raw packet data, 
> or what? :)
>

tcpdump is _the_ tool for this for command-line use.

For access from within a program, 'man bpf'.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access packets directly from NIC

[Виталий Туровец]

2012/10/31 Jack Mc Lauren :
> Hello FreeBSD users !
>
> How can i access and check packets directly from NIC ?
>
> Regards,
> Jack
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

I believe that easiest way is using tcpdump.
Also you should specify what you mean by 'accessing packets': is it
the need to view raw packet data, or what? :)

-- 




~~~
WBR,
Vitaliy Turovets
NOC Lead @TV-Net ISP
NOC Lead @Service Outsourcing company
+38(093)265-70-55
VITU-RIPE
X-NCC-RegID: ua.tv
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Access packets directly from NIC

[Jack Mc Lauren]

Hello FreeBSD users !

How can i access and check packets directly from NIC ?

Regards,
Jack
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: 9.0 support for RealTek NIC - re0 driver

[doug]

On Fri, 31 Aug 2012, lokada...@gmx.de wrote:


On 08/29/12 18:14, d...@safeport.com wrote:

This card is on a Dell Inspiron. It works perfectly on 8.x. Dmesg on 8.2
reports it as:

  re0: 

pciconf:

re0@pci0:4:0:0: class=0x02 card=0x04341028 chip=0x813610ec rev=0x02 
hdr=0x00

vendor = 'Realtek Semiconductor'
device = 'Realtek 10/100/1000 PCI-E NIC Family all in one NDIS 
Driver v5.728.0604.2009 06/04/2009 (Rtl8023)'

class  = network
subclass   = ethernet

On 9.0 I got it to work once or twice out of a couple of dozen tries.

9.0 dmesg reports:

  re0: RealTek 8139C+/8169/8169S/8110S PCI ...

The release docs imply the card is supported. I did not see a PR. Anyone 
else with similiar issues?

Is the MAC changing?
Give dmesg some message about it?


Not currently in the same city as my Dell. I installed 8.2 to make sure I did 
not have a hardware issue. I will [re]install 9.0 Sunday and report back.


_
Douglas Denault
http://www.safeport.com
d...@safeport.com
Voice: 301-217-9220
  Fax: 301-217-9277
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: 9.0 support for RealTek NIC - re0 driver

[lokada...@gmx.de]

On 08/29/12 18:14, d...@safeport.com wrote:

This card is on a Dell Inspiron. It works perfectly on 8.x. Dmesg on 8.2
reports it as:

  re0: 

pciconf:

re0@pci0:4:0:0: class=0x02 card=0x04341028 chip=0x813610ec 
rev=0x02 hdr=0x00

vendor = 'Realtek Semiconductor'
device = 'Realtek 10/100/1000 PCI-E NIC Family all in one NDIS 
Driver v5.728.0604.2009 06/04/2009 (Rtl8023)'

class  = network
subclass   = ethernet

On 9.0 I got it to work once or twice out of a couple of dozen tries.

9.0 dmesg reports:

  re0: RealTek 8139C+/8169/8169S/8110S PCI ...

The release docs imply the card is supported. I did not see a PR. 
Anyone else with similiar issues?

Is the MAC changing?
Give dmesg some message about it?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

9.0 support for RealTek NIC - re0 driver

[doug]

This card is on a Dell Inspiron. It works perfectly on 8.x. Dmesg on 8.2
reports it as:

  re0: 

pciconf:

re0@pci0:4:0:0: class=0x02 card=0x04341028 chip=0x813610ec rev=0x02 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'Realtek 10/100/1000 PCI-E NIC Family all in one NDIS Driver 
v5.728.0604.2009 06/04/2009 (Rtl8023)'
class  = network
subclass   = ethernet

On 9.0 I got it to work once or twice out of a couple of dozen tries.

9.0 dmesg reports:

  re0: RealTek 8139C+/8169/8169S/8110S PCI ...

The release docs imply the card is supported. I did not see a PR. Anyone else 
with similiar issues?



_
Douglas Denault
http://www.safeport.com
d...@safeport.com
Voice: 301-217-9220
  Fax: 301-217-9277
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Intel ProWireless 2200BG NIC need multicast update

[Yuval Prag]

Hi Im looking for help and some more info on the subject.

the only post i found is from april 2008 the post suggests to add the
capability to the driver based on or copy from a different WiFi
NIC driver and it is not working still same error

the NIC hangs in a way ifconfig show IP address the and status =
associated,  a simple ping to the router works with intermittent failures
in the form of "sento: Network is down" and than it hangs usualy afte the
15th packet send... a restart the NIC device with "/etc/rc.d/netif restart"
will cause the system to reboot!

the driver version comes with the ISO DVD is v1.72, so I was looking for a
new version on the FreeBSD VCS and there is a rev 1.82 posted March 2012
but this one fail the make on line 437 " assignment from incompatible
pointer type" ???

thanks for the time and help
Yuval
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

determine the nic pairs

[Deepak Kumar]

Hi Enthusiast,

I have a server which has around 20 nic interfaces.
Some are connected port to port via cross cable and some are connected via
a switch and few are not connected.
(Let consider all are connected port to port)
I want to find out the way so that I can determine the pairs efficiently.

I assigned ip starting from 172.x.x.30 with netmask 255.255.255.0
I created as many sockets as there are interfaces with
socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP)
then I bind the all but one interfaces to the ip I gave using
bind(sockfd, (struct sockaddr *)&in, sizeof(in));
where in is something like
bzero(&in, sizeof(in));
in.sin_family = AF_INET;
in.sin_port = htons(2074);
in.sin_addr.s_addr = inet_addr("172.x.x.30+interfaceno");

and one left socket I did
socket creation and using setsockopt I did
int option = 1;
setsockopt(sockfd[counter], SOL_SOCKET, SO_BROADCAST, &option,
sizeof(option));
and do
sendto(sockfd, arr, sizeof(arr), 0, (struct sockaddr *)&in, len);
where in is
bzero(&in, sizeof(in));
in.sin_family = AF_INET;
in.sin_port = htons(2074);
in.sin_addr.s_addr = inet_addr(172.x.x.255);

Now I want to send the packet from one interface and who ever receive
should be its partner.
But when I do recvfrom for one socket it blocks and I am not able to
implement timeout for it.
select is not working as it need file discripter and socket call is
returning struct socket.
So how should I implement timeout in recvfrom or use there exist some
equivalent of select for struct socket
or any other way to implement this.

PS: Ping is working fine in determining the pair but taking to much time.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

NIC problem

[Arlen McIntyre]

  I have an Intel Wifi Link 1000 BGN NIC that
I'm having trouble getting to work. I have
FreeBSD 8.3 installed. I looked in the NOTES file under
/usr/src/sys/conf
for the driver and did not see it listed. It is PCI.

   I have tried to configure the settings
via the sysinstall command post configuration.
I read about Project Evil and other options.
I wanted to see if someone could help me
out...


thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: List total traffic amount across external nic

[Dean E. Weimer]

On 06/07/2012 11:14, Fbsd8 wrote:

Running ipfilter and trying to list the total amount of the traffic
passing through the external NIC.

Maybe there is some other command to show this info.

Any help is appreciated.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"freebsd-questions-unsubscr...@freebsd.org"


try: systat -ifstat

--
Thanks,
 Dean E. Weimer
 http://www.dweimer.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: List total traffic amount across external nic

[Matthias Apitz]

El día Thursday, June 07, 2012 a las 12:14:56PM -0400, Fbsd8 escribió:

> Running ipfilter and trying to list the total amount of the traffic 
> passing through the external NIC.
> 
> Maybe there is some other command to show this info.
> 
> Any help is appreciated.

In the past I used for this:

$ cd /usr/ports/net/trafshow
$ cat pkg-descr 
TrafShow continuously displays the information regarding packet
traffic on the configured network interface that matches the boolean
expression. It periodically sorts and updates this information. It
may be useful for locating suspicious network traffic on the net.

WWW: http://soft.risp.ru/trafshow/index_en.shtml

HIH

matthias
-- 
Matthias Apitz
e  - w http://www.unixarea.de/
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

List total traffic amount across external nic

[Fbsd8]

Running ipfilter and trying to list the total amount of the traffic 
passing through the external NIC.


Maybe there is some other command to show this info.

Any help is appreciated.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

msk0 NIC getting stuck

[Jukka A. Ukkonen]

Greetings all,

Has anyone seen similar problems as this...


Nov 22 14:49:49 sleipnir kernel: msk0: watchdog timeout
Nov 22 14:49:49 sleipnir kernel: msk0: prefetch unit stuck?
Nov 22 14:49:49 sleipnir kernel: msk0: initialization failed: no memory for Rx b
uffers


The NIC freezes completely and will not return to sanity with
"ifconfig msk0 down" and "ifconfig msk0 up".

The environment this happens on is
FreeBSD sleipnir 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #0: Sun Nov 20 17:34:27
EET 2011 root@sleipnir:/usr/obj/usr/src/sys/Sleipnir  amd64

The same thing happens with the GENERIC kernel as well as with my
locally compiled kernel. The only difference in the kernels is that
the locally compiled one supports 4 fibs.

The hardware is a Supermicro H8DCL-6F motherboard with 2 AMD 4162EE CPUs
and 16GB of memory.
All of the file systems are mirrored on top of GUID partitions.
Most of them are UFS2+SU on top of gmirror and one ZFS on top of zpool
mirror.


Cheers,
// jau
.---  ..-  -.-  -.-  .-.-  .-.-.-..-  -.-  -.-  ---  -.  .  -.
  /Jukka A. Ukkonen, Oxit Ltd, Finland
 /__   M.Sc. (sw-eng & cs)(Phone) +358-500-606-671
   /   Internet: Jukka.Ukkonen(a)Oxit.Fi
  /Internet: jau(a)iki.fi
 v
.---  .-  ..-  ...-.-  ..  -.-  ..  .-.-.-  ..-.  ..
+ + + + My opinions are mine and mine alone, not my employers. + + + +
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

RE: Intel 82573E NIC and BMC with FreeBSD 8

[Rafael NAVAZA]

Ok I got the BMC responding when the "em" driver is loaded.

I had
 to comment out the line corresponding to the "CRC Stripping" (#4153) in
 /usr/src/sys/dev/e1000/if_em.c and compile/install/loader.conf the 
driver.

I know (from my google searches) that by doing it some 
other intel nics will not function properly with the driver. The only 
way to make every one happy would be to add a sysctl param to the driver, 
something like "hw.em.disable_crc_stripping" .

Where can I commit such thing ?

Rafael.

> From: rnav...@hotmail.com
> To: freebsd-questions@freebsd.org
> Date: Tue, 13 Sep 2011 19:24:02 +0200
> Subject: Intel 82573E NIC and BMC with FreeBSD 8
> 
> 
> Hi there,
> 
> I added a M3291 BMC on a TYAN S5197 motherboard and I'm trying to make it 
> work with FreeBSD 8.
> 
> I first tried to set it up with Linux, and it was pretty annoying ...
> What TYAN DID say to do is :
> 
> - DOS, flash the S5197 Motherboard with the latest BIOS 
> - DOS, flash the M3291 BMC with the correct Firmware
> - DOS, flash the Intel NIC (82573E) EEProm to enable IPMI
> - DOS, configure the MAC/IP of the BMC (I choose a BMC MAC different from the 
> NIC MAC, and of course an IP different from the host)
> - LINUX, "modprobe ipmi_si type=kcs ports=0xca8 irqs=0 regspacings=4"
> 
> All that is correct but not sufficient because I can only access to the BMC 
> locally !!!
> WHAT TYAN FORGOT TO SAY IS :
> 
> - DOS, declare the BMC MAC on the Intel NIC (82573E) EEProm "eeupdate.exe 
> /NIC=1 /MNGMAC=00:E0:81:XX:XX:XX"
> - LINUX, "modprobe e1000e CrcStripping=0"
> 
> Now it works with Linux :D
> 
> Now it is the FreeBSD turn :)
> 
> Well, it doesn't work "as is" ... :
> 
> - FREEBSD, "kldload ipmi" -> doesn't give access to the BMC locally
> - FREEBSD, "ifconfig_em0=DHCP" -> makes the BMC to stop responding
> 
> My question : is there any equivalent in FreeBSD of the Linux kernel 
> parameters that I have previously used ?
> 
> Any help would be appreciated ;) 
> 
> Regards,
> Rafael NAVAZA.
> 


  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Intel 82573E NIC and BMC with FreeBSD 8

[Rafael NAVAZA]

Hi there,

I added a M3291 BMC on a TYAN S5197 motherboard and I'm trying to make it work 
with FreeBSD 8.

I first tried to set it up with Linux, and it was pretty annoying ...
What TYAN DID say to do is :

- DOS, flash the S5197 Motherboard with the latest BIOS 
- DOS, flash the M3291 BMC with the correct Firmware
- DOS, flash the Intel NIC (82573E) EEProm to enable IPMI
- DOS, configure the MAC/IP of the BMC (I choose a BMC MAC different from the 
NIC MAC, and of course an IP different from the host)
- LINUX, "modprobe ipmi_si type=kcs ports=0xca8 irqs=0 regspacings=4"

All that is correct but not sufficient because I can only access to the BMC 
locally !!!
WHAT TYAN FORGOT TO SAY IS :

- DOS, declare the BMC MAC on the Intel NIC (82573E) EEProm "eeupdate.exe 
/NIC=1 /MNGMAC=00:E0:81:XX:XX:XX"
- LINUX, "modprobe e1000e CrcStripping=0"

Now it works with Linux :D

Now it is the FreeBSD turn :)

Well, it doesn't work "as is" ... :

- FREEBSD, "kldload ipmi" -> doesn't give access to the BMC locally
- FREEBSD, "ifconfig_em0=DHCP" -> makes the BMC to stop responding

My question : is there any equivalent in FreeBSD of the Linux kernel parameters 
that I have previously used ?

Any help would be appreciated ;) 

Regards,
Rafael NAVAZA.

  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[pete wright]

On Fri, Jul 22, 2011 at 1:26 PM, Michael W. Lucas
 wrote:
> On Fri, Jul 22, 2011 at 04:15:11PM -0400, Mike Tancsa wrote:
>> On 7/22/2011 4:10 PM, Michael W. Lucas wrote:

> Will applications such as NFS cut bandwith usage that much?
>
I have seen similar performance degradations with NFS in the past.  I
have seem cases where throughput is hurt due to frequent getattr()
calls by the NFS client (esp noticable on Linux hosts traversing large
namespaces fwiw).

Some possible workarounds/tweaks:
1) increase rsize/wsize (32k for larger files for example) of client mount
2) if performance is only requirement UDP will increase performance
versus TCP with obvious downside of using UDP :)
3) jumbo frames (MTU=9000) should help in most cases if available

I've also done a bit of testing with NFSv4 - and I find performance
here can be a bit better than v3 due to better attribute caching
(decreasing amount of getattr() calls when traversing filesystems) and
other interesting bigs v4 has.  Granted moving from v3 to v4 is not
trivial...


just my two bits :)
-pete


-- 
pete wright
www.nycbug.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Michael W. Lucas]

On Fri, Jul 22, 2011 at 04:15:11PM -0400, Mike Tancsa wrote:
> On 7/22/2011 4:10 PM, Michael W. Lucas wrote:
> > 
> > 
> > 3.65  419155.4
> 
> Thats 400Mb/s no ?   Whats the CPU in this thing ? Also your NIC version
> was 7.1.9.  RELENG_8 has 7.2.3. Can you try that version if possible ?

 I sit corrected, decimal point error. My apologies, long
day here.

For the CPU, 400Mbs isn't bad.

CPU: Intel(R) Celeron(R) CPU  420  @ 1.60GHz (1600.01-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x10661  Family = 6  Model = 16  Stepping = 1
  
Features=0xafebfbff
  Features2=0xe31d
  AMD Features=0x20100800
  AMD Features2=0x1
  TSC: P-state invariant

My ~30MB/s from applications is roughly 240Mb/s. 

Will applications such as NFS cut bandwith usage that much?

I'll try the newer driver.


> > So no, I'm not saturating this network. Not even close. I have a
> > machine with a 100Mbs vr0 that can spit out twice that much.
> 
> How could FastE nics do 800Mb/s ?

Same decimal point error. It's clearly time for me go home.

Thanks,
==ml

-- 
Michael W. Lucas
http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/
Latest book: Network Flow Analysis http://www.networkflowanalysis.com/
mwlu...@blackhelicopters.org, Twitter @mwlauthor
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Mike Tancsa]

On 7/22/2011 4:10 PM, Michael W. Lucas wrote:
> 
> 
> 3.65  419155.4

Thats 400Mb/s no ?   Whats the CPU in this thing ? Also your NIC version
was 7.1.9.  RELENG_8 has 7.2.3. Can you try that version if possible ?

> So no, I'm not saturating this network. Not even close. I have a
> machine with a 100Mbs vr0 that can spit out twice that much.

How could FastE nics do 800Mb/s ?

---Mike


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Michael W. Lucas]

On Fri, Jul 22, 2011 at 03:46:06PM -0400, Mike Tancsa wrote:
> On 7/22/2011 3:08 PM, Michael W. Lucas wrote:
> > 
> > Basically the same.  I don't think it's disk.
> 
> Are you able to saturate the ethernet ?  Try something like
> 
> 
> /usr/src/tools/tools/netrate/netblast/netblast
> 
> on the local ethernet and see if you can generate and receive a full
> gigabit on the wire

Very helpful, thank you. Copied ifstat and netblast from an 8.0 box to
the freenas box, and started firing traffic at a machine on the local
network.

./netblast x.x.x.x 500 250 10

start: 1311364875.158297086
finish:1311364885.158882731
send calls:1826947
send errors:   11
approx send rate:  182693
approx error rate: 0

ifstat -b -i em0 shows:

   17.84  214390.1
3.65  419155.4
4.12  418916.4
3.65  419466.2
  410.14  417715.7
5.06  418383.2
 3120.18  410983.4
   em0
 Kbps in  Kbps out
3.65  412871.2
3.65  416097.9
3.65  416431.1
5.65  195233.8

So no, I'm not saturating this network. Not even close. I have a
machine with a 100Mbs vr0 that can spit out twice that much.

==ml


> # ./netblast 10.11.11.243 500 250 10
> 
> start: 1311363559.619619931
> finish:1311363569.619418229
> send calls:5210086
> send errors:   1249890
> approx send rate:  396019
> approx error rate: 0
> 
> 
> ./netblast 10.11.11.241 500 300 10
> 
> start: 1311346264.584043978
> finish:1311346274.583848423
> send calls:7417664
> send errors:   4214676
> approx send rate:  320298
> approx error rate: 0
> 
> 
> When the sender if an igb nic, I am able to push out 955Mb to the em0
> nic acting as a sink. The other way around, 855Mb
> The em nic is
> 
> em1@pci0:5:0:0: class=0x02 card=0x34ec8086 chip=0x10d38086 rev=0x00
> hdr=0x00
> vendor = 'Intel Corporation'
> device = 'Intel 82574L Gigabit Ethernet Controller (82574L)'
> class  = network
> subclass   = ethernet
> bar   [10] = type Memory, range 32, base 0xb250, size 131072,
> enabled
> bar   [18] = type I/O Port, range 32, base 0x1000, size 32, enabled
> bar   [1c] = type Memory, range 32, base 0xb252, size 16384, enabled
> cap 01[c8] = powerspec 2  supports D0 D3  current D0
> cap 05[d0] = MSI supports 1 message, 64 bit
> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
> cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled
> ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected
> ecap 0003[140] = Serial 1 001517ed36e4
> 
> em1:  port 0x1000-0x101f mem
> 0xb250-0xb251,0xb252-0xb2523fff irq 16 at device 0.0 on pci5
> em1: Using MSIX interrupts with 3 vectors
> em1: [ITHREAD]
> em1: [ITHREAD]
> em1: [ITHREAD]
> em1: Ethernet address: 00:15:17:ed:36:e4
> 
> 
> 
> ifstat -b shows
> 
> # ifstat -b -i igb0
>igb0
>  Kbps in  Kbps out
> 0.00  0.00
> 0.00  0.00
> 578794.0  0.00
> 855298.0  0.00
> 855365.9  0.00
> 855316.6  0.00
> 855335.2  0.00
> 855346.5  0.00
> 855358.6  0.00
> 855368.7  0.00
> 855356.6  0.00
> 727163.6  0.00
> 0.00  0.00
> 
> thats the em equipped machine generating the traffic
> 
> 
>   ---Mike
> 
> 
> 
> 
> 
> > 
> > There's kern/152828 claiming a performance regression with em under
> > 8.2, but I'm not sure if that is applicable to my system. I'd upgrade
> > the kernel to test, but I'm not brave enough to downgrade the kernel
> > to 8.0 for comparison. (I've never had good luck running an old kernel
> > on a new userland.)
> > 
> > ==ml
> > 
> 
> 
> -- 
> ---
> Mike Tancsa, tel +1 519 651 3400
> Sentex Communications, m...@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge, Ontario Canada   http://www.tancsa.com/

-- 
Michael W. Lucas
http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/
Latest book: Network Flow Analysis http://www.networkflowanalysis.com/
mwlu...@blackhelicopters.org, Twitter @mwlauthor
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Mike Tancsa]

On 7/22/2011 3:08 PM, Michael W. Lucas wrote:
> 
> Basically the same.  I don't think it's disk.

Are you able to saturate the ethernet ?  Try something like


/usr/src/tools/tools/netrate/netblast/netblast

on the local ethernet and see if you can generate and receive a full
gigabit on the wire



# ./netblast 10.11.11.243 500 250 10

start: 1311363559.619619931
finish:1311363569.619418229
send calls:5210086
send errors:   1249890
approx send rate:  396019
approx error rate: 0


./netblast 10.11.11.241 500 300 10

start: 1311346264.584043978
finish:1311346274.583848423
send calls:7417664
send errors:   4214676
approx send rate:  320298
approx error rate: 0


When the sender if an igb nic, I am able to push out 955Mb to the em0
nic acting as a sink. The other way around, 855Mb
The em nic is

em1@pci0:5:0:0: class=0x02 card=0x34ec8086 chip=0x10d38086 rev=0x00
hdr=0x00
vendor = 'Intel Corporation'
device = 'Intel 82574L Gigabit Ethernet Controller (82574L)'
class  = network
subclass   = ethernet
bar   [10] = type Memory, range 32, base 0xb250, size 131072,
enabled
bar   [18] = type I/O Port, range 32, base 0x1000, size 32, enabled
bar   [1c] = type Memory, range 32, base 0xb252, size 16384, enabled
cap 01[c8] = powerspec 2  supports D0 D3  current D0
cap 05[d0] = MSI supports 1 message, 64 bit
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled
ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected
ecap 0003[140] = Serial 1 001517ed36e4

em1:  port 0x1000-0x101f mem
0xb250-0xb251,0xb252-0xb2523fff irq 16 at device 0.0 on pci5
em1: Using MSIX interrupts with 3 vectors
em1: [ITHREAD]
em1: [ITHREAD]
em1: [ITHREAD]
em1: Ethernet address: 00:15:17:ed:36:e4



ifstat -b shows

# ifstat -b -i igb0
   igb0
 Kbps in  Kbps out
0.00  0.00
0.00  0.00
578794.0  0.00
855298.0  0.00
855365.9  0.00
855316.6  0.00
855335.2  0.00
855346.5  0.00
855358.6  0.00
855368.7  0.00
855356.6  0.00
727163.6  0.00
0.00  0.00

thats the em equipped machine generating the traffic


---Mike





> 
> There's kern/152828 claiming a performance regression with em under
> 8.2, but I'm not sure if that is applicable to my system. I'd upgrade
> the kernel to test, but I'm not brave enough to downgrade the kernel
> to 8.0 for comparison. (I've never had good luck running an old kernel
> on a new userland.)
> 
> ==ml
> 


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Mike Tancsa]

On 7/22/2011 3:08 PM, Michael W. Lucas wrote:
> 
> Basically the same.  I don't think it's disk.

Are you able to saturate the ethernet ?  Try something like


/usr/src/tools/tools/netrate/netblast/netblast

on the local ethernet and see if you can generate and receive a full
gigabit on the wire

---Mike

> 
> There's kern/152828 claiming a performance regression with em under
> 8.2, but I'm not sure if that is applicable to my system. I'd upgrade
> the kernel to test, but I'm not brave enough to downgrade the kernel
> to 8.0 for comparison. (I've never had good luck running an old kernel
> on a new userland.)
> 
> ==ml
> 


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Michael W. Lucas]

On Fri, Jul 22, 2011 at 02:06:23PM -0400, Mike Tancsa wrote:
> On 7/22/2011 1:50 PM, Eduardo Morras wrote:
> > At 17:12 21/07/2011, Michael W. Lucas wrote:
> >> On Thu, Jul 21, 2011 at 05:01:57PM +0200, Eduardo Morras wrote:
> >> >
> >> > Have you tried other protocols? Http, rsync... It maybe a problem at
> >> > client side, some ftp clients can set a maximun ftp transfer, like
> >> > filezilla, winscp,
> >>
> >> FTP and NFSv3 both have similar results.
> >>
> >> ==ml
> > 
> > Perhaps you have reached the maximum disk speed. Sorry not more ideas,
> > but it doesn't look like a nic problem. Put the file in cache before
> > sending it. If it's faster the problem is a bottleneck on hard disk or
> > sata/ata/usb bus.
> 
> What if you do a fetch -o /dev/null {http|ftp}://remotesite/file
> 
> and see what speeds you get. That would get rid of the disk as an io issue

Good idea.

fetch -o /dev/null ftp://xxx/ftp/FreeBSD-9.0-CURRENT-201011-amd64-dvd1.iso
/dev/null 100% of 1027 MB   29 MBps 00m00s

Basically the same.  I don't think it's disk.

There's kern/152828 claiming a performance regression with em under
8.2, but I'm not sure if that is applicable to my system. I'd upgrade
the kernel to test, but I'm not brave enough to downgrade the kernel
to 8.0 for comparison. (I've never had good luck running an old kernel
on a new userland.)

==ml

-- 
Michael W. Lucas
http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/
Latest book: Network Flow Analysis http://www.networkflowanalysis.com/
mwlu...@blackhelicopters.org, Twitter @mwlauthor
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Mike Tancsa]

On 7/22/2011 1:50 PM, Eduardo Morras wrote:
> At 17:12 21/07/2011, Michael W. Lucas wrote:
>> On Thu, Jul 21, 2011 at 05:01:57PM +0200, Eduardo Morras wrote:
>> >
>> > Have you tried other protocols? Http, rsync... It maybe a problem at
>> > client side, some ftp clients can set a maximun ftp transfer, like
>> > filezilla, winscp,
>>
>> FTP and NFSv3 both have similar results.
>>
>> ==ml
> 
> Perhaps you have reached the maximum disk speed. Sorry not more ideas,
> but it doesn't look like a nic problem. Put the file in cache before
> sending it. If it's faster the problem is a bottleneck on hard disk or
> sata/ata/usb bus.

What if you do a fetch -o /dev/null {http|ftp}://remotesite/file

and see what speeds you get. That would get rid of the disk as an io issue

---Mike

> 
> HTH
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscr...@freebsd.org"
> 
> 


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Eduardo Morras]

At 17:12 21/07/2011, Michael W. Lucas wrote:

On Thu, Jul 21, 2011 at 05:01:57PM +0200, Eduardo Morras wrote:
>
> Have you tried other protocols? Http, rsync... It maybe a problem at
> client side, some ftp clients can set a maximun ftp transfer, like
> filezilla, winscp,

FTP and NFSv3 both have similar results.

==ml


Perhaps you have reached the maximum disk speed. Sorry not more 
ideas, but it doesn't look like a nic problem. Put the file in cache 
before sending it. If it's faster the problem is a bottleneck on hard 
disk or sata/ata/usb bus.


HTH 



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Jerry]

On Thu, 21 Jul 2011 16:31:25 +
Peter Harrison articulated:

> Sorry for top posting. My 'phone makes it awkward.
> 
> I use ndis for the wifi connection in my netbook. Was trivial to
> convert the Windows driver, and it works without issue.
> 
> Anyone know whether it could do 'N' class devices, to address Jerry's
> longstanding (and vocal, and justified) complaint - so that we can
> have an argument about why I'd rather configure my wireless manually
> in a text file and not have it done automagically by the OS and not
> be side-tracked by the non-availability of drivers?

Problem one was that NDIS was not working on 64 bit systems. I believe
that has been addressed; however I cannot confirm it. The last time I
tired was approximately three months ago. It would not work on the
system, ie, the system would not use the driver. I even tried a piece
of shit USB device (N protocol) on another one of my FreeBSD machines,
and that failed also. The last of my FreeBSD laptops is now gone; they
are all Win7 machines. I still have two towers, one with wireless USB
that fails on FreeBSD.

Now, I have absolutely no problem with you manually creating a file(s),
etc to get a connection created. On the other hand, my 10 year old
niece was visiting a few weeks ago. Like all kids, she had her laptop
with her. Upon turning it on, it discovered my wireless network. All I
had to do was give her the password, and she was on. Of course we are
not talking about network discovery and but rather the act of getting a
wireless card working in the first place. To a degree, they are
connected though.

Computers should make life easier, not more complicated. Manually
having to discover what form of encryption is being used on a network
when it can be done automatically, etcetera, just does not suit my
definition of easier. I would much rather be playing a round of golf
while you are debugging a wireless connection. So if you are looking
for an argument as to why you should not be manually forced to
configure a simple device that can and is automatically handled by
other OSs, you will not get an argument from me. That is unless you
think that I should also be forced to do the same. The "Marquis de
Sade" isn't my hero and I am definitely not into "sadism".


-- 
Jerry ✌
jerry+f...@seibercom.net

Disclaimer: off-list followups get on-list replies or ignored.
Do not CC this poster. Please do not ignore the "Reply-To" header.

http://www.catb.org/~esr/faqs/smart-questions.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

RE: em0 NIC slow on 8.2-p1 amd64?

[Peter Harrison]

Sorry for top posting. My 'phone makes it awkward.

I use ndis for the wifi connection in my netbook. Was trivial to convert the 
Windows driver, and it works without issue.

Anyone know whether it could do 'N' class devices, to address Jerry's 
longstanding (and vocal, and justified) complaint - so that we can have an 
argument about why I'd rather configure my wireless manually in a text file and 
not have it done automagically by the OS and not be side-tracked by the 
non-availability of drivers?



--
Peter Harrison
www.4harrisons.blogspot.com
-Original Message-
From: per...@pluto.rain.com
Sent:  21/07/2011 13:05:54
To: nec...@retena.com
Cc: questi...@freebsd.org; mwlu...@blackhelicopters.org
Subject:  Re: em0 NIC slow on 8.2-p1 amd64?

Eduardo Morras  wrote:

> If it's not connected at 1 gigabit or not full duplex you can
> force it with ifconfig. If there are too much errors check the
> cable.

Last I heard, this does _not_ work with gigabit unless you can
force-configure both ends of the link.  The negotiation protocol is
such that force-configuring just one end _guarantees_ a mismatch.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Michael W. Lucas]

On Thu, Jul 21, 2011 at 05:01:57PM +0200, Eduardo Morras wrote:
> 
> Have you tried other protocols? Http, rsync... It maybe a problem at 
> client side, some ftp clients can set a maximun ftp transfer, like 
> filezilla, winscp, 

FTP and NFSv3 both have similar results.

==ml

-- 
Michael W. Lucas
http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/
Latest book: Network Flow Analysis http://www.networkflowanalysis.com/
mwlu...@blackhelicopters.org, Twitter @mwlauthor
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Eduardo Morras]

Have you tried other protocols? Http, rsync... It maybe a problem at 
client side, some ftp clients can set a maximun ftp transfer, like 
filezilla, winscp, 



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Michael W. Lucas]

On Wed, Jul 20, 2011 at 09:32:27PM +0200, Eduardo Morras wrote:
> At 21:16 20/07/2011, Michael W. Lucas wrote:
> 
> >It's at gigabit:
> >
> >em0: flags=8843 metric 0 mtu 1500
> >
> >options=219b
> >ether 00:15:17:31:c8:fe
> >inet xxx
> >media: Ethernet autoselect (1000baseT )
> >status: active
> 
> All seems to be ok, try a netstat -I em0 -d  (it's a capital 'i') to 
> get statistics. If too much packets are dropped recheck cables.
> 
> Other options:
> 
> a) 30 MB/s looks very strange, do you have pf or similar with a filter rule?
> b) Have you checked your disk i/o performance?
> c) If you generate the data dinamically, may be your producer app is 
> the problem.
> 
> About the em specific problem under 8.2 you cite, others can guide 
> better than me.
> 
> HTH

No obvious errors on netstat:

netstat -I em0 -d
NameMtu Network   Address  Ipkts Ierrs IdropOpkts Oerrs 
 Coll Drop
em01500   00:15:17:31:c8:fe 11709782 0 0  6855755 0 
00 
em01500 139.171.199.0 data5-vm   9546994 - -  7584135 - 
-- 

PF is running, but disabling it makes no difference in throughput.

Disk is mostly idle... not saying it can't be disk, mind you, but
local disk-to-disk copies go much more quickly. I'm testing by copying
an ISO.

And as far as me knowing "many more things," well, if I knew what the
problem was, I wouldn't be begging for help like any other user.  :-)

Thanks,
==ml

-- 
Michael W. Lucas
http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/
Latest book: Network Flow Analysis http://www.networkflowanalysis.com/
mwlu...@blackhelicopters.org, Twitter @mwlauthor
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Michael W. Lucas]

On Wed, Jul 20, 2011 at 05:19:47PM -0400, Mike Tancsa wrote:
> On 7/20/2011 12:04 PM, Michael W. Lucas wrote:
> > Hi,
> > 
> > I'm running FreeNAS 8.0/amd64, with an 8.2-p1 kernel.  When using FTP
> > or SCP, performance maxes out around 30MB/s. This is on a gigabit
> > network, no errors showing. 
> 
> what does
> sysctl -a dev.em
> 
> show ?
> 
> What kind of switch is the box plugged into ? Can you show the output of
> the switch interface showing how its connected e.g. flow control,
> duplex, interface counters etc.

It's an HP Procurve 3400cl-24g.

  Port  Type  | Enabled Mode Flow Ctrl MDI 
...
  15100/1000T | Yes Auto Disable   Auto


  | Intrusion   MDI   Flow  Bcast 
  Port  Type  | Alert Enabled Status Mode   Mode  Ctrl  Limit 
...
  15100/1000T | NoYes Up 1000FDxMDI   off   0 

 Status and Counters - Port Counters for port 15  

  Name  : data5
  Link Status : Up  
  Totals (Since boot or last clear) :
   Bytes Rx: 2,717,700,038  Bytes Tx: 2,179,415,738 
   Unicast Rx  : 162,116,833Unicast Tx  : 190,514,323   
   Bcast/Mcast Rx  : 51,058 Bcast/Mcast Tx  : 35,257,606
  Errors (Since boot or last clear) :
   FCS Rx  : 0  Drops Rx: 0 
   Alignment Rx: 0  Collisions Tx   : 0 
   Runts Rx: 0  Late Colln Tx   : 0 
   Giants Rx   : 0  Excessive Colln : 0 
   Total Rx Errors : 0  Deferred Tx : 0 
  Rates (5 minute weighted average) :
   Total Rx  (bps) : 2428792Total Tx  (bps) : 5019632   
   Unicast Rx (Pkts/sec) : 0Unicast Tx (Pkts/sec) : 0 
   B/Mcast Rx (Pkts/sec) : 0B/Mcast Tx (Pkts/sec) : 1 
   Utilization Rx  : 00.24 %Utilization Tx  : 00.50 %


dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.1.9
dev.em.0.%driver: em
dev.em.0.%location: slot=0 function=0
dev.em.0.%pnpinfo: vendor=0x8086 device=0x108b subvendor=0x8086 
subdevice=0x class=0x02
dev.em.0.%parent: pci1
dev.em.0.nvm: -1
dev.em.0.debug: -1
dev.em.0.rx_int_delay: 0
dev.em.0.tx_int_delay: 66
dev.em.0.rx_abs_int_delay: 66
dev.em.0.tx_abs_int_delay: 66
dev.em.0.rx_processing_limit: 100
dev.em.0.flow_control: 3
dev.em.0.link_irq: 0
dev.em.0.mbuf_alloc_fail: 0
dev.em.0.cluster_alloc_fail: 0
dev.em.0.dropped: 0
dev.em.0.tx_dma_fail: 0
dev.em.0.rx_overruns: 0
dev.em.0.watchdog_timeouts: 0
dev.em.0.device_control: 1075053128
dev.em.0.rx_control: 67141634
dev.em.0.fc_high_water: 10240
dev.em.0.fc_low_water: 8740
dev.em.0.queue0.txd_head: 338
dev.em.0.queue0.txd_tail: 338
dev.em.0.queue0.tx_irq: 0
dev.em.0.queue0.no_desc_avail: 0
dev.em.0.queue0.rxd_head: 375
dev.em.0.queue0.rxd_tail: 374
dev.em.0.queue0.rx_irq: 0
dev.em.0.mac_stats.excess_coll: 0
dev.em.0.mac_stats.single_coll: 0
dev.em.0.mac_stats.multiple_coll: 0
dev.em.0.mac_stats.late_coll: 0
dev.em.0.mac_stats.collision_count: 0
dev.em.0.mac_stats.symbol_errors: 0
dev.em.0.mac_stats.sequence_errors: 0
dev.em.0.mac_stats.defer_count: 0
dev.em.0.mac_stats.missed_packets: 0
dev.em.0.mac_stats.recv_no_buff: 0
dev.em.0.mac_stats.recv_undersize: 0
dev.em.0.mac_stats.recv_fragmented: 0
dev.em.0.mac_stats.recv_oversize: 0
dev.em.0.mac_stats.recv_jabber: 0
dev.em.0.mac_stats.recv_errs: 0
dev.em.0.mac_stats.crc_errs: 0
dev.em.0.mac_stats.alignment_errs: 0
dev.em.0.mac_stats.coll_ext_errs: 0
dev.em.0.mac_stats.xon_recvd: 0
dev.em.0.mac_stats.xon_txd: 0
dev.em.0.mac_stats.xoff_recvd: 0
dev.em.0.mac_stats.xoff_txd: 0
dev.em.0.mac_stats.total_pkts_recvd: 11708739
dev.em.0.mac_stats.good_pkts_recvd: 11708739
dev.em.0.mac_stats.bcast_pkts_recvd: 2121887
dev.em.0.mac_stats.mcast_pkts_recvd: 57365
dev.em.0.mac_stats.rx_frames_64: 464757
dev.em.0.mac_stats.rx_frames_65_127: 4131944
dev.em.0.mac_stats.rx_frames_128_255: 43756
dev.em.0.mac_stats.rx_frames_256_511: 204667
dev.em.0.mac_stats.rx_frames_512_1023: 492040
dev.em.0.mac_stats.rx_frames_1024_1522: 6371575
dev.em.0.mac_stats.good_octets_recvd: 10457944503
dev.em.0.mac_stats.good_octets_txd: 2875493372
dev.em.0.mac_stats.total_pkts_txd: 7967315
dev.em.0.mac_stats.good_pkts_txd: 7967315
dev.em.0.mac_stats.bcast_pkts_txd: 121
dev.em.0.mac_stats.mcast_pkts_txd: 0
dev.em.0.mac_stats.tx_frames_64: 1739777
dev.em.0.mac_stats.tx_frames_65_127: 3871275
dev.em.0.mac_stats.tx_frames_128_255: 270032
dev.em.0.mac_stats.tx_frames_256_511: 412542
dev.em.0.mac_stats.tx_frames_512_1023: 255864
dev.em.0.mac_stats.tx_frames_1024_1522: 1417825
dev.em.0.mac_stats.tso_txd: 427046
dev.em.0.mac_stats.tso_ctx_fail: 0
dev.em.0.interrupts.asserts: 10716051
dev.em.0.interrupts.rx_pkt_timer: 1157
dev.em.0.interrupts.rx_abs_timer: 24
dev.em.0.interrupt

Re: em0 NIC slow on 8.2-p1 amd64?

[perryh]

Eduardo Morras  wrote:

> If it's not connected at 1 gigabit or not full duplex you can
> force it with ifconfig. If there are too much errors check the
> cable.

Last I heard, this does _not_ work with gigabit unless you can
force-configure both ends of the link.  The negotiation protocol is
such that force-configuring just one end _guarantees_ a mismatch.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Mike Tancsa]

On 7/20/2011 12:04 PM, Michael W. Lucas wrote:
> Hi,
> 
> I'm running FreeNAS 8.0/amd64, with an 8.2-p1 kernel.  When using FTP
> or SCP, performance maxes out around 30MB/s. This is on a gigabit
> network, no errors showing. 

what does
sysctl -a dev.em

show ?

What kind of switch is the box plugged into ? Can you show the output of
the switch interface showing how its connected e.g. flow control,
duplex, interface counters etc.

---Mike

-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Eduardo Morras]

At 21:16 20/07/2011, Michael W. Lucas wrote:


It's at gigabit:

em0: flags=8843 metric 0 mtu 1500

options=219b
ether 00:15:17:31:c8:fe
inet xxx
media: Ethernet autoselect (1000baseT )
status: active


All seems to be ok, try a netstat -I em0 -d  (it's a capital 'i') to 
get statistics. If too much packets are dropped recheck cables.


Other options:

a) 30 MB/s looks very strange, do you have pf or similar with a filter rule?
b) Have you checked your disk i/o performance?
c) If you generate the data dinamically, may be your producer app is 
the problem.


About the em specific problem under 8.2 you cite, others can guide 
better than me.


HTH


Thanks,
==ml



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Michael W. Lucas]

On Wed, Jul 20, 2011 at 07:12:27PM +0200, Eduardo Morras wrote:
> At 18:04 20/07/2011, Michael W. Lucas wrote:
> >Hi,
> >
> >I'm running FreeNAS 8.0/amd64, with an 8.2-p1 kernel.  When using FTP
> >or SCP, performance maxes out around 30MB/s. This is on a gigabit
> >network, no errors showing.
> >
> >It looks a lot like kern/152828, but it seems that nobody's looking at
> >that.
> 
> Don't know about that, but perhaps the nic is not working at full gigabit.
> 
> Can you post the output of ifconfig?
> 
> #ifconfig em0
> 

It's at gigabit:

em0: flags=8843 metric 0 mtu 1500

options=219b
ether 00:15:17:31:c8:fe
inet xxx
media: Ethernet autoselect (1000baseT )
status: active

Thanks, 
==ml


> If it's not connected at 1 gigabit or not full duplex you can force 
> it with ifconfig. If there are too much errors check the cable.
> 
> >As per suggestions from the archives, I've tried disabling TSO. No
> >change.
> >
> >Anyone else experiencing this, or have any suggestions? At the moment,
> >the boss is complaining that his Windows Home Server is doing better
> >than this machine, and that's a technological direction I really don't
> >want to go in.
> >
> >Thanks,
> >==ml
> 

-- 
Michael W. Lucas
http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/
Latest book: Network Flow Analysis http://www.networkflowanalysis.com/
mwlu...@blackhelicopters.org, Twitter @mwlauthor
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: em0 NIC slow on 8.2-p1 amd64?

[Eduardo Morras]

At 18:04 20/07/2011, Michael W. Lucas wrote:

Hi,

I'm running FreeNAS 8.0/amd64, with an 8.2-p1 kernel.  When using FTP
or SCP, performance maxes out around 30MB/s. This is on a gigabit
network, no errors showing.

It looks a lot like kern/152828, but it seems that nobody's looking at
that.


Don't know about that, but perhaps the nic is not working at full gigabit.

Can you post the output of ifconfig?

#ifconfig em0

If it's not connected at 1 gigabit or not full duplex you can force 
it with ifconfig. If there are too much errors check the cable.



As per suggestions from the archives, I've tried disabling TSO. No
change.

Anyone else experiencing this, or have any suggestions? At the moment,
the boss is complaining that his Windows Home Server is doing better
than this machine, and that's a technological direction I really don't
want to go in.

Thanks,
==ml



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

em0 NIC slow on 8.2-p1 amd64?

[Michael W. Lucas]

Hi,

I'm running FreeNAS 8.0/amd64, with an 8.2-p1 kernel.  When using FTP
or SCP, performance maxes out around 30MB/s. This is on a gigabit
network, no errors showing. 

It looks a lot like kern/152828, but it seems that nobody's looking at
that.

As per suggestions from the archives, I've tried disabling TSO. No
change.

Anyone else experiencing this, or have any suggestions? At the moment,
the boss is complaining that his Windows Home Server is doing better
than this machine, and that's a technological direction I really don't
want to go in.

Thanks,
==ml

-- 
Michael W. Lucas
http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/
Latest book: Network Flow Analysis http://www.networkflowanalysis.com/
mwlu...@blackhelicopters.org, Twitter @mwlauthor
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Question about NIC link state initialization

[perryh]

Steve Polyack  wrote:

> I was able to "fix" the single-user mode behavior (which I agree,
> isn't necessarily broken) and get it to bring up the links by
> simply patching init(8) to call system("/sbin/ifconfig") before
> prompting for the single-user shell.  It works, but I feel dirty.

I see no particular objection to adding a way of running "something"
ahead of the single-user shell, but system(3) is not necessarily the
best mechanism to use for the purpose because it invokes a shell.
It would be both more efficient and more robust to call fork(2) and
exec(3) (or execve(2)) directly.

It would be more general to fork/exec "/etc/rc.single" instead of
"/sbin/ifconfig", expecting "/etc/rc.single" to be an executable
script (with an appropriate shebang line) and ignoring the failure
which would occur if it did not exist.  (In your case, instead of
a script, you could make /etc/rc.single a link to /sbin/ifconfig.)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Question about NIC link state initialization

[Steve Polyack]

On 6/30/2011 1:10 AM, per...@pluto.rain.com wrote:

Steve Polyack  wrote:


... An occaisional fat-finger in /etc/fstab may cause one to
end up in single-user mode ... some of these systems have a LOM
(lights-out management) controller which shares the system's
on-board NICs ... when the system drops out of init(8) and into
single-user mode, the links on the interfaces never come up,
and therefore the LOM becomes inaccessible.

... all one has to do is run ifconfig to cause the NIC's links to
come up ... why do we have to run ifconfig(8) to bring the links
up on the attached interfaces?

When trying to troubleshoot a problem that was known or suspected to
involve the network or its hardware, one might not _want_ the NICs
alive.


Short of patching init(8) (or perhaps the NIC drivers?), I don't
see another way for me to ensure the links come up even when the
system drops into single-user mode on boot.

Something in /root/.profile, perhaps?  That should get run when the
single-user shell starts up, if it's started as a "login" shell.

This won't work.  When the system kicks you into single-user mode, you 
are prompted to enter the name of a shell or press enter for /bin/sh.  
If no one is there to press enter, or enter the path to an alternate 
shell, then a shell never starts.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Question about NIC link state initialization

[Steve Polyack]

On 6/30/2011 6:49 AM, Daniel Feenberg wrote:



On Wed, 29 Jun 2011, per...@pluto.rain.com wrote:


Steve Polyack  wrote:


... An occaisional fat-finger in /etc/fstab may cause one to
end up in single-user mode ... some of these systems have a LOM
(lights-out management) controller which shares the system's
on-board NICs ... when the system drops out of init(8) and into
single-user mode, the links on the interfaces never come up,
and therefore the LOM becomes inaccessible.

... all one has to do is run ifconfig to cause the NIC's links to
come up ... why do we have to run ifconfig(8) to bring the links
up on the attached interfaces?


When trying to troubleshoot a problem that was known or suspected to
involve the network or its hardware, one might not _want_ the NICs


Well, maybe, but if the system needs to boot into multi-user mode for 
the LOM to be available, what is the need for the LOM? At that point 
you can do everything you might need through the OS interface. Can I 
ask what is the brand of this so-called LOM? Is there any 
documentation implying something more useful? Do they describe doing a 
bare metal install of an

OS?


They are the Dell Remote Access Controllers (DRACs).  Now, they do have 
their own dedicated NIC, which we use for anything that really needs the 
attention.  However, the shared feature saves us a switchport per server 
we use it on.  When both on-board NICs are cabled (i.e. for lagg(4) 
failover), then the DRAC's shared NIC mode *also* supports automatic 
failover between both on-board NICs.  This doesn't help however if the 
operating system never turns on the links to either on-board NIC.


I was able to "fix" the single-user mode behavior (which I agree, isn't 
necessarily broken) and get it to bring up the links by simply patching 
init(8) to call system("/sbin/ifconfig") before prompting for the 
single-user shell.  It works, but I feel dirty.


- Steve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Question about NIC link state initialization

[Daniel Feenberg]

On Wed, 29 Jun 2011, per...@pluto.rain.com wrote:


Steve Polyack  wrote:


... An occaisional fat-finger in /etc/fstab may cause one to
end up in single-user mode ... some of these systems have a LOM
(lights-out management) controller which shares the system's
on-board NICs ... when the system drops out of init(8) and into
single-user mode, the links on the interfaces never come up,
and therefore the LOM becomes inaccessible.

... all one has to do is run ifconfig to cause the NIC's links to
come up ... why do we have to run ifconfig(8) to bring the links
up on the attached interfaces?


When trying to troubleshoot a problem that was known or suspected to
involve the network or its hardware, one might not _want_ the NICs


Well, maybe, but if the system needs to boot into multi-user mode for the 
LOM to be available, what is the need for the LOM? At that point you can 
do everything you might need through the OS interface. Can I ask what is 
the brand of this so-called LOM? Is there any documentation implying 
something more useful? Do they describe doing a bare metal install of an

OS?

Daniel Feenberg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Question about NIC link state initialization

[perryh]

Steve Polyack  wrote:

> ... An occaisional fat-finger in /etc/fstab may cause one to
> end up in single-user mode ... some of these systems have a LOM
> (lights-out management) controller which shares the system's
> on-board NICs ... when the system drops out of init(8) and into
> single-user mode, the links on the interfaces never come up,
> and therefore the LOM becomes inaccessible.
>
> ... all one has to do is run ifconfig to cause the NIC's links to
> come up ... why do we have to run ifconfig(8) to bring the links
> up on the attached interfaces?

When trying to troubleshoot a problem that was known or suspected to
involve the network or its hardware, one might not _want_ the NICs
alive.

> Short of patching init(8) (or perhaps the NIC drivers?), I don't
> see another way for me to ensure the links come up even when the
> system drops into single-user mode on boot.

Something in /root/.profile, perhaps?  That should get run when the
single-user shell starts up, if it's started as a "login" shell.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Question about NIC link state initialization

[Steve Polyack]

I have a handful of systems running FreeBSD 8.1-RELEASE.  An occaisional 
fat-finger in /etc/fstab may cause one to end up in single-user mode 
from time to time.  This would normally not be a problem, but some of 
these systems have a LOM (lights-out management) controller which shares 
the system's on-board NICs.  This works great 99% of the time, but when 
the system drops out of init(8) and into single-user mode, the links on 
the interfaces never come up, and therefore the LOM becomes 
inaccessible.  Cue remote-hands at the facility to help us remedy the 
problem.


I've been playing around with this configuration on a local system, and 
I've noticed that once at a single-user shell, all one has to do is run 
ifconfig to cause the NIC's links to come up.  You don't even have to 
specify the interface, nor do you have to specify "up".  As soon as I 
hit enter, ifconfig prints the typical interface summary - intermingled 
in with this are the bold kernel log messages stating "bce0: link state 
changed to UP" and "bce1: link state changed to UP".


So, my question is - why do we have to run ifconfig(8) to bring the 
links up on the attached interfaces?  Shouldn't they come up after the 
driver discovers and initializes the devices?  Keep in mind that I don't 
even have to pass any arguments (such as "up") to ifconfig.  
Furthermore, the behavior is exactly the same for bce(4) and em(4).


Short of patching init(8) (or perhaps the NIC drivers?), I don't see 
another way for me to ensure the links come up even when the system 
drops into single-user mode on boot.


- Steve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FBSD support for Intel mini-itx board w. realtek 8111D nic

[Warren Block]

On Fri, 1 Apr 2011, Erik Nørgaard wrote:

I'm looking at the D945GSEJT which has a realtek 8111DL nic. Which driver is 
used for this nic?


re(4).  Some forum users have had recent problems with certain versions 
(maybe newer) of the 8111.  My older 8111C onboard versions have always 
worked fine.___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

FBSD support for Intel mini-itx board w. realtek 8111D nic

[Erik Nørgaard]

Hi:

I've got a fanless via based mini-itx box as my gateway and server and 
looking to upgrade to a Intel Atom based box. I believe it's supported 
out of the box. Now, I don't have an extra monitor, basically I'm gonna 
take the old disk, plug it in and hope it will boot (FBSD81, GENERIC 
kernel). So,


I'm looking at the D945GSEJT which has a realtek 8111DL nic. Which 
driver is used for this nic?


Well, basically I need to preconfigure the network so I can connect 
if/when it gets up.


Thanks, Erik
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Ascertaining NIC Driver Version

[Chuck Swiger]

On Jan 7, 2011, at 11:12 AM, Robert Huff wrote:
>> "uname -a" is probably the most general answer, as most FreeBSD
>> NIC drivers don't have individualized version #s, aside from the
>> OS version itself.
> 
>   That is not my understanding.
>   To the OP: FreeBSD NIC drivers can and do have version numbers:
> 
> huff@>> grep \$FreeBSD /sys/dev/e1000/if_em.c
> /*$FreeBSD: src/sys/dev/e1000/if_em.c,v 1.64 2010/12/04 06:38:21 jfv Exp $*/

Um, that's the CVS revision number for that particular file.

It should be obvious that it has nothing whatsoever to do with a human-assigned 
driver version #, if one even exists, such as em "v6.9.21" for:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=839&DwnldID=17509&ProductFamily=Network+Connectivity&ProductLine=Intel%C2%AE+Server+Adapters&ProductProduct=Intel%C2%AE+PRO%2f1000+F+Server+Adaptereng

Regards,
-- 
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Ascertaining NIC Driver Version

[Robert Huff]

Chuck Swiger writes:

>  > Is there a command line utility, a la ethtool or the like, that
>  >  can be used to query the NIC driver version? 
>  
>  "uname -a" is probably the most general answer, as most FreeBSD
>  NIC drivers don't have individualized version #s, aside from the
>  OS version itself.

That is not my understanding.
To the OP: FreeBSD NIC drivers can and do have version numbers:

huff@>> grep \$FreeBSD /sys/dev/e1000/if_em.c
/*$FreeBSD: src/sys/dev/e1000/if_em.c,v 1.64 2010/12/04 06:38:21 jfv Exp $*/

The system in question:

FreeBSD 9.0-CURRENT #0: Sat Oct 23 08:15:53 EDT 2010 amd64 

Obviously, the driver and OS version have nothing to do with
each other.  And the FreeBSD driver version will probably have
nothing to do with any other driver version, especially one provided
by the manufacturer.


Robert Huff

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Re: Ascertaining NIC Driver Version

[vrwmiller]

Thanks, Chuck! I Googled for an answer for a while and didn't find much. I  
did find that the particular driver I was interested did have a version  
number in the source, but the question actually came from a user who  
doesn't have source trees on their hosts.


On Jan 7, 2011 1:45pm, Chuck Swiger  wrote:

On Jan 7, 2011, at 10:33 AM, vrwmil...@gmail.com wrote:


> Is there a command line utility, a la ethtool or the like, that can be  
used to query the NIC driver version?




"uname -a" is probably the most general answer, as most FreeBSD NIC  
drivers don't have individualized version #s, aside from the OS version  
itself.




The sysctl tree under dev for a particular device, ie, "sysctl  
dev.bce", "sysctl dev.em", etc will return more information which might  
include a vendor-specific driver version #...





Regards,



--



-Chuck




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Ascertaining NIC Driver Version

[Chuck Swiger]

On Jan 7, 2011, at 10:33 AM, vrwmil...@gmail.com wrote:
> Is there a command line utility, a la ethtool or the like, that can be used 
> to query the NIC driver version?

"uname -a" is probably the most general answer, as most FreeBSD NIC drivers 
don't have individualized version #s, aside from the OS version itself.

The sysctl tree under dev for a particular device, ie, "sysctl dev.bce", 
"sysctl dev.em", etc will return more information which might include a 
vendor-specific driver version #...

Regards,
-- 
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Ascertaining NIC Driver Version

[vrwmiller]

HI All,

Is there a command line utility, a la ethtool or the like, that can be used  
to query the NIC driver version?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Gary Kline]

On Thu, Nov 25, 2010 at 07:16:01PM +, Arthur Chance wrote:
> On 11/25/10 18:22, Gary Kline wrote:
> [Huge snip]

Super :-)

> > What I don't understand is the CF card and howto install
> > pfSense.  I'll re-read wherever I have to but some clues would
> > certainly help.  I installed pfSense by CDROM initially and
> > figure this time the install would be done by thumb-drive.
> > [?]
> >
> > Pointers, URLs welcome!
> 
> If you're installing onto a CF card you want the "embedded" version.
> You download the version that matches the size of your CF card -
> there are 512M, 1G, 2G and 4G versions. I went for 4G because I had
> a convenient card lying around, but it's overkill. You decompress it
> and simply dd it onto the card (presuming you've got a normal Unix
> box). This link will help


I just took a second look at what I have coming in my ALIX.6E1
Kit.  (Also found that 'CF' == Compact Flash; we've got enough 
abbrvs, all right.  )  At any rate, here is what is in my 6e1
kit:

* ALIX.6E1 system board (2/1/1/256/LX800)
* Laser etched black aluminum enclosure with USB and antenna cutouts
* Blank 2 GB Sandisk Ultra II CF Card
* Standard 15V 1.25A 18W power supply (US plug style)
* Ships unassembled

If your 4G CF card was overkill, will my 2GB card be enough?  If
not I'll order a slave chip; or maybe a 4G flash card.

Pasted immediately below is what I was pointed last last night. 
There were links like your URLs to the pfSense site.  Hm.  I
have more research to do (looks like) to learn enough to 
__know__ was I'm doing.  Or my friend and I.  But then I've had
pfSense going for about three years on severely antique
hardware, no problem.  

http://store.netgate.com/ALIX6E1-Kit-Black-Unassembled-P183.aspx
> 
> http://doc.pfsense.org/index.php/Installing_pfSense
> 
> This is the embedded category page on the doc wiki
> 
> http://doc.pfsense.org/index.php/Category:Embedded
> 
> Then all you do is insert the card into the CF adapter on the Alix
> board, fire it up and point your web browser at it to do the initial
> set up. (Don't forget to change the serial line speed to 9600
> beforehand.) The initial address is 192.168.1.1, username/password
> are admin/pfsense. Have fun.

Last question[s]: is there a toggle somewhere to change the
speed to 9600?  When a friend helped save my network in JAn,
2008, we did it all my chat and maybe one phone call, so my
memories of the details of getting pfSense set up the first time
have faded ... .  I have a 10.* internal network!  Oboy.  Well, 
here's hoping that a few FreeBSD types are around on 15th dec.

FWIW, My chat is gdk98188 [at] yahoo  

gary

PS: before my almost-disaster in 12/07 I used ifp and ifpw for
years.  The server also handled DHCP.  THe reason I went with 
pfsense was to offload that stuff "somewhere else"; it seems 
apropos of the Unix philosophy: simplicity is better.


> 
> -- 
> "Although the wombat is real and the dragon is not, few know what a
> wombat looks like, but everyone knows what a dragon looks like."
> 
>   -- Avram Davidson, _Adventures in Unhistory_

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Arthur Chance]

On 11/25/10 18:22, Gary Kline wrote:
[Huge snip]

What I don't understand is the CF card and howto install
pfSense.  I'll re-read wherever I have to but some clues would
certainly help.  I installed pfSense by CDROM initially and
figure this time the install would be done by thumb-drive.
[?]

Pointers, URLs welcome!


If you're installing onto a CF card you want the "embedded" version. You 
download the version that matches the size of your CF card - there are 
512M, 1G, 2G and 4G versions. I went for 4G because I had a convenient 
card lying around, but it's overkill. You decompress it and simply dd it 
onto the card (presuming you've got a normal Unix box). This link will help


http://doc.pfsense.org/index.php/Installing_pfSense

This is the embedded category page on the doc wiki

http://doc.pfsense.org/index.php/Category:Embedded

Then all you do is insert the card into the CF adapter on the Alix 
board, fire it up and point your web browser at it to do the initial set 
up. (Don't forget to change the serial line speed to 9600 beforehand.) 
The initial address is 192.168.1.1, username/password are admin/pfsense. 
Have fun.


--
"Although the wombat is real and the dragon is not, few know what a
wombat looks like, but everyone knows what a dragon looks like."

-- Avram Davidson, _Adventures in Unhistory_
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Gary Kline]

On Thu, Nov 25, 2010 at 12:48:47PM +, Arthur Chance wrote:
> On 11/25/10 03:01, Gary Kline wrote:
> >Folks (mostly Adam),
> >
> >Hang on a sec.  I think I misread what my friend said.
> >Following is a snip of what he said was good; that this was among
> >the stuff he installed a few years back and now was much better::
> >
> >
> >>ALIX.2D13 system board - $115
> >>CompactFlash card 4GB SLC - $20
> >>Enclosure - $9
> >>AC adapter - $13
> >
> >
> >Is this the same board and so forth that Arthur pointed me at below?
> >My friend's name is Noah; what he saw was that the boad was not in
> >stock and that it would not be restocked until 20dec.   Because the
> >15th is better for Noah to drive down, I would like to have the
> >stuff here when it's best for him.   Figure ther have to be other
> >vendors that sell this.
> 
> OK, I'm in the UK as are these people I buy from, but they do prices
> in dollars as well as pounds and euros, and will ship to the US.
> They don't have a 2d13 at the moment but do have 2d3s in stock (the
> 2d13 has a battery and RTC extra, that's all).
> 
> http://linitx.com/index.php
> 
> They've got enclosures, but the power supplies are european plugs.
> However, they are universal (100-250V), so an EU->US adapter would
> work. I use a SanDisk CF card in mine, and the pfSense install
> worked like a dream. The only wrinkle is remembering to change the
> serial line speed from 19200 to 9600 baud before installing pfSense,
> as the serial bootloader likes 9600.
> 
> I'd recommend getting "pfSense: The Definite Guide" as well
> 
> http://www.amazon.com/pfSense-Definitive-Christopher-M-Buechler/dp/0979034280/ref=sr_1_1/177-9101540-7293707?ie=UTF8&s=books&qid=1290689178&sr=1-1
> 


I _will_ order the Guide since I rely on pfSense ...  

What I ordered last night was the "6e1". The pcengines.com site
pointed me to a netgate website here in the States.  So: the
entire kit is enroute; or will be soon.

What I don't understand is the CF card and howto install
pfSense.  I'll re-read wherever I have to but some clues would 
certainly help.  I installed pfSense by CDROM initially and
figure this time the install would be done by thumb-drive.
[?]

Pointers, URLs welcome!

gary


> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Arthur Chance]

On 11/25/10 03:01, Gary Kline wrote:

Folks (mostly Adam),

Hang on a sec.  I think I misread what my friend said.
Following is a snip of what he said was good; that this was among
the stuff he installed a few years back and now was much better::



ALIX.2D13 system board - $115
CompactFlash card 4GB SLC - $20
Enclosure - $9
AC adapter - $13



Is this the same board and so forth that Arthur pointed me at below?
My friend's name is Noah; what he saw was that the boad was not in
stock and that it would not be restocked until 20dec.   Because the
15th is better for Noah to drive down, I would like to have the
stuff here when it's best for him.   Figure ther have to be other
vendors that sell this.


OK, I'm in the UK as are these people I buy from, but they do prices in 
dollars as well as pounds and euros, and will ship to the US. They don't 
have a 2d13 at the moment but do have 2d3s in stock (the 2d13 has a 
battery and RTC extra, that's all).


http://linitx.com/index.php

They've got enclosures, but the power supplies are european plugs. 
However, they are universal (100-250V), so an EU->US adapter would work. 
I use a SanDisk CF card in mine, and the pfSense install worked like a 
dream. The only wrinkle is remembering to change the serial line speed 
from 19200 to 9600 baud before installing pfSense, as the serial 
bootloader likes 9600.


I'd recommend getting "pfSense: The Definite Guide" as well

http://www.amazon.com/pfSense-Definitive-Christopher-M-Buechler/dp/0979034280/ref=sr_1_1/177-9101540-7293707?ie=UTF8&s=books&qid=1290689178&sr=1-1

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Gary Kline]

On Wed, Nov 24, 2010 at 09:45:41PM -0600, Adam Vande More wrote:
> On Wed, Nov 24, 2010 at 9:01 PM, Gary Kline  wrote:
> 
> > Folks (mostly Adam),
> >
> > Hang on a sec.  I think I misread what my friend said.
> > Following is a snip of what he said was good; that this was among
> > the stuff he installed a few years back and now was much better::
> >
> >
> > > ALIX.2D13 system board - $115
> > > CompactFlash card 4GB SLC - $20
> > > Enclosure - $9
> > > AC adapter - $13
> >
> >
> > Is this the same board and so forth that Arthur pointed me at below?
> > My friend's name is Noah; what he saw was that the boad was not in
> > stock and that it would not be restocked until 20dec.   Because the
> > 15th is better for Noah to drive down, I would like to have the
> > stuff here when it's best for him.   Figure ther have to be other
> > vendors that sell this.
> >
> 
> Yes, but if you browse the manufacturer you'll see that there are other
> boards in-stock which meet your requirements like this one:
> 
> http://www.pcengines.ch/alix6e1.htm
> 
> Doesn't have battery but that's easy enough to address around and less to go
> wrong.


all right.  the thing is that here i don't know the requirments.
if "6e1" is better, that good.

> 
> -- 
> Adam Vande More

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Matt Emmerton]

Maybe someone on-list can help me; after 5+ hours of clicking and
typing, I can't find an atom cpu computer with dual NICs.  I
_thought_ I'd found a computer to replace to Kayak firewall
[pfSense], but nada.

Any wizards on this list have a clue?


You'd probably have to build one yourself out of parts.  Any respectable 
computer shop will have Mini-ITX Atom motherboards and cases, just add 
another NIC to that along with memory/drives and you're done.


Regards,
--
Matt Emmerton 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Adam Vande More]

On Wed, Nov 24, 2010 at 9:01 PM, Gary Kline  wrote:

> Folks (mostly Adam),
>
> Hang on a sec.  I think I misread what my friend said.
> Following is a snip of what he said was good; that this was among
> the stuff he installed a few years back and now was much better::
>
>
> > ALIX.2D13 system board - $115
> > CompactFlash card 4GB SLC - $20
> > Enclosure - $9
> > AC adapter - $13
>
>
> Is this the same board and so forth that Arthur pointed me at below?
> My friend's name is Noah; what he saw was that the boad was not in
> stock and that it would not be restocked until 20dec.   Because the
> 15th is better for Noah to drive down, I would like to have the
> stuff here when it's best for him.   Figure ther have to be other
> vendors that sell this.
>

Yes, but if you browse the manufacturer you'll see that there are other
boards in-stock which meet your requirements like this one:

http://www.pcengines.ch/alix6e1.htm

Doesn't have battery but that's easy enough to address around and less to go
wrong.

-- 
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Gary Kline]

Folks (mostly Adam),

Hang on a sec.  I think I misread what my friend said.
Following is a snip of what he said was good; that this was among
the stuff he installed a few years back and now was much better::

  
> ALIX.2D13 system board - $115 
> CompactFlash card 4GB SLC - $20   
> Enclosure - $9
> AC adapter - $13  


Is this the same board and so forth that Arthur pointed me at below?
My friend's name is Noah; what he saw was that the boad was not in
stock and that it would not be restocked until 20dec.   Because the 
15th is better for Noah to drive down, I would like to have the
stuff here when it's best for him.   Figure ther have to be other
vendors that sell this.

gary



On Wed, Nov 24, 2010 at 04:03:56PM +, Arthur Chance wrote:
> On 11/24/10 01:43, Gary Kline wrote:
> >Maybe someone on-list can help me; after 5+ hours of clicking and
> >typing, I can't find an atom cpu computer with dual NICs.  I
> >_thought_ I'd found a computer to replace to Kayak firewall
> >[pfSense], but nada.
> >
> >Any wizards on this list have a clue?
> 
> I don't know if your requirement for an Atom CPU is absolute, or
> you're just looking for a low power solution, but if it's the latter
> and 100Mb/s networking is fast enough, I use one of these
> 
> http://www.pcengines.ch/alix2d13.htm
> 
> for my pfSense firewall. Three network interfaces so you have a DMZ,
> plus a hardware crypto accelerator for VPNs. Total power consumption
> measured at 5W. The alix2d2 is the 2 network port version.
> 
> -- 
> "Although the wombat is real and the dragon is not, few know what a
> wombat looks like, but everyone knows what a dragon looks like."
> 
>   -- Avram Davidson, _Adventures in Unhistory_

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Gary Kline]

On Wed, Nov 24, 2010 at 08:14:01PM -0600, Adam Vande More wrote:
> On Wed, Nov 24, 2010 at 7:20 PM, Gary Kline  wrote:
> 
> >Anybody?
> >
> 
> Gary, in case you didn't catch it the pcengines link already given to you is
> low power setup with comsumption comparable or better than an Atom.  It's
> also been tested with FreeBSD and pfSense according to the manufacturers
> site.  There's nothing wrong with Atom, but different models have different
> chipsets/NIC's and there may be a possibility of unsupported hardware.
> Perhaps it might be easier for you to go with a known commodity.
> 
> pfSense documentation is offered on their website as well as community
> support.  I suggest you start there.
> 


Thanks Adam,

I forwarded the other model to my friend at the U and didn't
hear back.  --Of course, for lots of the civilian class, it is
almost T'giving :-)  Good thing there is ~three weeks left... .

gary


> -- 
> Adam Vande More
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Adam Vande More]

On Wed, Nov 24, 2010 at 7:20 PM, Gary Kline  wrote:

>Anybody?
>

Gary, in case you didn't catch it the pcengines link already given to you is
low power setup with comsumption comparable or better than an Atom.  It's
also been tested with FreeBSD and pfSense according to the manufacturers
site.  There's nothing wrong with Atom, but different models have different
chipsets/NIC's and there may be a possibility of unsupported hardware.
Perhaps it might be easier for you to go with a known commodity.

pfSense documentation is offered on their website as well as community
support.  I suggest you start there.

-- 
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Gary Kline]

On Wed, Nov 24, 2010 at 02:23:33PM +0100, Goran Lowkrantz wrote:
> --On November 23, 2010 17:43:12 -0800 Gary Kline  wrote:
> 
> >Maybe someone on-list can help me; after 5+ hours of clicking and
> >typing, I can't find an atom cpu computer with dual NICs.  I
> >_thought_ I'd found a computer to replace to Kayak firewall
> >[pfSense], but nada.
> >
> >Any wizards on this list have a clue?
> >
> >--
> > Gary Kline  kl...@thought.org  http://www.thought.org  Public Service
> >UnixJourney Toward the Dawn, E-Book: http://www.thought.org
> >The 7.97a release of Jottings: http://jottings.thought.org
> >
> 
> I run pfSense on this
> 
> in this
> 
> 
> - glz


Well, it looks like this one is it; it has the enclosure and so
on with take more assembly that I myself can do, but not a
fellow computer geek.  Since I'm doing this as-if from scratch,
what's the best way of getting pfSense installed?  Can I do it
somehow over the wire or use a thumb drive?  

What I understand is that the board won't be in stock until Dec
20th and I need it by the 15th, so  should I just google around?
(I'm imagine all the tens of millions of peiople who are
shopping for a board that runs a firewall integrated with 
FrreeBSD:-)

Anybody?



-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Christer Solskogen]

On Wed, Nov 24, 2010 at 2:43 AM, Gary Kline  wrote:
> Maybe someone on-list can help me; after 5+ hours of clicking and
> typing, I can't find an atom cpu computer with dual NICs.  I
> _thought_ I'd found a computer to replace to Kayak firewall
> [pfSense], but nada.
>
> Any wizards on this list have a clue?

I don't know if I'm a wizard, but FitPC2i might do you good.

http://www.fit-pc.com/web/fit-pc2/specifications/


-- 
chs,
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Gary Kline]

On Wed, Nov 24, 2010 at 04:03:56PM +, Arthur Chance wrote:
> On 11/24/10 01:43, Gary Kline wrote:
> >Maybe someone on-list can help me; after 5+ hours of clicking and
> >typing, I can't find an atom cpu computer with dual NICs.  I
> >_thought_ I'd found a computer to replace to Kayak firewall
> >[pfSense], but nada.
> >
> >Any wizards on this list have a clue?
> 
> I don't know if your requirement for an Atom CPU is absolute, or
> you're just looking for a low power solution, but if it's the latter
> and 100Mb/s networking is fast enough, I use one of these
> 
> http://www.pcengines.ch/alix2d13.htm
> 
> for my pfSense firewall. Three network interfaces so you have a DMZ,
> plus a hardware crypto accelerator for VPNs. Total power consumption
> measured at 5W. The alix2d2 is the 2 network port version.
> 

Thanks to everyone indeed.  The long-story-short is that just a 
few months ago I thought I *had* found a low-power [Atom] box
with a dual-NIC for around $300.  So I figured that since there
was at least that one there might be others.  Late last night my 
friend at the University figured that it wouldn't be that hard
to build one from parts.  [[ Sure, if you've got two good hands
and a several hours, etc.   ]]

An Atom CPU is only the means to the end of finally having a low
power config.  Right now I'm probably burning 100w using the
Kayak and an '05 40G drive.  Any low-power box will work. 

Appreciate the help!

gary


> -- 
> "Although the wombat is real and the dragon is not, few know what a
> wombat looks like, but everyone knows what a dragon looks like."
> 
>   -- Avram Davidson, _Adventures in Unhistory_
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Arthur Chance]

On 11/24/10 01:43, Gary Kline wrote:

Maybe someone on-list can help me; after 5+ hours of clicking and
typing, I can't find an atom cpu computer with dual NICs.  I
_thought_ I'd found a computer to replace to Kayak firewall
[pfSense], but nada.

Any wizards on this list have a clue?


I don't know if your requirement for an Atom CPU is absolute, or you're 
just looking for a low power solution, but if it's the latter and 
100Mb/s networking is fast enough, I use one of these


http://www.pcengines.ch/alix2d13.htm

for my pfSense firewall. Three network interfaces so you have a DMZ, 
plus a hardware crypto accelerator for VPNs. Total power consumption 
measured at 5W. The alix2d2 is the 2 network port version.


--
"Although the wombat is real and the dragon is not, few know what a
wombat looks like, but everyone knows what a dragon looks like."

-- Avram Davidson, _Adventures in Unhistory_
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Goran Lowkrantz]

--On November 23, 2010 17:43:12 -0800 Gary Kline  wrote:


Maybe someone on-list can help me; after 5+ hours of clicking and
typing, I can't find an atom cpu computer with dual NICs.  I
_thought_ I'd found a computer to replace to Kayak firewall
[pfSense], but nada.

Any wizards on this list have a clue?

--
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service
UnixJourney Toward the Dawn, E-Book: http://www.thought.org
The 7.97a release of Jottings: http://jottings.thought.org



I run pfSense on this

in this


- glz
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Robert Huff]

Bruce Cran writes:

>  You also get network cards with multiple ports which would work. e.g.
>  
> http://reviews.cnet.com/adapters-nics/d-link-dfe-570tx/1707-3380_7-785663.html

The machine I'm typing on has a two port Intel Pro/1000-GT; I
cannot recommend it highly enough.
One caveat: the better multi-port cards can get expensive
very fast.


Robert Huff





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[Svein Skogen (Listmail account)]

On 24.11.2010 02:43, Gary Kline wrote:
> Maybe someone on-list can help me; after 5+ hours of clicking and
> typing, I can't find an atom cpu computer with dual NICs.  I
> _thought_ I'd found a computer to replace to Kayak firewall
> [pfSense], but nada.
> 
> Any wizards on this list have a clue?

http://global.msi.eu/index.php?func=proddesc&maincat_no=388&prod_no=1943

//Svein

-- 
+---+---
  /"\   |Svein Skogen   | sv...@d80.iso100.no
  \ /   |Solberg Østli 9| PGP Key:  0xE5E76831
   X|2020 Skedsmokorset | sv...@jernhuset.no
  / \   |Norway | PGP Key:  0xCE96CE13
|   | sv...@stillbilde.net
 ascii  |   | PGP Key:  0x58CD33B6
 ribbon |System Admin   | svein-listm...@stillbilde.net
Campaign|stillbilde.net | PGP Key:  0x22D494A4
+---+---
|msn messenger: | Mobile Phone: +47 907 03 575
|sv...@jernhuset.no | RIPE handle:SS16503-RIPE
+---+---
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

 Picture Gallery:
  https://gallery.stillbilde.net/v/svein/




signature.asc
Description: OpenPGP digital signature

Re: foo; no such thing as a "dual-nic" atom firewall

[Bruce Cran]

On Wed, 24 Nov 2010 01:26:53 -0800
per...@pluto.rain.com wrote:

> Dunno about having them on-board, but anything with a Poulsbo SCH
> should have two PCIe channels, each of which could be used for a
> NIC.

You also get network cards with multiple ports which would work. e.g.
http://reviews.cnet.com/adapters-nics/d-link-dfe-570tx/1707-3380_7-785663.html

-- 
Bruce Cran
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: foo; no such thing as a "dual-nic" atom firewall

[perryh]

Gary Kline  wrote:

> I can't find an atom cpu computer with dual NICs.

Dunno about having them on-board, but anything with a Poulsbo SCH
should have two PCIe channels, each of which could be used for a
NIC.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

foo; no such thing as a "dual-nic" atom firewall

[Gary Kline]

Maybe someone on-list can help me; after 5+ hours of clicking and
typing, I can't find an atom cpu computer with dual NICs.  I
_thought_ I'd found a computer to replace to Kayak firewall
[pfSense], but nada.

Any wizards on this list have a clue?

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.97a release of Jottings: http://jottings.thought.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Is support planned for Intel NIC I340-T4 (82580 ethernet chipset) ?

[Robert Huff]

Eduard Rozenberg writes:

>  I've checked the latest 8.1R hardware compatibility and don't see
>  the Intel 82580 ethernet chipset being supported. This is Intel's
>  latest ethernet chipset, released beginning of 2010 I think. Is
>  there support planned for this?

The person to ask would be Jack Vogel, who has posted to
various FreeBSD lists before.  Intel pays Jack to (among other
things) write our drivers, at which he does a very good job.


Robert Huff


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Is support planned for Intel NIC I340-T4 (82580 ethernet chipset) ?

[Eduard Rozenberg]

Hi,

I've checked the latest 8.1R hardware compatibility and don't see the Intel 
82580 ethernet chipset being supported. This is Intel's latest ethernet 
chipset, released beginning of 2010 I think. Is there support planned for this?

Thanks!
--Ed___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Need help troubleshooting NIC

[Mike Galvez]

On Mon, Feb 08, 2010 at 04:24:39PM -0600, Adam Vande More wrote:
> On Mon, Feb 8, 2010 at 1:19 PM, Mike Galvez  wrote:
> 
> > Over the weekend one my servers went down due to extended power failure.
> > The file system reports clean, but something has gone sideways with
> > networking. The server is a Dell 2950 running 7.0 release, and it's been
> > working fine for well over a year. It uses the BCE driver. Ifconfig
> > shows it to be up and active and configured with the correct IP, mask
> > and gateway, but I can't ping anything.
> >
> > I've tested the ethernet connection with a nearby machine and it works.
> > I also booted the 2950 from an Ubuntu live CD and the NIC worked, so i
> > don't think it's a hardware issue.
> >
> > Is there a way I can rebuild the driver without having to rebuild the
> > kernel?
> >
> 
> What does netstat -r show?
> 
> -- 
> Adam Vande More
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Adam,

Thanks for the reply. netstat -r shows a segfault before it finishes.
The machine is back online, but I beginning to think that maybe the nics
are flaky after all.

netstat -r
Routing tables

Internet:
DestinationGatewayFlagsRefs  Use  Netif
Expire
defaultcarruthers1-all-ro UGS 0   498375   bce0
localhost  localhost  UH  0  270lo0
128.143.87.0   link#1 UC  00   bce0
carruthers1-all-ro 00:d0:05:34:40:00  UHLW20   bce0 1197
Segmentation fault


-- 
Michael Galvez 
Information Technology Specialist University of Virginia
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Need help troubleshooting NIC

[Adam Vande More]

On Mon, Feb 8, 2010 at 1:19 PM, Mike Galvez  wrote:

> Over the weekend one my servers went down due to extended power failure.
> The file system reports clean, but something has gone sideways with
> networking. The server is a Dell 2950 running 7.0 release, and it's been
> working fine for well over a year. It uses the BCE driver. Ifconfig
> shows it to be up and active and configured with the correct IP, mask
> and gateway, but I can't ping anything.
>
> I've tested the ethernet connection with a nearby machine and it works.
> I also booted the 2950 from an Ubuntu live CD and the NIC worked, so i
> don't think it's a hardware issue.
>
> Is there a way I can rebuild the driver without having to rebuild the
> kernel?
>

What does netstat -r show?

-- 
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Need help troubleshooting NIC

[Mike Galvez]

Over the weekend one my servers went down due to extended power failure.
The file system reports clean, but something has gone sideways with
networking. The server is a Dell 2950 running 7.0 release, and it's been
working fine for well over a year. It uses the BCE driver. Ifconfig
shows it to be up and active and configured with the correct IP, mask
and gateway, but I can't ping anything. 

I've tested the ethernet connection with a nearby machine and it works.
I also booted the 2950 from an Ubuntu live CD and the NIC worked, so i
don't think it's a hardware issue.

Is there a way I can rebuild the driver without having to rebuild the
kernel?

-- 
Michael Galvez
Information Technology Specialist University of Virginia
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Inserting PC card NIC, system stops

[Fbsd1]

Hashimoto wrote:

Thanks for your reply, Paul.


$ uname -a
FreeBSD musca.localdomain 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0
r201741: Fri Jan  8 01:01:18 JST 2010
r...@aries.localdomain:/usr/obj/usr/src/sys/GENERIC  i386


$ tail /var/log/messages
Jan  9 21:29:12 musca kernel: cbb1: ready never happened, status = 00
Jan  9 21:29:12 musca kernel: ed0:  at port



ed(4) appears to be driver for that card


Sure.
I'm using GENERIC kernel,
and it includes cbb(4), ed(4) device driver.
But the system does not work fine with this PC card.



You are not clear just how you are inserting the nic card. Are you 
trying to insert the card while Freebsd is up and running or inserting 
the card while the pc is powered off and them during bootup post you get 
those msgs?


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Inserting PC card NIC, system stops

[Paul B Mahol]

On 1/10/10, Hashimoto  wrote:
> Thanks for your reply, Paul.
>
>>> $ uname -a
>>> FreeBSD musca.localdomain 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0
>>> r201741: Fri Jan  8 01:01:18 JST 2010
>>> r...@aries.localdomain:/usr/obj/usr/src/sys/GENERIC  i386
>>>
>>> 
>>> $ tail /var/log/messages
>>> Jan  9 21:29:12 musca kernel: cbb1: ready never happened, status = 00
>>> Jan  9 21:29:12 musca kernel: ed0:  at port
>
>> ed(4) appears to be driver for that card
>
> Sure.
> I'm using GENERIC kernel,
> and it includes cbb(4), ed(4) device driver.
> But the system does not work fine with this PC card.

Then it could be bug in hardware(and in FreeBSD because it should
not hang) or id ed(4) or in anything else, so report is as a bug.

-- 
Paul B Mahol
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Inserting PC card NIC, system stops

[Hashimoto]

Thanks for your reply, Paul.

>> $ uname -a
>> FreeBSD musca.localdomain 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0
>> r201741: Fri Jan  8 01:01:18 JST 2010
>> r...@aries.localdomain:/usr/obj/usr/src/sys/GENERIC  i386
>>
>> 
>> $ tail /var/log/messages
>> Jan  9 21:29:12 musca kernel: cbb1: ready never happened, status = 00
>> Jan  9 21:29:12 musca kernel: ed0:  at port

> ed(4) appears to be driver for that card

Sure.
I'm using GENERIC kernel,
and it includes cbb(4), ed(4) device driver.
But the system does not work fine with this PC card.

-- 
橋本紘希
hsm...@gmail.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Inserting PC card NIC, system stops

[Paul B Mahol]

On 1/9/10, Hashimoto  wrote:
> Hello.
> I have a problem with a PC card Ethernet interface.
>
> When I insert the PC card to my laptop,
> the system hungs and makes no response.
> When I eject the card,
> the system starts again and works fine.
> (working
>  -> insert the card
>  stopping
>  -> eject the card
>  working)
>
> Of course, I cannot use this card for network interface.
> (ifconfig command does not show this interface.)
> Are there some workarounds to work this card correctly?
> Regards.
>
> 
> Corega CG-LAPCCTXD
>
> $ uname -a
> FreeBSD musca.localdomain 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0
> r201741: Fri Jan  8 01:01:18 JST 2010
> r...@aries.localdomain:/usr/obj/usr/src/sys/GENERIC  i386
>
> 
> $ tail /var/log/messages
> Jan  9 21:29:12 musca kernel: cbb1: ready never happened, status = 00
> Jan  9 21:29:12 musca kernel: ed0:  at port

ed(4) appears to be driver for that card

-- 
Paul B Mahol
aaa
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Inserting PC card NIC, system stops

[Hashimoto]

Hello.
I have a problem with a PC card Ethernet interface.

When I insert the PC card to my laptop,
the system hungs and makes no response.
When I eject the card,
the system starts again and works fine.
(working
 -> insert the card
 stopping
 -> eject the card
 working)

Of course, I cannot use this card for network interface.
(ifconfig command does not show this interface.)
Are there some workarounds to work this card correctly?
Regards.


Corega CG-LAPCCTXD

$ uname -a
FreeBSD musca.localdomain 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0
r201741: Fri Jan  8 01:01:18 JST 2010
r...@aries.localdomain:/usr/obj/usr/src/sys/GENERIC  i386


$ tail /var/log/messages
Jan  9 21:29:12 musca kernel: cbb1: ready never happened, status = 00
Jan  9 21:29:12 musca kernel: ed0:  at port
0x100-0x11f irq 11 function 0 config 32 on pccard1
Jan  9 21:29:12 musca kernel: Novell probe generic 6
Jan  9 21:29:12 musca kernel: device_attach: ed0 attach returned 6

$ dmesg
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-RELEASE-p2 #0 r201741: Fri Jan  8 01:01:18 JST 2010
r...@aries.localdomain:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Mobile AMD Duron(tm) Processor (847.43-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x670  Stepping = 0
  
Features=0x383f9ff
  AMD Features=0xc0440800,MMX+,3DNow!+,3DNow!>
real memory  = 134217728 (128 MB)
avail memory = 17936 (95 MB)
kbd1 at kbdmux0
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_ec0:  port 0x62,0x66 on acpi0
acpi_button0:  on acpi0
acpi_lid0:  on acpi0
acpi_acad0:  on acpi0
battery0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci_link2: BIOS IRQ 11 for 0.11.INTA is invalid
pci0:  on pcib0
agp0:  on hostb0
agp0: aperture size is 256M
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
vgapci0:  mem
0xe000-0xe007,0x9000-0x97ff irq 10 at device 0.0 on
pci1
cbb0:  at device 8.0 on pci0
cardbus0:  on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb0: [FILTER]
cbb1:  at device 8.1 on pci0
cardbus1:  on cbb1
pccard1: <16-bit PCCard bus> on cbb1
cbb1: [FILTER]
fwohci0:  mem 0xf0001000-0xf0001fff irq 5 at device 11.0 on pci0
fwohci0: [ITHREAD]
fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:40:d0:01:00:01:be:36
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 1024 bytes.
fwohci0: max_rec 1024 -> 2048
firewire0:  on fwohci0
dcons_crom0:  on firewire0
dcons_crom0: bus_addr 0x10a4000
fwe0:  on firewire0
if_fwe0: Fake Ethernet address: 02:40:d0:01:be:36
fwe0: Ethernet address: 02:40:d0:01:be:36
fwip0:  on firewire0
fwip0: Firewire address: 00:40:d0:01:00:01:be:36 @ 0xfffe,
S400, maxrec 2048
fwohci0: Initiate bus reset
fwohci0: fwohci_intr_core: BUS reset
fwohci0: fwohci_intr_core: node_id=0x, SelfID Count=1, CYCLEMASTER mode
isab0:  at device 17.0 on pci0
isa0:  on isab0
atapci0:  port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1100-0x110f at device 17.1 on
pci0
atapci0: Correcting VIA config for southbridge data corruption bug
ata0:  on atapci0
ata0: [ITHREAD]
ata1:  on atapci0
ata1: [ITHREAD]
uhci0:  port 0x1200-0x121f irq 10 at device
17.2 on pci0
uhci0: [ITHREAD]
uhci0: LegSup = 0x8030
usbus0:  on uhci0
uhci1:  port 0x1300-0x131f irq 10 at device
17.3 on pci0
uhci1: [ITHREAD]
uhci1: LegSup = 0xa030
usbus1:  on uhci1
pci0:  at device 17.4 (no driver attached)
pci0:  at device 17.5 (no driver attached)
pci0:  at device 17.6 (no driver attached)
vr0:  port 0xe800-0xe8ff mem
0xf000-0xf0ff irq 10 at device 18.0 on pci0
vr0: Quirks: 0x0
vr0: Revision: 0x51
miibus0:  on vr0
smcphy0:  PHY 1 on miibus0
smcphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: Ethernet address: 00:40:d0:1d:3d:83
vr0: [ITHREAD]
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0:  irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model GlidePoint, device ID 0
atrtc0:  port 0x70-0x75 irq 8 on acpi0
fdc0:  port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0:  port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppc0: [ITHREAD]
ppbus0:  on ppc0
plip0:  on ppbus0
plip0: [ITHREAD]
lpt0:  on ppbus0
lpt0: [ITHREAD]
lpt0: Interrupt-driven port
ppi0:  on ppbus0
cpu0:  on acpi0
powernow0:  on cpu0
pmtimer0 on isa0
orm0:  at iomem
0xc-0xcbfff,0xe-0xe0fff,0xe6000-0xe6fff,0xeb000-0xe pnpid
ORM on isa0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb o

How to get NIC status?

[Peter Steele]

Assuming I have the name of an interface, what's the easiest way 
programmatically to get the status of the interface?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

NIC Support

[Jack Barnett]

Is the RealTek RTL8112L PCIe gigabit LAN Controller support in FreeBSD 7.2?
I could not find this in the hardware notes.  Is it listed under another 
name?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: IPF, NAT or NIC

[Freeco]

Freeco wrote:
> 
> Maybe i made some cabling loop, becauce my internet stoped to work. In the
> beginning everything was ok, but after some time when all 3 pc's who was
> connected to switch it stopped to work. Why?
> 

-- 
View this message in context: 
http://www.nabble.com/IPF%2C-NAT-or-NIC-tp25491958p25521566.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: IPF, NAT or NIC

[Freeco]

I suspect that you've created a cabling loop of some sort again.
Maybe i made some cabling loop, becauce my internet stoped to work. In the
beginning everything was ok, but after some time when all 3 pc's was
connected to switch it stopped to work. Why?
-- 
View this message in context: 
http://www.nabble.com/IPF%2C-NAT-or-NIC-tp25491958p25520353.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: IPF, NAT or NIC

[Steve Bertrand]

Freeco wrote:
> My gateway gave me a message: "gateway kernel: arp: x.x.88.17 is on fxp0 but
> got reply from 00:0c:42:11:15:a8 on rl0

That MAC address is that of a Mikrotic router.

I suspect that you've created a cabling loop of some sort again.

Steve



smime.p7s
Description: S/MIME Cryptographic Signature

Re: IPF, NAT or NIC

[Freeco]

My gateway gave me a message: "gateway kernel: arp: x.x.88.17 is on fxp0 but
got reply from 00:0c:42:11:15:a8 on rl0
-- 
View this message in context: 
http://www.nabble.com/IPF%2C-NAT-or-NIC-tp25491958p25513518.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"