search for: brigde

Hello, I am curious if the below setup makes any sense... If I have two public IP addresses served off of a cable modem, can I send one to a shorewall box in bridge mode, then have the other serve my network? Physically, I would like to run it: Cable Modem -> Shorewall Box -> Router -> Network Possible? I would like to do this using FC 4. thanks

On Fri, 11 Mar 2005 11:47:12 -0300 Mariano Wahlmann <wahlmann@agro.uba.ar> wrote: > hi, i'm trying brigde to use with qemu. my configuration is one > interface eth0 with two virtual ips 168.96.156.X and 10.1.1.X, but when > i use brigde i can only use one ip for br0 do you know how can i create > bridge br0 (to be used with qemu) and mantein my two ip's address config?. > > Thank...

...er down the xenbox. Is it normal ? Do you have a patch for xen-3.0-testing ? 2/ The "ethtool" doesn''t access to the data parameter of my RTL8139 lan interface in the dom0 to active the WakeOnLan power-on hardware fonction. Do you have any answer to that failure ? Is it come from Brigde or XEN hypervisor ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

HI I have 15 vm (libvirt + kvm) with a network brigde and ip address like 192.168.0.1 VM1 192.168.0.2 VM2 192.168.0.3 VM3 ..... The vm are use by other people and I want to be sure that if someone change the ip of VM3 to 192.168.0.1 it will filter it network traffic for him and can't flood the VM1 What the best way to achieve this Hope I m...

Hi I have a samba4 DC which also provides same KVM virtualisation services. During provision all IP numbers of all network interfaces where added to DNS, even the private KVM brigde Interfaces. Therefore clients which ask the DNS for AD-DNS records often get the IP of a an interface as answer, which is not reachable. This slows down things like login etc. I removed the DNS entries of the additional interfaces form the AD, using MMC DNS plugin and samba-tool dns command. But...

...gt; 192.168.221.202 Result: ACK never reaches 192.168.221.221 (last seen in TCP-dump of LOC-interface of FW) -------------------- Test-3: Custom generated packages (pacgen 1.01) sent 192.168.221.202 -> 192.168.224.254. Tcpdump was running on: 192.168.224.254, 192.168.221.7 and on the Sniffing Brigde. See http://statler.mupp.net/shorewall/Layout.jpg Result: RST-packet: Disappears (last seen in TCP-dump of LOC-interface of FW) ACK-packet: Disappears (last seen in TCP-dump of LOC-interface of FW) FIN-packet: Disappears (last seen in TCP-dump of LOC-interface of FW) SYN-packet: OK URG-packet: OK...

Hi, I want to know maximum vlan can be created by openvswitch and linux-brigde. how can I test for this limit. Is there any tool. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

I dont know gentoo, but the package might be called iproute2. You might also need the bridge-utils. Regards Dominik Friedrich Nietzsche schrieb: > Thanks found the issue atleast, here is what I get: > > xentest scripts # which ip > which: no ip in >

Hi, I have a Intel Xeon Dual Core server, with 3 GB RAM, running Centos 5.0, Asterisk 1.4.4 and mysql 5.0. It is a kinda high-traffic box, with about 60 concurrent calls. The profile of calls on this box are: Incoming: via a Sangoma A101 via SIP from anothjer SIP server Outgoing all calls that come in are sent out via SIP to yet another SIP server. This morning I has this error: (edited)

This was a bug 1.4.4 It has now been fixed in Asterisk 1.4.5 Stuart Bennett wrote: > Hi Yusuf > > A friend of mine had the same problem with a high volume site.. The problem > lies with a limitation in Linux. Linux will only allow a certain amount of > open files at a time. You will need to add the following line before running > asterisk. > > ulimit -n 32768 > >

Hello, I have see that my machine have an interface that named virbr0. I have no idea what is it and what it using for ? I am not configured any IP address for it but I see it had an IP address and see it listed in firewall config. Can anyone give me an explanation about this or point me to a document that describe it ? My machine running CentOS 5.2 and do not have internet connection from

I have a NetGear FV318 living in my DMZ, with one of its LAN-ports living in my LOC zone. What rules are needed in shorewall to allow a certain subnet to make connections to this device from the net zone? Do I define it as a tunnel in shorewall/tunnels, or do I just allow some selected traffic to the DMZ IP? I am not sure which of the docs are right for me in this case?

Hi to all. I''m installed XEN3.1 correctly but I''m some problem to start it. XEN start but I received this message: VFS: Cannot open root device "hda5" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) This is strange because my grub is configured like this:

Hi, We just migrated xen on gentoo on amd64 from 4.0 to 4.1 and encountered a few issues that were not documented. Here is how we solved them and what issues are remaining: 1. Our config files were referring to the LVM devices like /dev/vg/domU-root with disk = [ ''phy:vg/domU-root,sda1,w'' ]. This does not work anymore, we have to include ''/dev/'': disk = [

Hi, We just migrated xen on gentoo on amd64 from 4.0 to 4.1 and encountered a few issues that were not documented. Here is how we solved them and what issues are remaining: 1. Our config files were referring to the LVM devices like /dev/vg/domU-root with disk = [ ''phy:vg/domU-root,sda1,w'' ]. This does not work anymore, we have to include ''/dev/'': disk = [

Changes since v9: * series re-ordering so make functionality more distinct. Basic vlan filtering is patches 1-4. Support for PVID/untagged vlans is patches 5 and 6. VLAN support for FDB/MDB is patches 7-11. Patch 12 is still additional egress policy. * Slight simplification to code that extracts the VID from skb. Since we now depend on the vlan module, at the time of input skb_tci is

This series of patches provides an ability to add VLANs to the bridge ports. This is similar to what can be found in most switches. The bridge port may have any number of VLANs added to it including vlan 0 priority tagged traffic. When vlans are added to the port, only traffic tagged with particular vlan will forwarded over this port. Additionally, vlan ids are added to FDB entries and become