Tag Info

New answers tagged

0

I have seen similar messages in the log an did the following: to /etc/ufw/before.rules I added \# allow igmp codes from my local sub-net -A ufw-before-input -p igmp -m ttl --ttl-eq 1 -j ACCEPT and to /etc/ufw/before6.rules \# allow multicast group membership maintenance -A ufw6-before-output -p icmpv6 --icmpv6-type 130 -m hl --hl-eq 1 -j ACCEPT -A ...


0

Best to build the kernel manually the following is set for iptables module: # Networking options # CONFIG_PACKET=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=y CONFIG_XFRM_SUB_POLICY=y CONFIG_XFRM_IPCOMP=y CONFIG_NET_KEY=y CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y ...


1

Impressive as it was not established where the traffic comes. -s IP -i Interface Examples: sudo iptables -t nat -A PREROUTING -s 192.168.150.1 -p tcp --dport 80 -j DNAT --to-destination 192.168.150.1:80 sudo iptables -t nat -A PREROUTING -i wlan0 -p tcp --dport 80 -j DNAT --to-destination 192.168.150.1:80


0

I found another solution using iptables. iptables command to limit connections: iptables -A INPUT -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP you can exclude one ip: iptables -A INPUT -p tcp --syn --dport 80 -d ! 127.0.0.1 -m connlimit --connlimit-above 20 -j DROP I hope this is helpful for you.


0

Here's what I've learned: A Linux bridge is a misnomer... In the brctl world, a bridge behaves more like the switch of the networking world. Bridges are smart, in the sense they figure out what MAC addresses are attached to it and only forward ethernet frames to the bridge member that has a matching MAC address for efficiency. This is the behavior you'd ...


1

There are two things you should do to keep that system accessible before changing netfilter-rules: create an exception in the firewall rules for ssh from your machine create a safeguard create an exception create an appropriate rule with iptables sudo iptables -A INPUT -p tcp --dport ssh --source-address yourextIPadd -j ACCEPT (where yourextIPadd is ...


1

You can't... at least using an IP based connection protocol. Because your rule drops all incoming IP traffic coming to the gateway. BTW, all protocols I know like ssh, vnc, rdp and so on, use IP.


0

I cannot help you doing this with iptables, but the following does the trick: For TCP you could use redir: redir --lport=502 --cport=502 --caddr=192.168.1.50 [--debug] You can add --laddr to bind it to your interface. Else it would accept connections from any interface. For UDP you could use socat: sudo socat UDP4-RECVFROM:30718,fork ...


0

Test this: sudo su nano /usr/bin iptables-nat Paste these lines #! /bin/sh /sbin/iptables -F /sbin/iptables -A INPUT -i lo -j ACCEPT /sbin/iptables -A INPUT -s 192.168.99.0/24 -i em1 -j ACCEPT /sbin/iptables -t nat -A POSTROUTING -s 192.168.99.0/24 -o em2 -j MASQUERADE ** Save file - Control + O ** Close nano - Control + X chmod +x ...



Top 50 recent answers are included