Resp.: Resp.: Resp.: network problem- can't resolve hosts
Yeah, for whatever reason, the amd64 version is "ping-less." Strange
that such a basic tool would be left out...
2008/11/2, John Knight <jknight@geminimicro.com>:
> Robert Hayes wrote:
>>
>> Success! Or at least so far. The connection problem was a typical noob
>> mistake: I uncommented
>> the dhcp section in /etc/network/interfaces, and everything is working
>> correctly. It's just a question of checking the configuration files.
>> Of course I'm now getting HAL errors...
>> Thanks for the help!
>>
>>
>> 2008/11/1, Robert Hayes <el.capiango@gmail.com>:
>>
>>>
>>> I'm on Debian Sid right now, and looking in the kfreebsd partition I
>>> don't see anything named ping
>>> in /bin/, nor is there anything in /usr/bin/ named ping. I'll boot
>>> into kfreebsd and try the commands
>>> anyway to make sure. I'll keep you posted.
>>>
>>>
>>> 2008/11/1, John Knight <jknight@geminimicro.com>:
>>>
>>>>
>>>> Robert Hayes wrote:
>>>>
>>>>>
>>>>> I can't ping at all- it spits out "unrecognized command". I would
>>>>> never have believed it, but it seems that the tool isn't installed
>>>>> (and won't be until I can get apt-get to connect). Sorry I didn't
>>>>> mention it in the original email.
>>>>> I'm in Debian Sid right now, but here's what the file contains:
>>>>> # Sample /etc/network/interfaces file for GNU/kFreeBSD
>>>>>
>>>>> auto lo0
>>>>> iface lo0 inet loopback
>>>>>
>>>>> # DHCP network (replace ed0 with your interface, if different)
>>>>> #auto ed0
>>>>> #iface ed0 inet dhcp
>>>>>
>>>>> # Static network (replace ed0 with your interface, if different)
>>>>> #auto ed0
>>>>> #iface ed0 inet static
>>>>> # address 192.168.0.3
>>>>> # network 192.168.0.0
>>>>> # netmask 255.255.255.0
>>>>> # gateway 192.168.0.1
>>>>>
>>>>> I'm such a noob. I need to uncomment the DHCP section, don't I ?
>>>>>
>>>>>
>>>>> 2008/11/1, John Knight <jknight@geminimicro.com>:
>>>>>
>>>>>
>>>>>>
>>>>>> Robert Hayes wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> hi, i'm just now starting with Debian GNU/kfreebsd and I've already
>>>>>>> run into a problem. Yay me =(
>>>>>>>
>>>>>>> I installed the amd64 version (the iso is the one that dates to Feb.,
>>>>>>> and it burned correctly), and the installation went without a hitch.
>>>>>>> Upon reboot, no problems. I used "ifconfig -a" and it said that the
>>>>>>> network was up and running (acc. to dmesg the boot process correctly
>>>>>>> identified my network card and loaded the correct modules). But I
>>>>>>> can't connect with anything:
>>>>>>> apt-get update fails, claiming failure to resolve host (on all
>>>>>>> mirrors)
>>>>>>> trying to install the pgp keys fails, saying failure to resolve
>>>>>>> subkeys.pgp.net host
>>>>>>> So, what am I doing wrong here? Is ifconfig wrong, or do I need to
>>>>>>> fill out a bug report?
>>>>>>> thanks for any help you can give me.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> sounds like a dns issue perhaps. can you ping other servers via ip
>>>>>> instead
>>>>>> of hostname? what is the readout of the following command?
>>>>>>
>>>>>> "$ cat /etc/network/interfaces"
>>>>>>
>>>>>> --
>>>>>>
>>>>>> John Knight
>>>>>> phone: +1 706 255-9203
>>>>>> e-mail: jknight@geminimicro.com
>>>>>> website: geminimicro.com
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>> well, this is certainly interesting, hehe
>>>>
>>>> I'm almost positive my last install of kfreebsd had ping installed as
>>>> part
>>>> of the basic system. i could be wrong, but I remember getting the
>>>> networking portion up and running was fairly easy.
>>>>
>>>> I'm sort of clueless as to what exactly is wrong with your system, but
>>>> I'm
>>>> wondering if there is something wrong with the shell configuration
>>>> concerning the /bin/ directroy. Does running the following command give
>>>> any
>>>> results?
>>>>
>>>> "$ ls /bin/ | grep ping"
>>>>
>>>> If so, you might have to type out the entire location of the command and
>>>> its
>>>> argument like the following:
>>>>
>>>> "$ /bin/ping 72.14.207.99"
>>>>
>>>> If not, there might just be a huge issue with the amd64 port. If you
>>>> are
>>>> using a compatible processor, I would recommend using the latest i386
>>>> build
>>>> but that's only because that's the version that I and everyone I've
>>>> known
>>>> to
>>>> run and test kfreebsd has used.
>>>>
>>>>
>>>> --
>>>>
>>>> John Knight
>>>> phone: +1 706 255-9203
>>>> e-mail: jknight@geminimicro.com
>>>> website: geminimicro.com
>>>>
>>
>>
>
> cheers! glad you got it working. I'm still curious though, was the 'ping'
> package just not included?
>
> --
>
> John Knight
> phone: +1 706 255-9203
> e-mail: jknight@geminimicro.com
> website: geminimicro.com
Reply to: