similar to: odd log mesage...looks serious

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to run a QEMU VM on top of a FreeBSD 7.x server ... I've tried the exact same setup on my desktop, using 192.168.1.x and an fxp device, and it all works perfectly, but as soon as I do this on another machine on a public IP, I'm not getting any routing, I can't even ping it from the same machine ... My first thought was

Hello security, This output I've received from conventional cron daily job: [...] gw.nbh.ru kernel log messages: > Limiting closed port RST response from 201 to 200 packets per second [...] where fxp0 is an external interface. What could involve such a messages? In /var/log/messages the above strings was prepended by string: Feb 10 13:24:29 gw /kernel: ipfw: limit 100 reached on entry

This message was sent to bugtraq today: While playing around with FreeBSD 5.4 and jailing I discovered that it was possible to put an ethernet interface into promiscious mode from within the jailed environment, allowing a packetsniffer to gather data not meant for the jailed box. This also affects FreeBSD 5.3 (tested) but not FreeBSD 4.x This can be reproduced on boxes where BPF support is

I have just checked the Openbsd box on the if interface. fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:02:55:30:54:28 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::202:55ff:fe30:5428%fxp0 prefixlen 64 scopeid 0x1 xl0:

Hi: I have a machine with four interfaces connecting four different networks. I am learning to use nmap and trying to force the nmap working only one interface. As nmap man page states, I use -e option and it would not work: nmap -e fx0 -v -sP 192.168.128.0/23 Starting Nmap 3.95 ( http://www.insecure.org/nmap/ ) at 2006-02-04 14:04 CST getinterfaces: Failed to open ethernet interface (el0)

This is ifconfig on openbsd box: fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 I think this output shows that the fxp0 interface is on simplex mode. The voice degradation I referred was by using xlite soft phone. I open 2 line similtaneously and dial to FWD and back to my incoming extension. Xlite is runnning on a w2k box with realtek 100M nic in auto mode. I can

On 03/25/09 12:30, James Carlson wrote: > Girish Moodalbail writes: > >> bash-3.2# dladm show-link >> LINK CLASS MTU STATE PROMISC OVER >> e1000g0 phys 1501 up off -- >> e1000g1 phys 1502 up on -- >> > > That (plus or minus some column alignment) seems

Hello again :) With POLLING enabled I experience about 10%-25% performance drop when copying files over network. Tested with both SAMBA and NFS. Is it normal? FreeBSD 7.1-PRERELEASE #0: Sat Sep 6 01:52:12 CEST 2008 fxp0: <Intel 82801DB (ICH4) Pro/100 Ethernet> port 0xc800-0xc83f mem 0xe1021000-0xe1021fff irq 20 at device 8.0 on pci1 # ifconfig fxp0 fxp0:

Hello, I have been using the bridging facilities provided by Linux (vanilla 2.6.7 SMP with UML skas host patch applied) to bridge a regular physical ethernet network (on interface eth0) with a virtual network (on interface tap0, cf uml_switch, http://user-mode-linux.sourceforge.net/networking.html). A couple of virtual machines (run using user-mode linux, a tool that enables you to run linux

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

The 8168B (02) NIC works well except that it does not go into promiscuous mode despite advertising itself in that mode after being so directed with ifconfig. Unfortunately, the little box is destined to be an IDS monitor, so that function is essential. The board is an Intel Atom 330 run as x86_64, the nic is internal. We tried three drivers: the one in the 2.6.18-128.1.10.el5 kernel yields

Hello all, Playing with Xen on GNU/Debian Lenny, I just discovered that all my virtual network cards are in promiscuous mode by default. Changing that manually does not seems to change anything (that is, everything still works great). Is there any reason to have virtual network cards in promiscuous mode ? And where can I change this default behaviour ? Thanks, JB

Hi all, First of all, I have spent a lot of time reading up on it. Anyway, I live in a shared accomodation with 2 roommates and a landlord and we share a cable internet connection. It is 2Mbit/400Kbit connection. Sometimes when one of us is downloading a song through Kazaa or a new Linux or FreeBSD iso, the bandwidth gets hogged and other users can't get through. I was trying to configure

Hi, I have been doing some tests using hping2 and TCP SYN pings targeting local and remote hosts from two FreeBSD 4.7-RELEASE-p10 and one Linux 2.4.18 host. The three machines have the same hardware configuration and have been running for 6 months now. The average load isnt too high (usually 0.01 to 0.15) on the FreeBSD machines. Here is the output from hping2 (excuse me the line wrap),

Can I ask you a quick question? I''ve set up bridge-networking for Xen 4.1 (xen-4.1.3-25.el5.22) and networking was being done properly for Dom0 and DomUs. However, I noticed that Dom0 receives a lot of network interrupts or network packets even when they were not actually meant for either Dom0 or DomU. Now, here are the questions: 1. Dom0 is acting in promiscuous mode, right? 2. If

Hi there -- I want to have eth1 on my system run in promiscuous mode. I modified the /etc/sysconfig/network-scripts/ifcfg-eth1 file to read as follows: DEVICE=eth1 BOOTPROTO= ... ONBOOT= TYPE=Ethernet ... I reboote the system and when I did an /sbin/ifconfig, eth1 appeared without an ip address. I did a check in the /var/log/messages file and while eth0 is in promiscuous mode, eth1 does not

On Wed, May 31, 2017 at 3:56 AM, Julien Viard de Galbert via Syslinux <syslinux at zytor.com> wrote: > This extra socket cause the EFI udp stack to duplicate every packet > to be able to provide them to both udp_reader and socket->net.efi.binding. > The ones in socket->net.efi.binding were never read so they accumulated in > the stack on EFI side making the stack slower and

Motherboard ASUS CUSL2-C with 815EP chipset and two Intel 82559 Pro/100 Ethernet cards exibits the following. dmesg reports usual text only a few seconds after reboot. Later it displays a single line with a fragment of ipfw log, e.g. 167 213.131.11.152 in via fxp0 which seems to change with each new activity of ipfw. Files /var/log/dmesg.today and /var/log/dmesg.yesterday rotate daily as usual

On Thu, May 9, 2013 at 6:39 AM, syslinux-bot for Matt Fleming <matt.fleming at intel.com> wrote: > Commit-ID: fe283b78c973268f2d1f0309826ceeb5c9e8978d > Gitweb: http://www.syslinux.org/commit/fe283b78c973268f2d1f0309826ceeb5c9e8978d > Author: Matt Fleming <matt.fleming at intel.com> > AuthorDate: Fri, 22 Mar 2013 14:54:09 +0000 > Committer: Matt Fleming