New answers tagged

1

I don't think iperf is be flexible enough to simulate user activity for various traffic types. Depending on how you're using pfsense (routing, gateway, proxy, whatever) it will experience different load types. So I would rather stick to one of the following tools: Apache JMeter - this one have GUI and doesn't require programming skills Grinder - this guy ...


0

Try adding nameserver to your interfaces file under eth0: dns-nameservers 8.8.8.8


0

Needed to delete the character ; at the end of the query to get it to work. Didn't understand why, but "select * from nagioscheck;" returned an error and "select * from nagioscheck" works.


-1

Add the scrpit in /etc/rc.d/rc.local file, The script will be automatically executed during boot.


3

No, this is not possible in the sense of a "normal" CPU. You could use CUDA or a similar library if supported on your GPU chip, but that is not at all useful for general server tasks. However, most servers that are not designed for GPU computing have very weak GPUs and wouldn't offer any real benefit anyway.


0

Let's say you want to execute example.service at booting time, you'd do: vi /etc/systemd/system/example.service with this content: [Unit] Description=Example After=network.target [Service] Type=simple WorkingDirectory=/var/lib/example ExecStart=/usr/local/bin/example --pid /var/run/example.pid --core unlimited -c /etc/example/example.ini ...


0

When you configure your eth0 interface in /etc/network/interfaces you need to use ifup and ifdown to bring it up and down. These commands are used to configure (or, respectively, deconfigure) network interfaces based on interface definitions in the file /etc/network/interfaces. Bring eth0 interface up: ifup eth0 Bring eth0 interface down: ifdown eth0


0

For devices are managed by Network Manager can use the utility nmcli nmcli dev list iface eth0 | grep IP4-SETTINGS.GATEWAY: | awk '{ print $2}' For ppp0 in my case it's 0.0.0.0


5

Setting an upper limit for packet size was done for two reasons: ensure reliable transmission of the data (longer data are more susceptible to being corrupted and their CRC have lower changes of detecting/correcting the corruption); ensure that all Ethernet-compliant device have at least a 1500 byte buffer to send/receive packets. As you suggested, the ...


1

Found this googling a bit: Ethernet frame has 8 byte preamble, 6 byte source and 6 byte destination mac address, mac type of 2 bytes, and 4 bytes CRC. Assuming the MTU payload to be 1500 the total number of bytes comes to 1500 + 8 + 6 + 6 + 2 + 4 = 1526 bytes. Now between each frame there is a inter frame gap of 12 bytes which constitues 9.6micro ...


0

For the ppp0 device you can query the IP address of the peer with ip addr show ppp0. However, you don’t even need one, as for a point-to-point device like ppp0 you can simply set the route only to the interface, omitting the router IP.


0

As @Alex mention netstat -r, if that's not available there is also another way: $ ip route list dev eno1 default via X.X.X.X proto static metric 100 X.X.X.X/24 proto kernel scope link src X.X.X.X metric 100 $ replace eno1 with your device. dhclient -R routers - I can't test it, as I don't have dhcp set-up anywhere.


0

This command will give you all the routes set in your Linux machine, including gateway: route -n


0

Try running netstat -nr as opposed to netstat -r. Same for route, run route -n instead. This will show the actual IP address instead of the hostname.


0

So, it turned out that my problem is caused by this bug. The solution seems to be to update the ESX hosts's drivers.


0

Apparently I have to start it WITHOUT --network-veth? It's working now, but I don't understand it anymore so I won't mark this as accepted. Feel free to post something useful.


0

Using such configuration only traffic addressed to B is secured. When I try to send something from A to C - it is on the whole path insecured. That's exactly how it should be. You established a Transport Mode IPsec SA between A and B, which means there are IPsec policies that only apply for traffic between these two hosts. If you want to secure traffic ...


0

Disabling Enhanced C1 (C1E) in the BIOS fixed it for me. Not sure if the lower power state of C1E is messing with the driver, or that there's an oops in the driver when the processor is in this state. Anyway, problem solved.


0

You should check if interrupt coalescing is enabled. To check, issue ethtool -c <devname> (and report back here the result) To enable coalescing, issue ethtool -C <devname> adaptive-rx on; ethtool -C <devname> adaptive-tx on


1

You can achieve this by using virtualization, either with a bare-metal hypervisor (ESXi, Hyper-V, KVM) or containers (Solaris Zones, *BSD Jails, Linux LXC), depending if you need different operating systems for your servers. There is much debate over if this is a smart or terrible idea, so I won't lecture you on it much. There a guides out there how to ...


3

