similar to: can not wake on lan after halt -p (or shutdown -p now) on releng_7 and releng_7_0

Hi all I've very big problem with my nfsd server. I'm running FreeBSD-stable and sometime (one time/week) i've this kind of message on the console : bge0 watchdog timeout problems fxp1 watchdog timeout problems and all my network card is down. Nothing can make the network card work again (only reboot working). There are only one service I need on this server and

Hi, I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after booting, re0 works for only a short time, then gives "re0: PHY read failed" over and over. Does anyone have a suggestion on how to debug? Thanks, Steve

I have an Asus P5Q-WS running FreeBSD 7 and the onboard Realtek NIC's are not being detected. No Kernel modifications as this is a fresh install. pciconf -lv : re0@pci0:3:0:0: class=0x020000 card=0x82c61043 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network

With FreeBSD 6.3-RELEASE, I'm finding significant packet loss (sometimes 85%). If I insert an Intel nic (fxp), there is nil packet loss with similar tests (ping -c 100). re0: <RealTek 8168/8111B PCIe Gigabit Ethernet> port 0xc800-0xc8ff mem 0xf9fff000-0xf9ffffff irq 17 at device 0.0 on pci1 I have seen a thread on current mentioning similar problems:

Hi list, Are there any problems with the if_re ? After upgrade RELENG_7 on my laptop NIC stopped to work:( uname -a: FreeBSD notebook.minsk.domain 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #3: Fri Apr 10 20:38:55 EEST 2009 root@notebook.minsk.domain:/usr/obj/usr/src/sys/tiger-asus-a6m i386 notebook# dhclient re0 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on re0 to

A bit OT, but I'm running CentOS-5.6 on this machine (in fact on two of them) and it seems to run perfectly - I've had no problems at all. Except that I'd like to add a second ethernet port, and am not sure where one can find a card that will fit this machine. As far as I can see, it requires a half-height PCIe card, which seems to be rather a rare animal. (There doesn't seem to

Hello, I need some advice how to debug this issue ... Recently I got a new mainboard for a router, it's a Gigabyte GA-H77N-WIFI with two onboard re(4) NICs. The problem is that re0 works fine and re1 doesn't: It doesn't receive any packets. Tcpdump displays all outgoing packets, but no incoming ones on re1. Ifconfig shows the link correctly (100 or 1000 Mbit, depending on where I

Dear colleagues, experimenting with new amd64-based router we found strange re(4) behaviour when working in autoselect media mode: whenever promisc mode turned on, renegotiating occurs, leading to 3 to 45 (depending on STP settings on the switch) network unavailability. Moreover, some other re(4) setting changes seem to disturb link state unneededly (such as ifconfig re0 -vlanhwtag) The most

Hi, Whilst doing some QA work on XORP on my desktop, which has fxp0 and msk0, fxp0 got totally hosed. I was running PIM-SM and IGMPv2 router-mode on the box at the time. I wonder if this is related to the problems with fxp multicast transmission I saw back in April. I'm a bit concerned about this as fxp is still a very widespread and useful network chip. I am running

I've spent the past four days or so updating machines here to 4.8/9-stable via cvsup, and have done a complete make buildworld/kernel on each machine (some SMP, some single processor). It seems something is broken with the latest fxp driver, on each machine (different mobos and hardware configs) heavy network traffic with fxp NICs causes timeouts and random kernel panics. First machine to

Hi, I'm having strange performance problems with samba and an application written with VisualFox Pro. This application is entirely installed in a Windows share and it has a hystory of strange phenomenons. Initially it ran fast on an old NT server (but that server has been replaced). It has strange performance problems with Windows 2000 Server: it runs fast with some servers and slow with

Hi, I noticed that my 4.8R box seems to have a NFS problem. I use a FreeBSD/i386 4.8R box as a NFS server, and a FreeBSD/i386 5-CURRENT (as of today) as the NFS client. On the client, /a (on the server) can be mounted successfully with -o rw,bg,intr,mntudp options. However, when a large amount of write operations such as "cp -r /home/ncvs /a" are performed on the client, the

Hi, After updating from 7.0-RELEASE to STABLE (around 15/08) my NIC refuses to handle large file transfers. pciconf -lv re0@pci0:4:0:0: class=0x020000 card=0x001a6409 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller' class = network subclass = ethernet Log

My system is: Intel CC820 motherboard (which supports PME# wake up for wake on LAN) 3com 3C905C which also supports wake on LAN via PME# Linux 5.5 The motherboard BIOS is later than one that reports an issue with WOL and this particular network card was fixed. But when I turn off the PC (shutdown or poweroff commands or front panel button), it cannot be restarted via WOL. The network light on

Some switch hardware can generate the packets directly, negating the need for a box on every VLAN. Meraki hardware can do it, but you have to go through the dashboard so automating it isn't currently possible. Here is some documentation on forwarding WoL on catalyst 3750 switches from Cisco:

Has anyone experience with WOL under Centos (5.3).? If so, how exactly do you put the machine to sleep, and how exactly do you wake it up remotely? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin

On Sun, 2020-05-17 at 20:25 -0600, R C wrote: > Ok, I get that, found it before; "typically sent as a UDP datagram to > port 0, 7 or 9, or directly over Ethernet as EtherType 0x0842" > > > The keyword being 'typically', but what is it that ether-wake actually > uses/does? (I need to forward a WOL packet to a different > > vlan on some Cisco

My future plan currently looks like this for my VPS hosting solution, so any feedback would be appreciated: Each Node: Dell R210 Intel X3430 Quad Core 8GB RAM Intel PT 1Gbps Server Dual Port NIC using linux "bonding" Small pair of HDDs for OS (Probably in RAID1) Each node will run about 10 - 15 customer guests Storage Server: Some Intel Quad Core Chip 2GB RAM (Maybe more?) LSI

Hello, after upgrading my system from 7.1-RELEASE to recent RELENG_7 I noticed stalled network transfers in certain cases. I have an Intel PRO/100 ethernet adapter (card=0x00408086 chip=0x12298086 rev=0x0c). In general networking works fine. I can ping hosts, surf on websites and so on. But if I send large files (>1 MB) to my server the transfer stalls after a few kilobytes. This concerns FTP

Many thanks to those that responded to my original posting with information about Network UPS Tools and commercial UPS products. In our planning a path forward to implement UPS-based power fail protection, we have come across what appears to be an issue with the state of the CentOS 6 machines being UPS protected.? Most of these machines are desktop/deskside machines that are likely to be idle