search for: arp

Hi all, Does any one know if this is normal operating of ARP. Or where to start looking. I am seeing a lot of ARP requests for my router IP from the same IP within seconds. 21:04:41.112929 arp who-has IP tell MY ROUTERS IP 21:04:41.186354 arp who-has IP tell MY ROUTERS IP 21:04:41.372972 arp who-has IP tell MY ROUTERS IP 21:04:41.546921 arp...

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 | | | |__________| | __________|____...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:14.arp Security Advisory The FreeBSD Project Topic: denial of service due to ARP resource starvation Category: core Module: sys Announced: 2003-09-23 Credits: Apple Product...

Hi, Thiago Oliveira <cpv.thiago@gmail.com> writes: > I would like to know the same! Currently I am using iptables to do it. I use ebtables. -Timo

...PHYSDEV match --physdev-in vif1.0 Chain OUTPUT (policy ACCEPT) target prot opt source destination debian:~# sysctl -p net.ipv4.conf.default.rp_filter = 1 net.ipv4.ip_forward = 1 net.ipv6.conf.all.forwarding = 1 net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.conf.default.proxy_arp = 1 + ip route list 192.168.100.3 dev vif1.0 scope link src 192.168.1.10 192.168.100.4 dev vif2.0 scope link src 192.168.1.10 192.168.1.200 dev eth0 proto kernel scope link src 192.168.1.10 default via 192.168.1.200 dev eth0 mw-xen:~# xm info host : debian release...

...: RETURN > > Bridge chain: POSTROUTING_direct, entries: 0, policy: RETURN > > Bridge chain: OUTPUT_direct, entries: 0, policy: RETURN > > Bridge chain: libvirt-I-vnet0, entries: 9, policy: ACCEPT > -j I-vnet0-mac > -p IPv4 -j I-vnet0-ipv4-ip > -p IPv4 -j ACCEPT > -p ARP -j I-vnet0-arp-mac > -p ARP -j I-vnet0-arp-ip > -p ARP -j ACCEPT > -p 0x8035 -j I-vnet0-rarp > -p 0x835 -j ACCEPT > -j DROP > > Bridge chain: libvirt-O-vnet0, entries: 4, policy: ACCEPT > -p IPv4 -j O-vnet0-ipv4 > -p ARP -j ACCEPT > -p 0x8035 -j O-vnet0-rarp > -j D...

Hello, You may recall some of My Dmz question around Thanksgiving. While I have configured a Proxy arp Dmz. I would like to practice with the routed setup you suggested Tom as your network was simular. Here is one of your quotes "The configuration of eth2 is largely irrelevant but you certainly don''t want to confuse things by assigning any default gateway out of that interface. I...

...mple, the router at 1.2.3.1 is outside the firewall and many of the servers at 1.2.3.nnn/24 are behind the firewall. (Obviously, 1.2.3.nnn is a fudged network.) eth0 points outward to the Internet. eth1 points inward to the serers. Both eth0 and eth1 have IP Address 1.2.3.2. I setup proxy ARP like this: echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp And I set up appropriate routes to the systems on both sides of the firewall. This all works - all the systems route the way they are supposed to route. Here is the problem. Be...

...iners as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host to not receive their arp replies anymore and as such they cannot reach their gateways and are now isolated from the network. There was a more recent update as well (4.1.4-2) which I have now since applied however this particular issue persists. The arp replies are received by the host and passed all the way up to the bri...

...iners as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host to not receive their arp replies anymore and as such they cannot reach their gateways and are now isolated from the network. There was a more recent update as well (4.1.4-2) which I have now since applied however this particular issue persists. The arp replies are received by the host and passed all the way up to the bri...

