Hot answers tagged

1

Change the onboot value to yes, indicating this device should be activated as boot time. onboot=no to onboot=yes This device should be activated at boot-time


1

When you have the machine working as a hotspot and dhcpd working, you just need to make work as a router - my recommandation is to try finding a guide to setup the version of Fedora you use as a router. It basically comes down to: enable ip forwarding set up routing set up masquerading allow the traffic in whatever firewall you use. I've never used ...


1

The IP 169.254.169.254 is in the network block 168.254.0.0/16 allocated for Automatic Private IP Addressing. It should never be routed to the internet. If your IP address is in the block you will not have direct connectivity to the internet. However, you may be able to use a proxy to connect to sites on the internet. There are a number of mechanisms ...


1

There are a few things to point out about your question's content which should answer you: An IP address does not generate a DNS lookup. It simply generates a connection request that gets routed. The existence of a proxy server on any system does not in itself decide what happens with the traffic. What does is the routing table and firewall rules. The ...


1

If you are sending very small quantities of data at a time then it could happen: For every transmit you will receive an ack, possibly with zero byte payload. For every receive you will transmit an ack, possibly with zero byte payload. For every new connection you will transmit/receive a syn, a syn/ack, and an ack. (probably all with zero payload) There ...


1

You should have correct device name. So change your interface name - if you've changed it to eth0 during installation - to enp5s0 in: /usr/lib/systemd/system/dhcpcd@.service Then you'll be able to enable it. You can bring your interface up by running : ip link set dev enp5s0 up and then obtain an IP from DHCP by running : dhcpcd enp5s0 you can also ...


1

I think this will work: ip route add 10.1.1.1/32 dev eth0 So when you ping 10.1.1.1 it will route via eth0.


1

Inherent limitations The issue could be variable (e.g. congested link to ISP or congestion within ISP). It could also be horrible ("firewall" or even "anti-virus" doing deep packet inspection); the tools below might not show any problem at all. They're worth having, but there is a limit to how much you can achieve just typing commands into a terminal. 2 ...


1

Apparently the problem is that by default, you can only have one default gateway on a system. The case described would lead to asynchronous routing. Solution The iproute2 program, which is included in all current Linux distributions and already installed even, as a rule, can be used for the solution of this problem. Normally, a Linux system only has one ...


1

For anyone who comes across this one another good answer is here http://stackoverflow.com/questions/3130911/tcpdump-localhost-to-localhost, if the traffic that isn't showing up is localhost->localhost traffic. I feel like in other situations I haven't had to do that, but at least a few times I've had to.



Only top voted, non community-wiki answers of a minimum length are eligible