Have you considered the possibility that your local system is already infected and has a keylogger on it that records all your passwords etc.? Especially if your adversaries may be targeting you directly? I would suggest the following: Use a secure local system, for example a system booted from an officially purchased LiveCD (or just a friend you know has ...


2

The bug is in the Version: 6.1.2 of nuttcp For more information and fix read this link https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745051 My suggestion is to use a new version. mkdir nuttcp cd nuttcp/ wget http://nuttcp.net/nuttcp/beta/nuttcp-7.3.3.c If you don’t have gcc sudo apt-get install build-essential manpages-dev compile program and run ...


0

Edit the file /etc/sysctl.conf net.ipv4.ip_forward = 0 reload sysctl -p /etc/sysctl.conf masquerade your private IP as your public when you go out to the internet (whichever interface owns the public IP) iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE Nat imcoming requests back to you VM and port - presumably a bridge or tap device. iptables -t ...


0

Update: Installation of Spice client needs the following (Linux, Kubuntu) - spice-client - spice-vdagent - (optional) spice-vdagent (Windows - Works well with Windows10): Windows binaries Then you need to open ports on your host: 5900 (unsecure), 5901 (secure - needs additional configuration). I did this with gufw, a very simple tool to build a ...


0

I actually just had to figure this out a few weeks ago. I did it using the netem box as a router, but I don't think that actually matters much. Basically, the netem function that you want (there's more than just that) will tell your nic to hold onto the traffic for some user-determined amount of time. It is not concerned with how the traffic gets to the ...


0

You can use ssh HOST nc as a proxy: Host *.saturnin.* *.saturnin bb-* ProxyCommand ssh -q -A saturnin.lab.eng.brq.redhat.com nc %h %p IdentityFile ~/.ssh/bot_rsa User root Drawback: this requires having entries in /etc/hosts on the host. Alternatively I am using nc with sed to get local name/IP: Host tbb-* ProxyCommand ssh -q -A ...


0

You cannot connect these VMs directly to one another. If you want them to be on an isolated virtual network, created a NAT network (or use libvirt's default network), assign all the private network based NICs to that network, and give them IPs that will be able to ping each other.


0

This should be very simple. If you are on NAT, then you simply need a forward rule that would send the packets to 192.168.122.1, that's the host's IP on the libvirt default network. If you are using a bridged setup, make sure the host bridge has an IP, and redirect the packets there. All the configuration needs to be done on the guest.


0

Found the solution. Created Outbound NAT rule on the LAN interface. Source is tunnel network, destination is LAN network. Source IP is always firewall IP, but that's something I can live with.


0

The iptables packetfilter drops the responses of the 10.0.0.0/8 ips to the 192.168.0.0/8 IPs. Add a rule to allow packets from 10.0 to 192.168 that are already established, before the DROP rule: -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT That should do the trick. If not, remove the DROP rule to check if that is really the origin of the ...


1

I'm assuming you are referring to this tutorial. With linux bridge, you are going to use your netem box as a switch, without even an ip but for management. This way, the client is going to communicate straight to your server. As long as you don't specify subinterfaces (eg eth0.101), your switch will forward all vlan tagged traffic as-is.


0

Thinking about this some more, I realized that it probably had to do with the reply trying to go over the 130.10 interface. I set that interface to another RFC private subnet 172.16.x.x that I wasn't using, and restarted networking. Just like that, 130.x hosts could connect to the 122.10 address. That is fine, because in production, the second interface ...


3

Your setup will probably do what you want, once you have a service listening on the concerned port(s). Iptables is a packet filter, not a connection endpoint.


0

Recent Linux kernels have the feature that you ask for. If you configure the kernel, set CONFIG_IPV6_ROUTER_PREF, see Networking support -> Networking options -> The IPv6 protocol -> Router Preference (RFC 4191) support. You may need to recompile the kernel if your distro defaults to switch this feature off.


1

The libvirt is using TUN device for this purpose. You can manually create this device by following command: # /usr/bin/tunctl -t virbr0-nic


1

I once had the same issue on a server. CentOS didnt add the route automaticly because the gateway is not in the same subnetmask (i guessed). You need to add a persistent/static route. CentOS documentation can be found here: https://www.centos.org/docs/5/html/5.2/Deployment_Guide/s1-networkscripts-static-routes.html Try the following for your route-eth0 ...


0

Those are most certainly failed connection attempts. Check out with tcpdump; you should see them along with your host's ICMP port unreachable (since you don't have anything listening on that port): 01:58:31.471535 IP some.remote.host.24053 > your.local.host.21095: UDP, length 35 01:58:31.472006 IP your.local.host > some.remote.host: ICMP ...


0

I hate iptables -L output. not sure how anyone reads it. iptables-save is king and iptables -S will usually do in a pinch. (Just personal anecdotes). Let's run through the troubleshooting process: Iptables As far as I can tell the only DROP statement in your firewall is never referenced. (EG: unreachable). If port 80 is working without a special firewall ...


-2

Go to Control Panel > Network and Sharing Center > Change adapter Settings > Right Click "Local Area Connection" > Properties Disable "Internet protocol Version 6 (TCP/IPv6)" Disable "Link-Layer Topology Discovery Mapper I/O Driver" Disable "Link-Layer Topology Discovery Responder" I had Ping spikes from 30ms up to 3000ms, sometimes even "Ping request ...


1

Bridging and routing are not the same. Bridging happens at a lower layer than routing. Essentially bridging behaves like a switch. The virtual switch implemented by the Linux bridging code will have one interface attached to the upper layers of the network stack as well as a number of physical interfaces. So in your case where there are two physical ...



Top 50 recent answers are included