similar to: Bug in the HOWTO: proxy-arp (?)

Hello, My apologies if this isn''t the right place to send questions about this thread. I have a couple one''s about proxy_arp and gratuitous arp reply frames. I have setup the proxy_arp parameter on a linux system (kernel 2.4.20). Now, when I start a M$-Windoze machine it complain about "...duplicated IP address...". This is a know behaviour, and the solution is

Hello, Fast question: from DomU I cannot ping Dom0, I only get 19:17:33.573370 arp who-has 192.168.10.1 tell 192.168.10.150 19:17:34.573421 arp who-has 192.168.10.1 tell 192.168.10.150 using tcpdump in Dom0. Why? --------------- Detailed question: I''m setting up a Xen virtual server. The environment is: -HVM -AMD64 -Debian Etch and using Xen from Debian repository (so Xen 3.0.3,

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 network, from the ethernet side of a DSL router that has a /29 public

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings I''m having a network problem that I don''t understand. It involves/hinges upon an internal router running the latest Shorewall. We make weather radar control and networking software. Our customers are experiencing a connection timeout, but here in the office we are not. I have some slight suspicions as to why they see a

Woops - my fat fingers hit the send key before I could put in a subject a minute ago. Hello - I am using kernel 2.4.27 and running into behavior I don''t know how to explain. I have 2 relevant interfaces. eth0 is external, eth1 is internal. My internal LAN is 10.10.10.0/24. My External range is 1.2.3.0/27 (dummied up). I have an H.323 videoconference device inside my internal

Here is a puzzle. I have a network with several servers. It''s a mess. It''s a /24 and pieces and servers are all over the place inside this /24 block, on both sides of the firewall. For example, 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

I''m working with LEAF boxes as gateway machines. I''m trying to implement Proxy-ARP to build a bandwidth manager for my network. I''ve gone as per the lartc howto to implement a transparent bridge in an existing network and plan to put in my tc script after this. I''m configuring the box as a standalone one before plugging it into the network. I''m getting

Hello everyone, I''m using shorewall successfully on many servers withount any problems and I''m really happy with this great piece of software. But now I ran into a problem with shorewall 3.0.4 on Ubuntu 6.06 running on a vServer. The provider uses virtual interfaces like eth0:vs01 for the customers. The interface eth0 cannot be touched. I''ve read the instructions

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.10 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.10 Nothing Earth-shattering here and there is no reason to upgrade if you are not seeing one of the corrected problems. - ----------------------------------------------------------------------- Problems corrected in version 2.0.10 1) The

On Thu, Apr 11, 2019 at 10:43 PM Vasiliy Tolstov <v.tolstov@selfip.ru> wrote: Hi Vasiliy, > > ср, 10 апр. 2019 г. в 19:46, Ruben Kerkhof <ruben@rubenkerkhof.com>: > > > > On Wed, Apr 10, 2019 at 1:44 PM Laine Stump <laine@redhat.com> wrote: > > > > > > On 4/9/19 11:35 AM, Ruben Kerkhof wrote: > > > > On Tue, Apr 9, 2019 at 5:10 PM

shorewall-users hi,ALL I have a firewall have three interface, one NIC is internal (eth0), second NIC is SSN(eth2), and other NIC is external(eth1), on internal network have 10.0.1.59 and gw 10.0.1.163 eth0: 192.168.1.254/24 eth1: 10.0.1.55/24 gw 10.0.1.163 I use shorewall''s proxyarp 10.0.1.59 eth1 eth0 no no that is OK. I saw /usr/share/shorewall/firewall, I

In kernel 2.6.31, the handling of the rp_filter interface option was changed incompatibly. Previously, the effective value was determined by the setting of net.ipv4.config.dev.proxy_arp logically ANDed with the setting of net.ipv4.config.all.proxy_arp. Beginning with kernel 2.6.31, the value is the arithmetic MAX of those two values. Additionally, a ''loose'' routefiltering

/-----------------------\ | | |eth0 |eth0 |-------| |-------| | |eth1 eth1 | | -------- A |____ _______| B |----- | | \ / | | --------| | | --------| | | | |

Hello, I''m facing a rather strange problem with the netback interface. My setup involves a netvm, which has some physical network interfaces assigned, and a client VM where a net front is running (exposed as eth0) and which is connected to that netvm (via vif42.0 interface, as seen in the netvm on the dumps below). Now, the netvm has two physical network interfaces assigned: 1) A

Package: xen-utils-common Version: 4.0.0-1 Severity: important When Xen is configured in routed mode, restarting xend fails because the script hotplugpath.sh is missing. Please see below for more information. *** root at eliott:~# /etc/init.d/xend restart Restarting Xen daemons: xend/etc/xen/scripts/network-route: line 20: /etc/xen/scripts/hotplugpath.sh: No such file or directory

Package: xen-utils-3.2-1 Version: 3.2.0-5 Severity: important $vifnum is undefined when this is called. Starting XEN control daemon: xend/etc/xen/scripts/network-route: line 27: /proc/sys/net/ipv4/conf/eth/proxy_arp: No such file or directory /etc/xen/scripts/network-route: line 27: /proc/sys/net/ipv4/conf/eth/proxy_arp: No such file or directory /etc/xen/scripts/network-route: line 27:

ср, 10 апр. 2019 г. в 19:46, Ruben Kerkhof <ruben@rubenkerkhof.com>: > > On Wed, Apr 10, 2019 at 1:44 PM Laine Stump <laine@redhat.com> wrote: > > > > On 4/9/19 11:35 AM, Ruben Kerkhof wrote: > > > On Tue, Apr 9, 2019 at 5:10 PM Michal Privoznik <mprivozn@redhat.com> wrote: > > >> > > >> On 4/9/19 4:38 PM, Ruben Kerkhof wrote:

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 | | | |__________| | __________|________________________________

I''m rate limiting and prioritizing traffic upstream of a slow wan link using htb, classic wonder shaper type stuff. I''m using the following command for traffic that does not match any of my defined filters: tc qdisc add dev eth0 root handle 1: htb default 50 It appears that local, non-routable traffic like arps and igmp are being snared by this and end-up queued in the lowest

On Wed, Apr 10, 2019 at 1:44 PM Laine Stump <laine@redhat.com> wrote: > > On 4/9/19 11:35 AM, Ruben Kerkhof wrote: > > On Tue, Apr 9, 2019 at 5:10 PM Michal Privoznik <mprivozn@redhat.com> wrote: > >> > >> On 4/9/19 4:38 PM, Ruben Kerkhof wrote: > >>> Hi all, > >>> > >>> I have a hook script, /etc/libvirt/hooks/network,