Networking :: Ping Hangs When Specifying Interface Option
Feb 10, 2009
I am working on a project that needs to know that an interface is up and has stable connectivity so I am told by higher ups that I am going to use ping to solve this. So I was writing something much like the ping program to send out ping packets to [URL]. The issue comes in the fact that I need to do this for every interface that is currently up. So I mimic the code from iputils version of ping to tie the socket to an interface and everything works well except I don't get any packets returned to me.
So digging further I opened wireshark and indeed my interface is getting the ICMP echo response packets but linux (ubuntu 8.10) isn't passing the packet up. So I tried running "sudo ping -I ppp0 www.google.com" and the exact same behavior happens here too. (also seen but not solved here: [URL]. Also my iptables in empty and I also have a wifi connection which is my default gateway in addition to the 3G ppp0 connection. It is not a routing issues cause when I collect packet on the given interface I see the packets that should be there.
The entry in the routing table for ppp0 is: (dst)68.28.xx.yy (gateway)0.0.0.0 (genmask)255.255.255.255 (flags)UH (metric)0 (ref)0 (use)0 (Iface)ppp0
So I was wondering if anyone would either A) be willing to spend a minute to check and see if they are able to ping with the -I option and if so let me know if their routing has entries for that interface (route -n) or B) if anyone has any ideas on why the system isn't passing the packet up to the socket?
I have 2 NICs on my computer connected to 2 different networks. On 1 interface i wish to disable the return of ping and on the other interface i wish to still allow ping. Is this possible? Both interfaces need to be able to send and receive data. I know that you can disable ping in /etc/sysctl.conf but is there a way to set the ping value for a specific interface only?
I have an ubuntu server that I am using as a gateway router. I have 2 nics in the machine and am using iptables to run the NAT.I now have a need to provide several machines on the inside of the network with their own public IP. So I created a virtual interface on the the WAN card and attempted a 1:1 nat across it, but it's not working. The virtual interface isn't even responding to pings. If I ping the ip of the virtual interface from the outside, it doesn't work. If I run a tcpdump on the interface, I can see ICMP request packets but no replies. Watching the same dump while pinging the non-virtual interface IP results in both request and reply packets. What's stranger the inbound ICMP request packets on the virtual interface seem to be hit or miss. Sometimes when I ping it, I can see the request packets hitting the interface, sometimes I get nothing.
I've configured an FC14 installation and have been able to do everything over the internet as needed. Then I added a VPN client and can connect to the VPN. I can't ping a server I know is available on the VPN. Ping hangs, not getting any response (including timing out).My other Linux box (running all of the same software) can get to the server on the other side of the VPN so I know everything is okay except for my configuration.I had the same problem when I originally configured the other system and remember that I had to manually edit some setting in a file but don't remember what it was.
So I keep reading that bonding ethernet devices is supposed to be easy. I have followed several tutorials and tried a few things on my own, and I can't seem to get it right. I currently have a setup that allows me to ping internally on my network, but when I try to ping externally I get the error: connect: Network is unreachable
Before I bonded the interface my connection worked fine. Here are my config files. I am running centos 5.3 on a virtual machine. /etc/sysconfig/network-scripts/ifcfg-bond0
I am using an virtual machine. where I need to ping from one machine to another. earlier I was able to ping. But after going to google.com once, I cannot ping back to this machine.
But if I gave ping -I eth1 <IP> then I can ping.
I cannot install any package, so tell me solution which includes not installing any package.
I have managed to configure a wireles PCI card on CentOS 5.3 and it seems to work fine. It is a off brand (Hercules) with a Ralink RT61 chipset. I installed the most current driver (RT2501PCI/mPCI/CB(RT61:RT2561/RT2561S/RT2661) from the rt2x00 Open Source Project. I now have a question that might be very simple for one or more of you to answer. When I issue the command "shutdown -h now", the machine starts to come down and brings down eth0 cleanly, but when it attempts to bring down wlan0, the machine hangs and never brings down the interface OR powers off the box. The only way to complete the power off is to "hard" power off the machine.
I have two machines on this network, one running Ubuntu and the other running Fedora.
When I'm using the Wireless network on the Ubuntu machine, I cannot ping the Fedora machine. Everything else works. I can browse the net fine.
If I switch over to the Wired Network then I can ping the other machine.
I don't understand why ping doesn't work only over the Wireless. I can ping the router so I'm guessing it's getting blocked by the router but I didn't block ICMP traffic.
I tried asking on IRC and they ran out of ideas too to find out where the problem is.
I just installed my first EVER bind DNS server. I am running bind9 on Ubuntu 10.04. Everything seems to be working great except one thing: If I ping a host that I have set up in bind by its HOSTNAME the pings take 5-6 seconds to reply/print to the screen between each echo response. If I ping by the host's IP address, they echo back very quickly.
I have read that IPv6 can cause this, but I have disabled it in /etc/sysctl.conf and the problem still exists.
I know everyone says this can't be a DNS issue, but this never was an issue with dnsmasq (which i was using prior), and it doesn't make sense that the ping are ONLY slow when pinging by hostname and not IP.
Configs below:
Ping by hostname - there is a 5-6 second delay between each one of the responses:
Code:
Ping by IP - the responses come VERY quickly one after the other:
So, I have an Virtual Machine running CentOS 5.4. It sits behind a hardware firewall which also does NAT'ing. I've set up plenty of these, so I know for sure the firewall and NAT rules are set up correctly. From the host, I can ping anything in my subnet and the gateway. But I can't ping anything else beyond the gateway. I can perform DNS queries and when I try to ping, it finds the appropriate IP address.But from the outside, I can ping the PUBLIC address (It's a 1 public to 1 private address NAT, not 1 public to multiple private). I've tried it with IPTABLES on and off, with no change.
I have Mandriva One 2009.0 (192.168.1.100) on one box and Mandriva Free 2010.0 (192.168.1.118) on the other. I can ping router (192.168.1.1) from both of these boxes but I can't ping one box to the other and the other way around. What's going on?.
Do I have to change some settings in router?. Or is it firewall issue on those two machines?. Both of these boxes are connected by cable. Symbol of the router: TL-WR340G.
recently I have installed a suse 10 sp2 on my computer. I have a big problem about connecting to my ADSL Router. The problem is that I can't ping the router at all and the Kinternet log is prompted that
status is: disconnected trying to connect to smpppd connect to smpppd Status is: disconnected error: cannot read real interface for eth-bus-pci-0000:04:00.0
I can easily open the web page of my router with windows OS but in the suse I can not do that with firefox.
I just had an ATT Uverse RG installed. However my Smoothwall router that previously worked fine with the ADSL SpeedStream is no longer accepting an address assignment DHCP ip address from this new gateway. (3800HGV-B)Any thoughts ideas or experience working with this hardware? ATT only supports Windows and Mac
I have connected xp and fedora through crossover cable . xp has ip address 192.168.0.1/24 (manually assigned) fedora has 192.168.0.2/24 with default route equal to 192.168.0.1
I can ping fedora from xp computer but i can't able to ping xp from fedora computer.
I have manully edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file with correct subnet mask and ip address because when i tried to give ip address manully in network manager the subnetmask is replaced with gateway address don't know why.
Now i want to share internet through crossover cable . xp is connected to internet through wireless usb adapeter.
I have the same problem with an Ubuntu 10.04 live CD. Whenever I attempt to boot (Lu|U)buntu from a live CD/USB, on most computers. it works just fine. However, on two computers, the live media starts off just fine with the main menu (Try Ubuntu without installing, etc.), then, when I select any option except 'Boot from First Hard Disk', after a few seconds, the CD stops spinning or the USB loses power. I'm convinced it's not a problem from the media, since it works perfectly fine on some computers.
Sysinfo: Code: Host Name: OWNER-PC OS Name: Microsoftr Windows VistaT Home Premium OS Version: 6.0.6001 Service Pack 1 Build 6001 OS Manufacturer: Microsoft Corporation
I try to ping with php : exec("ping -n 1 $ip",$output[],$retval); it works fine in window. but in linux i got this error : ping: icmp open socket: Operation not permitted are there any ways to solve this ?
I'm running an Acer 1810Tz, dual boot with win7.Under 9.10 and Grub I had no boot issues, however I have just completed the upgrade to 10.04 and upgraded GRUB to GRUB2.Everything boots just fine into Ubuntu, and my GRUB menu looks right, but when I select the Windows 7 option, the machine just hangs with a black screen, white cursor top left. I'm sure this is a trivial problem, something overwritten that shouldn't have been perhaps, but I have no clue where to start.
I've started facing the weirdest problem. I have to restart the ethernet interface a couple of times a day and everytime i do that the server locks up completely and i have to hard reboot it.info: recently shifted to a new server, all new components and new installation, OS version CentOS 5.6
This applies to my 2 opensuse PC's, my Windows PC is fine.I can ping a hostname, say "PC1" but I can not ping PC1.domain.local (even the host PC can not ping it's own FQDN). When I ping just the hostname the ping stats even list the FQDN.Onto the next issue, since all my PC's, have the domain prefix domain.local, my Synology can not. I can ping it's IP and that is it. I can resolve it's name with nmblookup just fine tho and that is what is killing me. How is this not resolving.Even weirder, I can browse to "Synology" in Network Servers under places on the slab.
I can connect to the internet and browse. I'm wired and using DHCP on a Windows network. Updating Ubuntu or downloading programs takes hours for 52MB of updates. Why? I read some articles that mention Network Manager needs to be enabled at the .conf file. Can I edit this using GUI or command line only?
I am trying to get a Linux (Slackware 13.37) working in a Windows networking environment. The IT support for this organisation does not extend to Linux support, so I'm limited in what help I can get for this.
I'm trying to get to the point where I can get to the internet to download what I need on this Linux machine.
The situation is this (*fictitious addresses used) -My Linux machine uses a fixed IP address (10.100.150.21) My Windows machine uses a DHCP assigned IP address (10.100.150.213)Both Linux and Windows machine are configured to access the gateway server (10.100.150.1)So, I can ping the Linux machine from the Windows machine and vice-versa.I can ping the gateway machine from the Windows machine.I can browse Windows Shares on the network via SMB from the Linux machine.I CANNOT ping the gateway machine from the Linux machine with the Destination Host Unreachable message being the error message.
For actual internet access I need to access a proxy server but since the Linux machine can't even ping the gateway server, it fails to ping the proxy.Now, I have been told the gateway is a HW based router and for Windows machine they use some software for authentication to connect to the network. This software isn't available for Linux, so that's why I've been told to use a fixed IP address.My experience of networking is pretty basic and most of the Linux setup is done via running Slackware's setup program.
I have a debian server installed with a static ip. Now i am able to ping my ip, but when i try to configure a domain name with the nameserver as my ip, i am not able to ping the domain name
I installed nss-mdns in Fedora Core 10 and can see all the Bonjour published hosts on the lan. However, I am always forced to append the .local domain when referring to a host:
I have an IBM Bladecenter HS21 with 3 blade servers. All 3 blade servers were initially installed with RedHat Linux 4. I then installed ixMOS on one of the blade servers, and Mandriva Linux was also installed (over RedHat) automatically along with ixMOS.
Now, I have some network problems. The other 2 servers with RedHat can ping each other, but it appears that the server with ixMOS/Mandriva Linux is isolated, that is, I can't ping the other 2 servers from it, and I can't ping it from the other 2 servers.
Does anyone have any ideas on what is wrong and how I can solve this problem? One more thing, my installation of Mandriva Linux has no GUI, so I have to do everything using the command line interface.
