search for: port2

...t 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. Can you explain me how do I create the port used by dnsmasq? For example, is it correct to execute # ovs-vsctl add-port virbr1 port2 tag=2 to create a port for the vLan whose tag is 2 named "port2"? Try something like this: ovs-vsctl add-port virbr1 port2 tag=2 ovs-vsctl set Interface port2 type=internal ifconfig port2 10.0.0.1 ifconfig port2 up /usr/sbin/dnsmasq --strict-order --bind-interfaces --except-interface...

...PT ipmasqadm portfw -a -P udp -L $EXT_IP 4569 -R $ASTERISK_IP 4569 ipchains -A portfw -s 0/0 1024: -d $EXT_IP 4569 -p 17 -j ACCEPT ipmasqadm portfw -a -P udp -L $EXT_IP 5036 -R $ASTERISK_IP 5036 ipchains -A portfw -s 0/0 1024: -d $EXT_IP 5036 -p 17 -j ACCEPT # loop for a bunch of ports for streams port2=10001 while [ $port2 -lt 10699 ] do ipmasqadm portfw -a -P udp -L $EXT_IP $port2 -R $ASTERISK_IP $port2 ipchains -A portfw -s 0/0 1024: -d $EXT_IP $port2 -p 17 -j ACCEPT ipchains -A portfw -s 0/0 $port2 -d $EXT_IP $port2 -p 17 -j ACCEPT port2=$((port2+1)) done # ***************************...

...sg, I get this: e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1e:68:58:00:4c <-- this is Port1 e1000e 0000:03:00.0: eth1: (PCI Express:2.5GT/s:Width x1) 00:15:17:d3:43:62 <-- PCIe Card e1000e 0000:08:00.0: eth2: (PCI Express:2.5GT/s:Width x1) 00:1e:68:58:00:4d <-- this is Port2 So this is how it gets enumerated for some reason. But during the machine's POST, it always brings up the PXE boot order as Port1, Port2, and finally the PCIe card, which is the correct order that I want it in. It also only has one single expansion slot so it's not like I can try a differe...

...ilani <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 to execute > # ovs-vsctl add-port virbr1 port2 tag=2 > to create a port for the vLan whose tag is 2 named "port2"? > > > Try something like this: > > ovs-vsctl add-port virbr1 port2 tag=2 > ovs-vsctl set Interface port2 type=internal > ifconfig port2 10.0.0.1 > ifconfig port2 up >...

Hello, with CentOS 6.2 - is it possible to configure OpenSSH daemon to listen on different IPs _and_ ports? I have received a 2nd IP address for my server and have successfully configured by adding the new "/etc/sysconfig/network-scripts/ifcfg-eth0:1" file. I'd like SSHd to keep listening at the_old_ip:22 but also at the_new_ip:443. The 443 on the_old_ip is already taken by

...-scripts/ifcfg-${NETDEV}-tmp /bin/mv -f /etc/sysconfig/network-scripts/ifcfg-${NETDEV}-tmp \ /etc/sysconfig/network-scripts/ifcfg-${NETDEV} done 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 ethernet devices as: Port1 Port2 PCIe card So where and why is the order changed when the kernel kicks in and start booting the machine? And how can I stop it, or c...

I want to capture all my Asterisk traffic (including RTP) and then analyse it. My plan was to use tcpdump and then analyse with Wireshark. The following works: tcpdump -i eth0 -s 0 -w /tmp/tcpdump.1 But I want to be a bit more selective: tcpdump -C 100 -W 10 -w /tmp/tcpdump -i eth1 -s 0 udp and dst port >= 5060 This doesn't capture the RTP traffic. Could anyone advise what I'm

...loads are always drawn below the driver node */ + subgraph cluster_driver { + fillcolor = grey; + style = filled; + driver -> {payload1, payload2} [dir=none]; + } + + /* Driver malloc references */ + edge [style=dashed]; + driver -> port1; + driver -> port2; + driver -> port3:e; + driver -> port4; + + payload1:s -> port1:e; + payload2:s -> port3:e; + edge [style=""]; + + subgraph cluster_topology { + label="Topology Manager"; + labelloc=bottom; + + /* Topology references */ +...

...press:2.5GT/s:Width x1) > > 00:1e:68:58:00:4c <-- this is Port1 > > e1000e 0000:03:00.0: eth1: (PCI Express:2.5GT/s:Width x1) > > 00:15:17:d3:43:62 <-- PCIe Card > > e1000e 0000:08:00.0: eth2: (PCI Express:2.5GT/s:Width x1) > > 00:1e:68:58:00:4d <-- this is Port2 > > > > So this is how it gets enumerated for some reason. But during the > machine's > > POST, it always brings up the PXE boot order as Port1, Port2, and finally > > the PCIe card, which is the correct order that I want it in. It also only > > has one single e...

...ame up that way) However I ran into other issues with the r8169 driver and ultimately replaced it for an IntelPRO, which happens to use the same e1000e module as the builtin ones. Great. Except ... Now when I kickstart the machine, I get this: builtin port1 -> eth0 PCIe card -> eth1 builtin port2 -> eth2 What I want is: builtin port1 -> eth0 builtin port2 -> eth1 PCIe card -> eth2 I should also point out here that when PXE kicks in on this machine, the machine correctly enumerates the ethernet devices as port1, port2 and then the PCIe card. So somewhere in the kickstart proces...

