Re: Problem with re0
Hi,
Gabor Radnai (gabor.rad...@gmail.com) [10.11.11 23:22] wrote:
> pciconf:
> n...@pci0:0:20:0:class=0x068000 card=0x816a1043 chip=0x026910de rev=0xa3
> hdr=0x00
> vendor = 'NVIDIA Corporation'
> device = 'MCP51 Network Bus Enumerator'
> class = bridge
> r...@pci0:1:0:0:class=0x02 card=0x816810ec chip=0x816810ec rev=0x01
> hdr=0x00
> vendor = 'Realtek Semiconductor'
> device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)'
> class = network
> subclass = ethernet
>
i have the same problem (i was writing here before, but still no idea)
with onboard (Realtek Gigabit Ethernet NIC(NDIS 6.0)
(RTL8168/8111/8111c)) nic while the same driver but another vendor
(D-Link DGE-528T Gigabit adaptor (dlg10086)) nic works fine ...
the flapping of the realtek interface is so much drastic, that i was
forced to unplug the cable even on the ip less nic
i was sure it is the problem of the onboard rt nics ...
uname:
FreeBSD 8.1-STABLE #3 amd64
pciconf -lv:
r...@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)'
class = network
subclass = ethernet
r...@pci0:1:0:0: class=0x02 card=0x43001186 chip=0x43001186 rev=0x10
hdr=0x00
vendor = 'D-Link System Inc'
device = 'Used on DGE-528T Gigabit adaptor (dlg10086)'
class = network
subclass = ethernet
dmidecode:
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: AT5NM10-I
Version: Rev x.0x
Serial Number: MT7006K15200628
Asset Tag: To Be Filled By O.E.M.
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To Be Filled By O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LAN
Internal Connector Type: None
External Reference Designator: LAN
External Connector Type: RJ-45
Port Type: Network Port
--
Zeus V. Panchenko
IT Dpt., IBS ltdGMT+2 (EET)
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Pyun YongHyeon (pyu...@gmail.com) [10.11.13 01:01] wrote: > > Please be more specific for the issue. Your description is hard to > narrow down possible cause. > > > i was sure it is the problem of the onboard rt nics ... > > > > pciconf output of all re(4) controllers are useless because the > vendor uses the same device id. Please show me the output of dmesg > which will contain necessary information to identify your > controller revision. > oh, sorry :( here is what you say: the integrated onboard nic: re0: port 0xe800-0xe8ff mem 0xfafff000-0xfaff,0xfaff8000-0xfaffbfff irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x2800 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 48:5b:39:d2:1d:89 re0: [FILTER] external PCI nic: re1: port 0xd800-0xd8ff mem 0xfbeffc00-0xfbeffcff irq 17 at device 0.0 on pci1 re1: Chip rev. 0x1000 re1: MAC rev. 0x miibus1: on re1 rgephy1: PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re1: Ethernet address: 00:21:91:f4:5f:e4 re1: [FILTER] all that data i was posting here before (several months ago) and nothing changed since that time due to production state of the boxes i was forced finally to switch to external nics and to configure it with vlans and even to unplug the cable of the onboard nic since nic with plugged cable but without assigned ip address did begin flap (may be it's specific of the swith it plugged in, it is TP-Link TL-SG5426 but no other nic behaves this way) i have 7 boxes of this configuration and all 6 are running now on external nics if i can provide any debug/info/e.t.c. please let me know, i'd be happy it'd work at last :) -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: card sleeping
kalin m (ka...@el.net) [10.11.23 01:16] wrote: > > > hi all.. > > recently i had to change the static ip on a machine here at work. > nothing wrong with that. what's happening with this new ip (different > network) is that for short periods of time sometimes the machine is > unpingable. until i try to login ssh. as soon as i do that the ping and > the rest of network activity resumes - http. > looks like cached MAC at the router/commutator -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Hi all,
the same problem i wrote in the first posts about year ago :(
onboard re(4) tremendous flapping
while ( cable connects nic and switch )
{
re0: link state changed to UP
re0: link state changed to DOWN
}
here the details:
dmidecode
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: AT5NM10-I
Version: Rev x.0x
Serial Number: MT7006K15200322
uname -a
FreeBSD 8.2-PRERELEASE amd64
system was cvsup-ed 2011.01.20
if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari
dmesg
rgephy0: PHY 1 on miibus0
rgephy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX,
100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX,
1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto,
auto-flow
re0: Ethernet address: 20:cf:30:89:5e:95
re0: [FILTER]
pciconf -lv
re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)'
class = network
subclass = ethernet
flapping starts with cable pluging to the nic and to the switch, even without
ip assignment
switch used is TP-LINK TL-SG5426
the problem persists already about year and the only solution is to use
external nic ...
any idea/news?
--
Zeus V. Panchenko
IT Dpt., IBS ltdGMT+2 (EET)
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
another detail for this nic dmidecode Base Board Information Manufacturer: ASUSTeK Computer INC. Product Name: AT5NM10-I Version: Rev x.0x Serial Number: MT7006K15200322 uname -a FreeBSD 8.2-PRERELEASE amd64 system was cvsup-ed 2011.01.20 if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari dmesg rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 20:cf:30:89:5e:95 re0: [FILTER] pciconf -lv re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet while connected directly NIC <-> NIC they flaps too so, the issue with switch related causes can be excluded i believe -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Pyun YongHyeon (pyu...@gmail.com) [11.01.31 04:08] wrote: > > The RTL8168/8111D sample board I have does not show this kind of > > issue. This happens only when established link is 1000baseT, right? > > I slightly changed PHY's link detection code so would you try that > > patch at the following URL? > > http://people.freebsd.org/~yongari/re/rgephy.link.patch3 > > Previous one had a bug, please update one. > http://people.freebsd.org/~yongari/re/rgephy.link.patch4 no change :( interface continues to flap -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Milan Obuch (freebsd-...@dino.sk) [11.01.31 17:31] wrote: > > I checked my cables and one of them had bad pairing. Worked in 100 Mb mode, > but not in 1 Gb mode. After I replaced it I check with flood ping, 1472 bytes > packets again and no sign of problem here - one reply missing in almost 21 > millions tries. How are your flaps 'visible'? What fails? Ping test is > simple, > so I could overlooked something, but now it works for in 1 Gb mode, too... > while NIC flaps i see switch port on/off and in dmesg: ... re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP ... -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Pyun YongHyeon (pyu...@gmail.com) [11.01.31 23:14] wrote: > > Then I have no idea. Does other OS work with your hardware without > issues? As last resort, could you try vendor's FreeBSD driver? The > vendor's driver applies a bunch of magic DSP fixups which re(4) > does not have. I don't know whether it makes difference or not but > it would be worth a try. Note, vendor's driver treat your > controller as old 8139 such that it disables all offload features > and does not work on non-x86 architectures. > i386 exposes the same problem :( as for vendor's drivers, i didn't try them yet ... -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
collisions on tun interfaces ...
Hi, may somebody epxplain it for me, what can cause collisions on tun interfaces created by ppp(8) and openvpn? > uname -a FreeBSD 8.2-STABLE #0 i386 > netstat -i NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll tun0 1492 18940349 0 0 15737760 0 45668 tun0 1492 A.B.C.D A-B-C-D.domain 15623965 - - 12429351 - - tun1 1500 12721670 0 0 9957662 0 11161 tun1 1500 E.F.G.H E-F-G-H.vpn 6454 - - 445751 - - rl0: flags=8843 metric 0 mtu 1500 options=3808 ether 00:30:4f:67:cf:81 media: Ethernet autoselect (100baseTX ) status: active tun0: flags=8051 metric 0 mtu 1492 options=8 inet A.B.C.D --> A1.B1.C1.D1 netmask 0x Opened by PID 3943 tun1: flags=8051 metric 0 mtu 1500 options=8 inet E.F.G.H --> E1.F1.G1.H1 netmask 0x Opened by PID 1387 tun0 is created by ppp(8) in /etc/ppp.conf is: default: set log Phase Chat LCP IPCP CCP tun command set server /var/run/ppp/internet "" 0177 set device PPPoE:rl0 set speed sync enable lqr echo set lqrperiod 30 set login set ctsrts off add default HISADDR set timeout 0 set redial 0 0 set cd 5 tun1 is created by OpenVPN with configuration: client dev tun1 proto udp ... so, what can cause the collisions and can i fix them? -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: collisions on tun interfaces ...
YongHyeon PYUN (pyu...@gmail.com) [11.04.29 21:29] wrote: > On Fri, Apr 29, 2011 at 12:52:31PM +0300, Zeus V Panchenko wrote: > > Hi, > > > > may somebody epxplain it for me, what can cause collisions on tun > > interfaces created by ppp(8) and openvpn? > > > > > uname -a > > FreeBSD 8.2-STABLE #0 i386 > > > > > netstat -i > > NameMtu Network Address Ipkts Ierrs IdropOpkts > > Oerrs Coll > > tun0 1492 18940349 0 0 15737760 > > 0 45668 > > tun0 1492 A.B.C.D A-B-C-D.domain 15623965 - - 12429351 > > - - > > tun1 1500 12721670 0 0 9957662 > > 0 11161 > > tun1 1500 E.F.G.H E-F-G-H.vpn 6454 - - > > 445751 - - > > > > > > rl0: flags=8843 metric 0 mtu 1500 > > options=3808 > > ether 00:30:4f:67:cf:81 > > media: Ethernet autoselect (100baseTX ) > > status: active > > tun0: flags=8051 metric 0 mtu 1492 > > options=8 > > inet A.B.C.D --> A1.B1.C1.D1 netmask 0x > > Opened by PID 3943 > > tun1: flags=8051 metric 0 mtu 1500 > > options=8 > > inet E.F.G.H --> E1.F1.G1.H1 netmask 0x > > Opened by PID 1387 > > > > tun0 is created by ppp(8) > > > > in /etc/ppp.conf is: > > default: > > set log Phase Chat LCP IPCP CCP tun command > > set server /var/run/ppp/internet "" 0177 > > set device PPPoE:rl0 > > set speed sync > > enable lqr echo > > set lqrperiod 30 > > set login > > set ctsrts off > > add default HISADDR > > set timeout 0 > > set redial 0 0 > > set cd 5 > > > > tun1 is created by OpenVPN with configuration: > > client > > dev tun1 > > proto udp > > ... > > > > so, what can cause the collisions and can i fix them? > > > > It seems tun(4) just increments collision counter whenever it > can't enqueue packet. Because it's not collision at all I think > it's a bug that had been there from day 1. Just nuking updating the > counter will address the issue. You still can get the previous > collision counter of tun(4) with d option of netstat which shows > number of packets dropped due to send queue full. thanks, and is there way to influence that? -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: collisions on tun interfaces ...
Adrian Chadd (adr...@freebsd.org) [11.05.01 09:09] wrote: > On 1 May 2011 04:43, YongHyeon PYUN wrote: > > > It's tunable. Set net.link.ifqmaxlen. > > I know it's tunable at boot time; I mean why is it that low by default? > and what will be acceptable value for ASDL connections 8 and more MBit/s? -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: IPSec Routing
jh...@socket.net (jh...@socket.net) [11.05.22 05:31] wrote: > What I am not understanding is how to add routes correctly when using > transport mode. I have added the proper incoming/outgoing information > using setkey. When I display the information using setkey -DP, the routes > appear correct. I have defined one outbound route for the local private > network to the remote private network and vice versa. > what tcpdump shows? is there firewall? -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
weird results while ipsec + ipfv_nat (nat before vpn)
length 166: y.y.y.y > x.x.x.x: ESP(spi=0x060bc3e3,seq=0x7), length 132 00:00:00.635567 ethertype IPv4 (0x0800), length 166: x.x.x.x > y.y.y.y: ESP(spi=0xad597f86,seq=0x8), length 132 00:00:00.024689 ethertype IPv4 (0x0800), length 166: y.y.y.y > x.x.x.x: ESP(spi=0x060bc3e3,seq=0x8), length 132 00:00:00.636724 ethertype IPv4 (0x0800), length 166: x.x.x.x > y.y.y.y: ESP(spi=0xad597f86,seq=0x9), length 132 00:00:00.024286 ethertype IPv4 (0x0800), length 166: y.y.y.y > x.x.x.x: ESP(spi=0x060bc3e3,seq=0x9), length 132 so, is it possible to get it working? if yes, where is my mistake, please? -- Zeus V. Panchenko JID:z...@gnu.org.ua GMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
lagg(4) and alises
Hi, i need advice, please? while trying to set lagg(4) interface i faced some difficulty ... i need advice to optimize/correct the configuration ... mine current configuration is: igb2 igb3 | | igb0 +--+-++igb1 x.x.x.x ---+ FreeBSD 8.1-STABLE #4 amd64 +--- y.y.y.y/30 /29+---+-+---+ | | em0 em1 | | switch00 -+- lagg0 -+- switch01 + + z.z.z.z/26 + + | || | | +-- trunk 1 -+ | + trunk 2 ---+ /etc/rc.conf ... ifconfig_igb0="inet x.x.x.x/29 media autoselect" ifconfig_igb1="inet y.y.y.y/30 media autoselect" ifconfig_em0="UP" ifconfig_em1="UP" ifconfig_lagg0="laggproto lacp laggport em0 laggport em1" ipv4_addrs_lagg0="z.z.z.z/26" # only this forced it work, # ifconfig_lagg0 assigns # the address but it doesn't work ... now i need to set additional three ip addresses on lagg0 ... and everything i was trying was not working ... i was trying to add this to /etc/rc.conf: ifconfig_lagg0_alias0="inet 91.216.196.10/26" ifconfig_lagg0_alias1="inet 91.216.196.11/26" ifconfig_lagg0_alias2="inet 91.216.196.12/26" after reboot addresses are assigned but ifconfig lagg0 shows status: no carrier so, here is the question: how is it correct to set aliases on lagg(4) interface (aggregation protocol `lacp') in /etc/rc.conf file? -- Zeus V. Panchenko JID:z...@gnu.org.ua GMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: lagg(4) and alises
Hi, replying self question ... ipv4_addrs_lagg0="x.x.x.x/29 y.y.y.y/30 z.z.z.z/26" did help everything works after reboot all addressess are assigned and interface is up seems it is the only way to do that ... -- Zeus V. Panchenko JID:z...@gnu.org.ua GMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: igb watchdog timeouts
Hi, the same was for me untill i upgraded BIOS up to the latest one available from the MB vendor site i run: FreeBSD 8.1-RELEASE amd64 on: Base Board Information Manufacturer: Supermicro Product Name: X8SIL-F Version: 0123456789 BIOS Information Vendor: American Megatrends Inc. Version: 1.1 Release Date: 05/27/2010 with external quad port ethernet card i...@pci0:3:0:0: class=0x02 card=0xa02b8086 chip=0x10e88086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'Unknown (Unknown)' this MB is the second one i was trying, several days ago i asked to change it because of two onboard em(4) nics which worked unstable and any load were hanging them out up to reboot that time nothing helped (no one version of OS and bios upgrade), bUt igb(4) was working perfectly after the change the picture turned around until bios update and now i'm still unable to make them (no em(4) nither igb(4)) to hang :) and close to conclude the problem was in bios ... but anyway, now i'm CVS-ing to RELENG_8 :) -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) Jack Vogel (jfvo...@gmail.com) [10.07.30 06:49] wrote: > Try the code from STABLE/8 or HEAD if you would please, if you have > questions > of what or how let me know. > > Jack ---end quoted text--- ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: igb watchdog timeouts
Robin Sommer (ro...@icir.org) [10.07.30 18:38] wrote: > I'm going to try the driver from 8-STABLE, as suggested by Jack > (thanks!), but for the record, I've already updated the BIOS and I'm > still seeing the timeouts. just have CVS-ed to RELENG_8, recompiled the kernel and loaded the drivers em(4) and igb(4) - works! :) i was testing them with nc(1) server side: nc -u -l 5 > /dev/null client side: nc -u 5 < /dev/random but the maximum i was able to get was 500Mbit/s btw, is it correct to test it such way? -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: igb watchdog timeouts
Mike Tancsa (m...@sentex.net) [10.07.30 20:25] wrote: > > Try using the tools in /usr/src/tools/tools/netrate > > you can generate a lot more traffic this way. > thank you Mike, it works! :) netsend 10.11.0.2 5 1000 20 60 Sending packet of payload size 1000 every 0.05000s for 60 seconds start: 1280511835.0 finish:1280511895.14942 send calls:1190 send errors: 0 approx send rate: 19 approx error rate: 0 waited:13557673 approx waits/sec: 225961 approx wait rate: 1 -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
re0 link UP/DOWN on 8.1-STABLE amd64
Hi All, can enybody help with the subj, please? problem: onboard interface re0 link state UP/DOWN flapping i have: # uname -a FreeBSD 8.1-STABLE #0: Mon Aug 9 10:33:17 EEST 2010 amd64 # dmidecode ... Base Board Information Manufacturer: ASUSTeK Computer INC. Product Name: AT5NM10-I ... # pciconf -lcv r...@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[70] = PCI-Express 2 endpoint IRQ 2 max data 128(256) link x1(x1) cap 11[ac] = MSI-X supports 4 messages in map 0x20 cap 03[cc] = VPD # ifconfig re0 re0: flags=8843 metric 0 mtu 1500 options=389b ether 20:cf:30:89:5e:95 inet 10.10.0.111 netmask 0x broadcast 10.10.255.255 media: Ethernet 1000baseT status: active sporadically interface begins to flap and dmesg shows: ... Aug 11 14:29:44 kernel: re0: link state changed to DOWN Aug 11 14:29:47 kernel: re0: link state changed to UP Aug 11 14:29:58 kernel: re0: link state changed to DOWN Aug 11 14:30:01 kernel: re0: link state changed to UP ... systat doesn't show high interrupts on the card # systat -v 1 usersLoad 0.06 0.02 0.00 Aug 11 15:45 Mem:KBREALVIRTUAL VN PAGER SWAP PAGER Tot Share TotShareFree in out in out Act 1069020 177580 2968312 209660 455852 count All 1149408 184236 1076855k 251780 pages Proc:Interrupts r p d s w Csw Trp Sys Int Sof Flt278 cow8057 total 1 74 885 842 1181 57 268 736278 zfodatkbd0 1 ozfod22 rl0 irq17 0.4%Sys 0.1%Intr 0.2%User 0.0%Nice 99.3%Idle%ozfod 2000 cpu0: time ||||||||||| daefr33 re0 irq256 379 prcfr 2 ahci0 257 29 dtbuf 704 totfr 2000 cpu1: time Namei Name-cache Dir-cache10 desvn react 2000 cpu3: time Callshits %hits % 87484 numvn pdwak 2000 cpu2: time 921 921 100 24183 frevn pdpgs 3 intrn Disks ada0 ada1 pass0 pass1 576392 wire KB/t 21.40 0.00 0.00 0.00 1040084 act tps 2 0 0 0 1948900 inact MB/s 0.04 0.00 0.00 0.00 cache %busy 0 0 0 0 455852 free 427520 buf i have changed motherboards ... the same effect. after some time the problem appears again is there any info i can provide? thanks in advance -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: re0 link UP/DOWN on 8.1-STABLE amd64
Pyun YongHyeon (pyu...@gmail.com) [10.08.11 19:31] wrote: > On Wed, Aug 11, 2010 at 03:50:14PM +0300, Zeus V Panchenko wrote: > > Hi All, > > > > can enybody help with the subj, please? > > > > problem: onboard interface re0 link state UP/DOWN flapping > > > > > > i have: > > # uname -a > > FreeBSD 8.1-STABLE #0: Mon Aug 9 10:33:17 EEST 2010 amd64 > > > > # dmidecode > > ... > > Base Board Information > > Manufacturer: ASUSTeK Computer INC. > > Product Name: AT5NM10-I > > ... > > > > # pciconf -lcv > > r...@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 > > hdr=0x00 > > vendor = 'Realtek Semiconductor' > > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' > > class = network > > subclass = ethernet > > cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 > > cap 05[50] = MSI supports 1 message, 64 bit enabled with 1 message > > cap 10[70] = PCI-Express 2 endpoint IRQ 2 max data 128(256) link x1(x1) > > cap 11[ac] = MSI-X supports 4 messages in map 0x20 > > cap 03[cc] = VPD > > > > > > # ifconfig re0 > > re0: flags=8843 metric 0 mtu 1500 > > > > options=389b > > ether 20:cf:30:89:5e:95 > > inet 10.10.0.111 netmask 0x broadcast 10.10.255.255 > > media: Ethernet 1000baseT > > status: active > > > > > > > > > > sporadically interface begins to flap and dmesg shows: > > ... > > Aug 11 14:29:44 kernel: re0: link state changed to DOWN > > Aug 11 14:29:47 kernel: re0: link state changed to UP > > Aug 11 14:29:58 kernel: re0: link state changed to DOWN > > Aug 11 14:30:01 kernel: re0: link state changed to UP > > ... > > > > > > systat doesn't show high interrupts on the card > > # systat -v > > 1 usersLoad 0.06 0.02 0.00 Aug 11 15:45 > > > > Mem:KBREALVIRTUAL VN PAGER SWAP > > PAGER > > Tot Share TotShareFree in out in > > out > > Act 1069020 177580 2968312 209660 455852 count > > All 1149408 184236 1076855k 251780 pages > > Proc:Interrupts > > r p d s w Csw Trp Sys Int Sof Flt278 cow8057 total > > 1 74 885 842 1181 57 268 736278 zfod > > atkbd0 1 > > ozfod22 rl0 > > irq17 > > 0.4%Sys 0.1%Intr 0.2%User 0.0%Nice 99.3%Idle%ozfod 2000 cpu0: > > time > > ||||||||||| daefr33 re0 > > irq256 > > 379 prcfr 2 ahci0 > > 257 > > 29 dtbuf 704 totfr 2000 cpu1: > > time > > Namei Name-cache Dir-cache10 desvn react 2000 cpu3: > > time > >Callshits %hits % 87484 numvn pdwak 2000 cpu2: > > time > > 921 921 100 24183 frevn pdpgs > > 3 intrn > > Disks ada0 ada1 pass0 pass1 576392 wire > > KB/t 21.40 0.00 0.00 0.00 1040084 act > > tps 2 0 0 0 1948900 inact > > MB/s 0.04 0.00 0.00 0.00 cache > > %busy 0 0 0 0 455852 free > >427520 buf > > > > > > i have changed motherboards ... the same effect. after some time the > > problem appears again > > > > > > is there any info i can provide? > > > > Show me the output of dmesg and "devinfo -rv | rgephy". dmesg contains lines as above: ... re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to D
Re: re0 link UP/DOWN on 8.1-STABLE amd64
oh, i forgoten :( dmesg.boot contains: re0: port 0xe800-0xe8ff mem 0xfafff000-0xfaff,0xfaff8000-0xfaffbfff irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x2800 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 48:5b:39:d2:1d:89 re0: [FILTER] -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: re0 link UP/DOWN on 8.1-STABLE amd64
Pyun YongHyeon (pyu...@gmail.com) [10.08.11 23:09] wrote: > On Wed, Aug 11, 2010 at 10:34:07PM +0300, Zeus V Panchenko wrote: > > oh, i forgoten :( > > > > dmesg.boot contains: > > > > re0: > Ethernet> port 0xe800-0xe8ff mem > > 0xfafff000-0xfaff,0xfaff8000-0xfaffbfff irq 17 at device 0.0 on pci2 > > re0: Using 1 MSI messages > > re0: Chip rev. 0x2800 > > re0: MAC rev. 0x > > miibus0: on re0 > > rgephy0: PHY 1 on miibus0 > > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > 1000baseT-FDX, auto > > re0: Ethernet address: 48:5b:39:d2:1d:89 > > re0: [FILTER] > > > > >From the output above, I believe you're using slightly old stable. > Please use 8.1-RELEASE and let me know how it works on 8.1-RELEASE. ooops sorry, it was another box here the one i was begining from and where the problem persists too > uname -a FreeBSD egw.ibs.dn.ua 8.1-STABLE FreeBSD 8.1-STABLE #0: Mon Aug 9 10:33:17 EEST 2010 r...@egw.ibs.dn.ua:/usr/obj/usr/src/sys/EGW amd64 re0: port 0xe800-0xe8ff mem 0xfafff000-0xfaff,0xfaff8000-0xfaffbfff irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x2800 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 20:cf:30:89:5e:95 re0: [FILTER] > devinfo -rv rgephy0 pnpinfo oui=0x732 model=0x11 rev=0x2 at phyno=1 i was cvsup-ing a couple of days ago ... now i have killed all tree and cvs-ing again ... -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
startup network configuration choice
Hi All, may somebody advice, please ... i'd like to get automatic network configuration for my netbook while startup depending on the network it connected to while starting up ... not dhcp, but system startup script to detect the network and to configure the interfaces i have written script which receives arguments -h for home and -j for job and cosequently configures network, and configured network in rc.conf for one of the connections (default is job) but i'd like the system to do that automaticaly to avoid timeouts of network services like sshd/sendmail/e.t.c. when i'm starting up with "wrong" connection is there correct way to do that with some of the sturtup scripts or i have to do that by hands somewhere in rc.early? -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: RADIX_MPATH usage information
+1 -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
mac address cleaning ignored ...
Hi All, i have faced some "weird" mac address caching issue ... need help to understand who is who :( i have box A: FreeBSD 8.1-STABLE #2 amd64 and box B: FreeBSD 8.1-STABLE #3 amd64 both are connected to TP Link switch TL-SG5426 after nic change on box B i can ping box B from box A but i can not ping A from B ... i see the box A continue to reply to the box B old nic mac address ... how can it be possible if i have made: - arp cleaning on box A after what arp shows correct mac for host B -- pf reload/restart - arp cleaning on box B after what arp shows correct mac for host B -- pf reload/restart -- cold reboot - host/dns/mac cleaning on switch after what mac table contains correct mac for host B -- switch soft reload on box A i have quagga running ... can it cach mac addresses? the nic change was needed due to the heavy onboard nic re(4) card=0x83a31043 chip=0x816810ec Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c) flapping really i have no idea what to do except cold reboot of box A ... but who can to continue to remembers box B old nic mac address after all of that cleanings? thanks in advance -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
mac address cleaning ignored ...
cold reboot of box A helped ... why only cold? :( -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