Can''t get proxy arp with arp -s <IPaddr> <MACaddr> pub to work with a 2.4 kernel. I see some evidence in the archive that this was broken in the 2.0.x timeframe and never fixed. Anyone know for sure if it''s broken or working ? (I''m attempting to route a few addresses into a routed netw...

Hello, I'm recently stumbled over the libvirt network filter capabilities and got pretty excited. Unfortunately I'm not able to get the the "clean-traffic" filterset working. I'm using a freshly installed Debian Stretch with libvirt, qemu and KVM. My config snippet looks as follows: sudo virsh edit <VM> [...] <interface type='bridge'> <mac

hi all, i got flooded by these msgs like 1000+ lines, any idea? my kernel is dated Nov-30 FreeBSD 4.9-stable # tail -f /var/log/messages Jan 18 19:43:23 xb /kernel: arp: 202.79.180.1 moved from 00:04:5a:49:eb:74 to 00:50:0f:4f:c0:00 on rl0 Jan 18 19:45:06 xb /kernel: arp: 202.79.180.1 moved from 00:50:0f:4f:c0:00 to 00:04:5a:49:eb:74 on rl0 Jan 18 19:45:18 xb /kernel: arp: 202.79.180.1 moved from 00:04:5a:49:eb:74 to 00:50:0f:4f:c0:00 on rl0 Jan 18 19:45:41 xb /ke...

Hi all, I''m running Xen-3.2 and linux-image-2.6.18 as Dom0 kernel on a VT-x processor. The problem is that broadcast arp who-has packets are not seen in Dom0 kernel. I''ve tried both precompiled debian kernel and compiled latest one from sources as described at http://lists.xensource.com/archives/html/xen-users/2008-01/msg00699.html There is no linux bridge invoked, xend-config has (network-script netw...

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply 10.32.2.51 is-at 00:30:48:34:44:6c...

...-ping- Site 1 (tinc-srv01) - Failure Server -ping- Site 1 - Server 1 - Failure Site 2 tinc-srv02 and server are running in a hosted environment (vmware esxi hypervisor) . while Site 1 and tinc-srv01 are running on my laptop (vmware workstation). On the server in site 2 it appears that there is no arp entries being propagated in its arp table. Is there a feature I need to enable ( ie Proxy Arp) on tinc-srv02 the arp to reach the server (site 2) ? My tinc-srv02 in Site 2 has one interface that I have bridged with tun0. Please advise? <yazeedfataar at hotmail.com> -------------- next pa...

...But now the weird part comes: I can communicate from domU to dom0, but not the other way around, unless I keep a ping running from domU to dom0... That''s right, weird... while trying the ping from dom0 to domU, I used tcpdump both on the bridge, on the vif and on the eth0 in the domU. The arp packets never get to domU, but they appear both in the bridge and the vif sniff''s... Here is the bridge: ifconfig virbr0 virbr0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff inet addr:192.168.120.254 Bcast:192.168.120.255 Mask:255.255.255.0 inet6 addr: fe80::7...

...But now the weird part comes: I can communicate from domU to dom0, but not the other way around, unless I keep a ping running from domU to dom0... That''s right, weird... while trying the ping from dom0 to domU, I used tcpdump both on the bridge, on the vif and on the eth0 in the domU. The arp packets never get to domU, but they appear both in the bridge and the vif sniff''s... Here is the bridge: ifconfig virbr0 virbr0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff inet addr:192.168.120.254 Bcast:192.168.120.255 Mask:255.255.255.0 inet6 addr: fe80::7...

...m, something strange happens. The networking works fine via usb0 for some time (a few minutes typically), yet suddenly, after enough packets got exchanged, the networking stops working. When I run tcpdump on the vif* interface I can see that suddenly there is nobody (in the netvm) to reply for the ARP requests from the client VM (the client vm has Xen ID = 42 in this dump, and IP = .5, and gateway = .1): [root@netvm user]# tcpdump -ni vif42.0 arp tcpdump: WARNING: vif42.0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on vif42.0, l...

...n I connect to a directly-connected 10.0.0.xxx address it indeed chooses the 10.0.0.2 source address (link-address), but when connecting to a remote host (via a GW learned by Zebra) it uses the 17.70.0.1 source address. Great! Problem solved! Well.. Almost.. There seems to be one snag: Incorrect ARP source address. If there is no ARP entry for the gateway yet (no traffic has gone out, routes learned from another BGP peer) and I try to reach a remote address immediately then the ARP request that goes out on the 10.0.0.0 network for the correct gateway does *not* contain the 10.0.0.2 source a...