...loads are always drawn below the driver node */ + subgraph cluster_driver { + fillcolor = grey; + style = filled; + driver -> {payload1, payload2} [dir=none]; + } + + /* Driver malloc references */ + edge [style=dashed]; + driver -> port1; + driver -> port2; + driver -> port3:e; + driver -> port4; + + payload1:s -> port1:e; + payload2:s -> port3:e; + edge [style=""]; + + subgraph cluster_topology { + label="Topology Manager"; + labelloc=bottom; + + /* Topology references */ +...

...00:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) > 00:1e:68:58:00:4c <-- this is Port1 > e1000e 0000:03:00.0: eth1: (PCI Express:2.5GT/s:Width x1) > 00:15:17:d3:43:62 <-- PCIe Card > e1000e 0000:08:00.0: eth2: (PCI Express:2.5GT/s:Width x1) > 00:1e:68:58:00:4d <-- this is Port2 > > So this is how it gets enumerated for some reason. But during the machine's > POST, it always brings up the PXE boot order as Port1, Port2, and finally > the PCIe card, which is the correct order that I want it in. It also only > has one single expansion slot so it's not...

...Vo in this forumthread: http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1277983799644+28353475&threadId=1320596 So this is how my cable look like now: DB9-3 <---> RJ45-4 DB9-2 <---> RJ45-5 DB9-5 <---> RJ45-6 This cable is connected between port2 on the HP UPS Management Module, and the onboard DB9 connector on a server running Ubuntu 10.04 and NUT 2.4.3 In the HP UPS Management Module, I've set up a client called "tor" in load1, and assigned serial port2 to it with a shutdown time of 2 minutes. This is my nut configuration...

...gt; > > 00:1e:68:58:00:4c <-- this is Port1 > > > e1000e 0000:03:00.0: eth1: (PCI Express:2.5GT/s:Width x1) > > > 00:15:17:d3:43:62 <-- PCIe Card > > > e1000e 0000:08:00.0: eth2: (PCI Express:2.5GT/s:Width x1) > > > 00:1e:68:58:00:4d <-- this is Port2 > > > > > > So this is how it gets enumerated for some reason. But during the > > machine's > > > POST, it always brings up the PXE boot order as Port1, Port2, and > finally > > > the PCIe card, which is the correct order that I want it in. It also &...

...pology-figure-1.dot b/Documentation/gpu/dp-mst/topology-figure-1.dot new file mode 100644 index 000000000000..fb83789e0a3e --- /dev/null +++ b/Documentation/gpu/dp-mst/topology-figure-1.dot @@ -0,0 +1,31 @@ +digraph T { + /* Topology references */ + node [shape=oval]; + mstb1 -> {port1, port2}; + port1 -> mstb2; + port2 -> mstb3 -> {port3, port4}; + port3 -> mstb4; + + /* Malloc references */ + edge [style=dashed]; + mstb4 -> port3; + {port4, port3} -> mstb3; + mstb3 -> port2; + mstb2 -> port1; + {port1, port2} -> mstb1; + + ed...

...t/topology-figure-1.dot > new file mode 100644 > index 000000000000..fb83789e0a3e > --- /dev/null > +++ b/Documentation/gpu/dp-mst/topology-figure-1.dot > @@ -0,0 +1,31 @@ > +digraph T { > + /* Topology references */ > + node [shape=oval]; > + mstb1 -> {port1, port2}; > + port1 -> mstb2; > + port2 -> mstb3 -> {port3, port4}; > + port3 -> mstb4; > + > + /* Malloc references */ > + edge [style=dashed]; > + mstb4 -> port3; > + {port4, port3} -> mstb3; > + mstb3 -> port2; > + mstb2 ->...

...000..fb83789e0a3e > > > --- /dev/null > > > +++ b/Documentation/gpu/dp-mst/topology-figure-1.dot > > > @@ -0,0 +1,31 @@ > > > +digraph T { > > > + /* Topology references */ > > > + node [shape=oval]; > > > + mstb1 -> {port1, port2}; > > > + port1 -> mstb2; > > > + port2 -> mstb3 -> {port3, port4}; > > > + port3 -> mstb4; > > > + > > > + /* Malloc references */ > > > + edge [style=dashed]; > > > + mstb4 -> port3; > > > +...

...de 100644 > > index 000000000000..fb83789e0a3e > > --- /dev/null > > +++ b/Documentation/gpu/dp-mst/topology-figure-1.dot > > @@ -0,0 +1,31 @@ > > +digraph T { > > + /* Topology references */ > > + node [shape=oval]; > > + mstb1 -> {port1, port2}; > > + port1 -> mstb2; > > + port2 -> mstb3 -> {port3, port4}; > > + port3 -> mstb4; > > + > > + /* Malloc references */ > > + edge [style=dashed]; > > + mstb4 -> port3; > > + {port4, port3} -> mstb3; > >...

...urce type='unix' path='/path/port1' mode='client'/> <model type='virtio'/> </interface> <interface type='vhostuser'> <mac address='52:54:00:3b:83:1b'/> <source type='unix' path='/path/port2' mode='client'/> <model type='virtio'/> </interface> when i create the VM the qemu command is like this without 'share=on' parameter: -object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node0 -numa no...

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a