Search results

I continue to receive query traffic as follows: over the past months, these arrive approx. every thirty seconds. whois reverals that they come from With apologies, I do not know to interpret the format of the logged data, and I cannot find a clear, concise record layout for the logged data...

It's time to put this dog down; I don't think it's the fault of the onboard NIC in HPE ProLiant ML10 box. I've suffered with this problem for over three weeks. I've resorted to breaking down the ProLiant box and restoring the original FreeBSD v10.1 OS HDD to the original legacy platform...

No, actually the DMZ port has never been enabled in the Cisco configuration. (the Cisco port end of the CAT5 has never been unplugged from a LAN port on the switch.) BTW, I've discovered that I can ping the gateway port (.86) in addition to user (.81), and also another FreeBSD http server on a...

Noted: your advice regarding Linux, DMZ configuration, et al. (more perhaps for a future discussion). Regardless, I still suspect that something is broken with this Realtek driver. I'm breaking down the new HP box and swapping the Rosewill PCIe NIC for a new Intel NIC. EDIT/UPDATE: Done, but...

Segue'ing ahead re: Any thoughts regarding how the system is coming up with re0 when ifconfig is executed? (since it's not included in the kldstat -v list) In other words, where did/does this re0 driver module come from?

Well, as suspected, this will be a problem. There is a compile process involving a Makefile and autorun.sh (bash shell script) that are Linux shell dependent. What a POS! Seems anymore that if it's not Windoze, then Linux is the other option. What has made Linux so @#$! popular? :mad: I...

Everything is connected to LAN ports. DMZ is not used. Yes, the Cisco router is configured via a web GUI. . . .did try this but again, no joy. I have concerns regarding the "found or identified module", re0, which does not show up in the list revealed by kldstat -v, yet it seems to...

Address as assigned by AT&T are: .80 network .81 user available .82 " .83 " .84 " .85 " (apparently a 5th?) .86 gateway .87 broadcast This /29 network block was assigned by AT&T U-verse. I have confirmed that .86 is set as the default gateway in the Cisco router. I suppose that any...

OK, I suppose this is/was my lack of understanding of routing (a black art) dating back to circa late 1990's-2001. I've always included it, perhaps needlessly, but the system interface has always worked. This morning, as an experiment (for chuckles and grins), I've commented it out of...

Originally had network_interfaces="re0" . . .commented out. (always thought it was unnecessary -- gone again!) re: Actually mine is a /29 network of 8 static IP's (*.80-*.87); therefore, has to be 255.255.255.248 I've always included gateway_enable="YES" # Set to YES if this host will be...

Received and installed a Rosewill RC-411v3 - Network Adapter 10/100/1000 Mbps PCI-Express card and disabled the on-board NIC (in the legacy BIOS). I configured /etc/rc.conf to include gateway_enable="YES" # Set to YES if this host will be a gateway. defaultrouter="162.202.233.80"...

What actually happened: for some unknown reason, during the modification and test of the moused (port, type) specs in /etc/rc.conf, the system actually rolled-back from v10.3 to v7.2 RELEASE p8. This has resulted in loss of configuration files, e.g., apache24 back to apache22. Not sure...

MAJOR UPDATE! This problem apparently and mysteriously "fixed" itself. I have no idea how. I segued to another problem . . .installing a Logitech USB wireless mouse. Last evening and this morning, I rebooted the system several times, but the same error message (from a system call) limits...

Ran it and seemed to work; commands such as tar and ifconfig work once again however, the file, libpix.so.5, is still not found on the system, but the ifconfig command (now working) does not issue the message, ifconfig: shared object "libpix.so.5" not found required by "ifconfig". Strange...

Well, did this, but the upgrade still crashed. I have no idea where it was in the process . . .something about rebooting and running the upgrade again. It seemed to finish but the OS v10.3 is still there, bootable but severely damaged. Several things seem to be missing or out of place...

While executing freebsd-update -r 11.0-RELEASE upgrade Well, what can be done about this? Fetching metadata signature for 11.0-RELEASE from update.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata...

Note: It doesn't necessarily need to be symbolically linked to another physical location . . .it's just a convenience (to protect the source code saved in a different location other than /user/src/sys/i386/conf/ALPHAI3). Actually I've tested both scenarios asking the make buildkernel...

First, thanks for your interest in this puzzle! Well, I can assure you that the file does exist . . .I created it by copying the /usr/src/sys/i386/conf/GENERIC to /root/kernels/ALPHAI3, symbolically linked it to /usr/src/sys/i386/conf/ALPHAI3, and then edited it. So far, it is identical to the...

The current installed kernel (/boot/kernel) dates to DEC 31, 2001 (Yes, the OS is v10.1 . . .running 24/7 more or less since then . . .would upgrade but new server platform cannot speak to the Ethernet via the NIC.) I have downloaded a fresh driver from Intel...

Yeah, what I suspected. So if ifconfig can't see the NIC, then a driver for the NIC is missing from the FreeBSD OS?