What's the total number of "o"s in:
Q: Limit ARP to gateway IP only My current network setup is as follows
auto lo
iface lo inet loopback
    dns-nameservers 8.8.8.8 8.8.4.4

auto eth0
iface eth0 inet static
address 104.244.72.242/32
gateway 107.189.30.113
pointopoint 107.189.30.113
netmask 255.255.255.255

I was having an issue before where ARP would end up connecting to 104.244.72.1 causing issues I fixed that by adding
net.ipv4.conf.all.arp_announce=1
net.ipv4.conf.all.arp_ignore=2

arp now connects/returns only to
Address                  HWtype  HWaddress           Flags Mask            Iface
107.189.30.113           ether   00:16:cd:0b:1e:7c   C                     eth0
107.189.30.1             ether   0c:81:26:30:b8:78   C                     eth0

However this is causing issues still. How can I get it to only connect to 107.189.30.113
To add this environment is from within a nested virtual machine Proxmox node network is as follows
auto lo
iface lo inet loopback

iface ens3 inet manual

auto vmbr0
iface vmbr0 inet static
        address 107.189.30.113/24
        gateway 107.189.30.1
        bridge-ports ens3
        bridge-stp off
        bridge-fd 0
post-up ip route add 104.244.72.242/32 dev vmbr0
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up echo 1 > /proc/sys/net/ipv4/conf/all/proxy_arp

The host I am with does do MAC filtering. I am trying to next-hop the connection.

A: Depending on your environment, I think you might want to look into how to limit access to and from your system with a local endpoint firewall.
I would consider ufw, iptables, ipfilter or similar, depending on which Linux / BSD / Unix flavor you have installed.
Also, arp may not be the source of your issues. You should probably look at your routing table. You do not describe the nature of your issues, hence it is not easy to lead you to a solution.

user
I counted 111 "o"s in that text.
assistant