similar to: arp corrupted

Hi, My bridging stops when I start a third Xen domain !?!? I have a few domains setup (mail, wiki, pbx). If I start two domains bridge networking works great. But if I start a third, either the new domains does not work or one of the other DomUs stops working! By stop working I mean I can''t route traffic outside of Dom0. I have been looking at this on and off for a couple of weeks.

Hi all. I experienced a strange behaviour in the "arp" command when I use the "pub" (publishing) flag. This is the scenario (I know it''s an unusual one, but it''s just for a test): __________ | | | host C | | | |__________| | __________|________________________________

On Sat, 18 Jul 2015 22:37:30 -0700 Gordon Messmer wrote: > On 07/18/2015 10:12 PM, Frank Cox wrote: > > Interesting. But since it's still exactly the same, it's still not > > working; it still fails in exactly the same way too. > > Yes, but that means you need to start with the standard troubleshooting > stuff. Do you have link? Is the Ethernet cable working?

Dear all, Has anyone experienced this whilst running DRBD over eth1 between two CentOS 5.7 servers? eth1 is a private IP address, unroutable. eth0 is the public address. CentOS will reply sometimes once every 3 days or every 14mins~ saying "My public IP is on eth1" to arp requests when it's not, it's eth0. This freezes traffic and causes issues. We've looked at arp*

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: important A few minutes after starting a domU, network access is no longer possible from and to it. This does not always happen and is not easily reproducible, but seems to occur in all newly started domUs from some point in time on. However, also restarting the dom0 does not necessarily prevent the problem. At the moment when

Am 19.07.2015 um 08:13 schrieb Frank Cox: > On Sat, 18 Jul 2015 22:37:30 -0700 > Gordon Messmer wrote: [ ... ] > Do you see > any traffic if you run "tcpdump -nn -i eth1"? > > I see no traffic on eth1 with that command until I log into another session and type "ping google.com". Then I get this output: > > [root at audio ~]# tcpdump -nn -i eth1 >

On Wed, 2015-09-16 at 01:52 +0200, Arne Klein wrote: > [...] > At the moment when the network in the domU completely stops working, > there is the error message > [2178752.854380] vif vif-33-0 vif33.0: Guest Rx stalled > visible in dmesg in the dom0. This will therefore be a kernel issue not a hypervisor one. It sounds like a backend one given the issue is with both new and

This one is really throwing me. Thanks in advance for any advice. I''m working on a 4 port firewall system. It is running heartbeat+drbd. Primary box looks like this: eth0 -> net/cicso router 192.168.144.2/29 eth1 -> drbd/heartbeat crossover cable 192.168.254.253/30 eth2 -> dmz 192.168.144.10/24 eth3 -> loc 192.168.101.2/24 The IP''s

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, this might seem like a classical problem but I''ve trouble getting this working correctly: # ifconfig ### output stripped down: eth0 Link encap:Ethernet HWaddr 00:50:FC:2B:EB:1B inet addr:192.168.5.220 Bcast:192.168.5.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:02:44:60:EC:58 inet

We have a webserver that is connected to three different networks. Due to our cabling, we have to run two of those networks over the same physical network. When connecting from OS X and Windows we are occasionally blocked because the client is sending to the wrong interface. Linux clients seem to have no problem at all. I have read the docs and understand that the problems exists because of

Hy shorewall users :)) I have the following config in my shorewall: DNAT net:200.137.193.2 loc:192.168.0.55 udp 135,445 - 200.137.193.38 DNAT net:200.137.193.2 loc:192.168.0.55 udp 137:139 - 200.137.193.38 DNAT net:200.137.193.2 loc:192.168.0.55 tcp 135,139,445 - 200.137.193.38 The IP

I''m trying to setup some DNAT and the packets seem to be disappearing after the PREROUTING step. The packets are coming in eth2 (both LOG targets in iptables and tcpdump confirm this). They are then DNATed to an IP that should cause them to go out eth3. However I never see them go out that interface. I have tried putting LOG rules into the FORWARD chain with no success. I''m

Hello everybody. I have a problem with my firewall rules on my Slackware Linux box 9.0 (kernel 2.4.20-xfs). This system is configured with 3 NIC (one for the router, one for the dmz, and the other for the private net). I have written a firewall (iptables) that is processing packet based also on the incoming interface. This firewall is connected in a not good environment where all the NIC (and the

Hi, I''m having problems with new Shorewall installation on Fedora Core 3 (had same problem with Core 2 and upgrade did not help even iptables was upgraded from 1.2.9 to 1.2.11). I''ve followed two nic example, but starting Shorewall drops all connections and don''t permit any outgoing requests, even with "all allowed" policy. Policy file is below. Current setup

Using a default xen3.0.1 setup for dom0(rhel4 distro) and domUs (gentoo, rhel4, centos4.2 distros, ttylinux) with the domUs all having dhcp turned on, is there an easy way to tell from within the dom0 what ip addresses were assigned to the domUs after bootup? Toby Ford USi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=40 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From laforge@netfilter.org 2003-02-03 16:49 ------- We haven't seen this

I''m very new to shorewall. My setup is IP Gateway (CentOS 4 + Shorewall) with 3 NIC cards. Shorewall works great on the firewall machine. Bind also works (local net machines get IPs fine). Under firestarter, all works great. With shorewall, the loc machines can not route past the firewall. They can connect to the firewall, but not past it. Exactly what information should I post to get

Hi, I''ve installed xen 3.0.3 from packages (xen-linux-system) on a debian etch, and i''ve configured it with network-bridge script in the default way (netdev=eth0, bridge=xenbr0, etc...) which is ok for me. the problem I have: I cannot ping any outer machine from dom0 (nor any outer machine can ping me). It gives me a "Destination Host Unreachable" message that

Hello! I am using shorewall shorewall-2.0.11-1 on fedora core2 (iptables-1.2.9-95.7). My box has 2 physical nic´s plus one virt. ipsec interface for a freeswan-vpn connection. A few days ago, portsentry spit out a lot of connections from windows clients (port 135, 445). Ooops. I review my shorewall settings but could not find a mistake. So I took a win-client and established a second

I been running shorewall with out any problems for several months. But I''ve now run into a problem. Hopefully this will be enough information. I''m running shorewall version 1.4.8. On Fedora core 1. Coming into my location I have a T1. I have 5 internet routable IP''s. I''m currently using one as my default internet connection. My ISP''s router is