similar to: [Bridge] Problem Bridging VLANs

Date: Thu, 22 Mar 2012 11:43:03 -0700 Subject: Re: [libvirt] Problem with Open vSwitch and dnsmasq From: aatteka at nicira.com To: dano1988 at hotmail.it CC: libvir-list at redhat.com; roberto.sassu at polito.it; paolo.smiraglia at polito.it; dev at openvswitch.org On Thu, Mar 22, 2012 at 11:11 AM, Daniele Milani <dano1988 at hotmail.it> wrote: I think I could try the first solution.

Just responding in case this may be of help to somebody with firewalling issues. Not sure if this is off on a tangent to the original question... Here are three different forms of common firewall scripts and ways of getting SIP to work behind them. The third one has some additional stuff beyond just SIP although I can't remember why I wrote it that way. I've been having no fun using

Hello, I'm having a problem getting two (working) NICs enslaved to a bridge to both work in the bridge. The setup is just for testing and looks like this: (NETWORK)-------|bridge|---------|test PC| I'm building a bridge from an old Dell Optiplex GX1 desktop. Using kernel-2.6.9-gentoo-r4, with bridging and ebtables compiled into the kernel; the two PCI NICs are Intel, and the e100

(Cc'ing to libvirt-users at redhat.com) On 03/22/2012 02:43 PM, Ansis Atteka wrote: > > > On Thu, Mar 22, 2012 at 11:11 AM, Daniele Milani <dano1988 at hotmail.it > <mailto:dano1988 at hotmail.it>> wrote: > > I think I could try the first solution. Can you explain me how do > I create the port used by dnsmasq? > > For example, is it correct

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

So a 70-persistent-net.rules like # onboard port 1 -> eth0 ACTION=="add", SUBSYSTEM=="net", BUS=="pci", ID=="0000:00:19.0", NAME="eth0" # PCIe card -> eth2 ACTION=="add", SUBSYSTEM=="net", BUS=="pci", ID=="0000:03:00.0", NAME="eth2" # onboard port 2 -> eth1 ACTION=="add",

So I'm back to this problem. A quick run down of what the original problem was: I have a machine that I'm configuring to use kickstart to setup. It has two builtin ethernet ports (labeled ports 1 and 2) and I'm adding a third one on its PCIe bus. Originally I was using an r8169 clone a default kickstart always put it as eth0 with the builtin ones as eth1 and eth2 respectively. After

another identical machine will have the same bus ids. that's why this works. Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty Ltd GitHub: @tartansandal Suite 1416 401 Docklands Drive Docklands VIC 3008 Australia "All parts should go together without forcing. You must

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

Actually, I know what the MAC is for the builtin Port1 and 2. Those are listed in the BIOS. But ultimately I don't want to rely on them as I want the same kickstart file to work for other machines, so hardcoding those in the kickstart file wouldn't quite work, unless I start writing multiple kickstart files, one per machine. Anyway, lspci reports this: 00:19.0 Ethernet controller: Intel

Right, I understand that part. However I believe I'm now in the realm of making this specific to this machine as I have no guarantee that another identical machine will pop up with those same bus IDs. Maybe for the internal ports, but I don't know if the same will happen for the PCIe bus. Would that be correct? On Thu, May 14, 2015 at 6:21 PM, Kahlil Hodgson < kahlil.hodgson at

On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > The current way of handling refcounting in the DP MST helpers is really > > confusing and probably just plain wrong because it's been hacked up many > > times over the years without anyone actually going over the code and > > seeing if things

Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent

UPS: HP R3000 XR with HP UPS Management Module What I Want: I just want the UPS to shut down the client called "tor" before the UPS power drains out, I'd prefer to use a direct serial cable instead of network, in case the network doesn't work. I'll manage the UPS trough the ethernet using the built-in HTTP webinterface in the HP UPS Management Module. I've created a

When I was working on this last time (with the r8169 driver), someone on this list provided the following script which is what "fixed" the issue at the time by creating a new 70-persistent-net.rules file with the devices enumerated in order. However, this no longer works now. echo "[KICKSTART] Binding eth interfaces to the expected MAC address in UDEV" echo "## Created by

I've been doing some testing between Windows 2000 Pro (SP4) and Windows 2000 Server (no SP and SP4) -- specifcally testing file transfers from a Samba 2.2.8a server. Samba server: P4/2.2GHz, ServerWorks chipset, SCSI UW2 disk subsystem (Bonnie++ tested to 35MB/sec), 3Com (acenic) gigabit ethernet Win2kPro: P3/700, 3Com Vortex 100mbit network card Win2kServer: P3/800, 3Com Vortex 100mbit

https://bugzilla.netfilter.org/show_bug.cgi?id=1427 Bug ID: 1427 Summary: can not reuse source port to a DNATed IP if it is being used by another connection Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: normal Priority: P5

On 15 May 2015 at 03:51, Ashley M. Kirchner <ashley at pcraft.com> wrote: > After the machine boots and I look in /root/ksnet-devices, I see the MAC > addresses for the devices as: > Port1 -> eth0 > PCIe Card-> eth1 > Port2 -> eth2 > > And yet, during the machine's POST (which can verify by the PXE boot up of > each device), it correctly enumerates the

On Tue, Dec 18, 2018 at 04:27:58PM -0500, Lyude Paul wrote: > On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > > The current way of handling refcounting in the DP MST helpers is really > > > confusing and probably just plain wrong because it's been hacked up many > > > times over the