Tag Info

Hot answers tagged

3

as noted in the updates to the question, the problem is that after the kernel passes the packet to whatever raw sockets are listening on that protocol, it then hands it off to any kernel modules registered for that same protocol. since I had been using a sit tunnel on my netbook, the tunnel4 module was still loaded even though I had temporarily set up the ...


1

Whether your IP is assigned via DHCP or static it should not effect how ping operates. Once the IP is assigned ICMP does not care how you got it.


1

Because ISPs choose the most cheapest paths for them. If routing traffic to the ISP (C) for ISP (A) is cheaper through ISP (D) (which is probably a big company with really big links, which sells the traffic in significant volumes and because of that have lower prices) than by ISP (B) (which can be a pretty small ISP with small resources, so they traffic ...


1

Use Route Tables Your route table will be where this is indicated. You should be able to ping either IP on a separate ping operation, without issue, if your PC is aware of where those networks are. If the routes aren't already there, you should be able to add them yourself. Syntax route add -p <network> mask <subnet mask> <gateway> Example ...


1

Start with connectivity from the CentOS box. Can you ping any other hosts on the network? If not, then you need to figure out what's going on there. Is the IP address in the same subnet as the other hosts on the network? You don't give any information about what IP and subnet mask the various hosts are set up with, or what your network looks like, so any ...


1

nmap will give following output though both hosts are not in same subnet ! ashish@ashishk:~/chef-repo/.chef$ nmap -p7 -Pn 172.31.4.235 Starting Nmap 6.40 ( http://nmap.org ) at 2015-08-25 15:25 IST Nmap scan report for 172.31.4.235 Host is up. PORT STATE SERVICE 7/tcp filtered echo Nmap done: 1 IP address (1 host up) scanned in 2.24 seconds But you ...


1

The solution is to set Linux System Capabilites to allow raw socket on the host machine.


1

It looks like tektonic does not have the address 2001:470:1f0e:12a7::2 assigned to its venet0 interface. It is receiving the packets and rejecting them even though they are well-formed. Your next step should be to verify that tektonic can establish TCP connections to IPv6-only hosts such as ipv6.google.com, and that the packets indeed travel to the ...


1

The ICMP errors are send by the kernel because no socket exists to receive protocol 41 packets with that particular combination of source and destination IP address. If a process creates a raw socket with protocol 41, then the kernel will stop producing the ICMP errors. Such a socket by default will receive packets from all source IP send to any destination ...



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