Re: ping: sendto: Can't assign requested address
GLADtr GLADtr wrote:
Hello my friends! Help me please with its problem. I`m don`t understood what
it is problem...
I doubt I do either, but I'll bite.
*mx# uname -a*
FreeBSD mx.taricat.ru 8.0-STABLE FreeBSD 8.0-STABLE #1: Mon Jan 25 09:28:38
UTC 2010 r...@mx.taricat.ru:/usr/obj/
usr/src/sys/GENERIC i386
mx#
*mx# ping 127.0.0.1*
PING 127.0.0.1 (127.0.0.1): 56 data bytes
ping: sendto: Can't assign requested address
ping: sendto: Can't assign requested address
^C
--- 127.0.0.1 ping statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
*mx# ping localhost*
PING localhost (127.0.0.1): 56 data bytes
ping: sendto: Can't assign requested address
ping: sendto: Can't assign requested address
^C
--- localhost ping statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
What does `ifconfig lo0` say? Anything in /var/run/dmesg.today
about lo0?
*mx# ping `hostname`*
ping: cannot resolve mx.taricat.ru: Host name lookup failure
What about `head -n 40 /etc/hosts`? Looks like the
machine can't find its own address. `cat /etc/resolv.conf` ?
*mx# ping google.com*
PING google.com (74.125.87.103): 56 data bytes
64 bytes from 74.125.87.103: icmp_seq=0 ttl=56 time=188.367 ms
64 bytes from 74.125.87.103: icmp_seq=1 ttl=56 time=180.537 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 2 packets received, 33.3% packet loss
round-trip min/avg/max/stddev = 180.537/184.452/188.367/3.915 ms
*mx# ping 10.10.0.113*
PING 10.10.0.113 (10.10.0.113): 56 data bytes
^C
--- 10.10.0.113 ping statistics ---
193 packets transmitted, 0 packets received, 100.0% packet loss
mx#
*mx# ifconfig*
xl0: flags=8843 metric 0 mtu 1500
options=9
ether 00:01:03:09:2e:b4
inet 10.10.0.114 netmask 0xfff0 broadcast 10.10.0.127
media: Ethernet autoselect (100baseTX )
status: active
plip0: flags=8810 metric 0 mtu 1500
lo0: flags=8049 metric 0 mtu 16384
options=3
inet6 fe80::1 prefixlen 64 scopeid 0x3
inet6 ::1 prefixlen 128
nd6 options=3
mx#
OK, you don't have an `inet` (IPv4) address configured
for the lo0 device. That's the issue. Try `ping6 localhost`
or `ping6 ::1`.
*mx# netstat -rn*
Routing tables
Internet:
DestinationGatewayFlagsRefs Use Netif Expire
default10.10.0.126UGS 2 97xl0
10.10.0.112/28 link#1 U 2 465xl0
10.10.0.114link#1 UHS 00lo0
Protocol Family 28:
DestinationGatewayFlagsNetif Expire
(28) 0001 (28)
0001 UH
lo0
(28) fe80 0003
link#3 U lo0
(28) fe80 0003 0001
link#3 UHS lo0
(28) ff01 0003 (28)
fe80 0003 0001 U
lo0
(28) ff02 0003 (28)
fe80 0003 0001 U
lo0
mx#
*mx# less /etc/rc.conf*
hostname="mx.taricat.ru"
#ifconfig_xl0="inet 91.198.171.167 netmask 91.198.171.128"
#defaultrouter="91.198.171.129"
#ifconfig_ste0="inet 10.10.11.100 netmask 255.255.255.0"
#pf_enable=YES
#pf_rules="/etc/pf/conf"
#named_enable=YES
ifconfig_xl0="DHCP"
sshd_enable=YES
#pflog_enable=YES
#clear_tmp_enable=YES
#smartd_enabled=YES
#samba_enable=YES
#nmbd_enable=YES
#smbd_enable=YES
#samba_config="/usr/local/etc/smb.conf"
#zfs_enable="YES"
/etc/rc.conf (END)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ping: sendto: Can't assign requested address
On 1/18/07, Questions <[EMAIL PROTECTED]> wrote: Hello, Let me preface this mail by saying: I'm an idiot. Now that we've gotten that out of the way, you don't have to say it! I have a piece of networking equipment that does not have a "factory defaults" button on it. it has to be RMA'd and returned to the manufacturer if you can't remember login credentials (forgot username,pass/IP, etc) I was assigning the unit an IP address of 172.20.1.x but I typod it. 127.20.1.x and as you can guess, I can't connect to the unit from any other device now. 127.x is loopback. I have tried assigning a 127.20.1.x address to an ethernet interface in a FreeBSD box, and removinging the 127.0.0.1/8 on localhost. I've also gone into the routing table, and removed all traces of routes for 127.x and finally, *tried* creating a route for 127.20.1.x to go out the ethernet interface (link #2) The problem with everything above is: no matter what ip/subnet combination I use, I get a message (when adding the route) that the network is unreachable. Then, when I try to ping the device from the fbsd box, I get "ping: sendto: Can't assign requested address" My question is: Is it possible in any way, to change the 127 routing to pass out my ethernet card long enough to re-ip this device? I haven't yet come up with a decent solution. Thanks for any thoughts, Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" What's the piece of equipment? Is there a serial(comm) port ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: "ping: sendto: Can't assign requested address"
Please disregard the last message, I figured it out. Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
