download cvsup?

Tue Oct 19 02:42:37 UTC 2010

Thanks guys! But to give more background the host in question IS
networking, at this point  I can ssh into and out of it.. I just can't
resolve externally.

[root at LBSD2:/usr/ports]#ifconfig
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
	ether 00:14:22:38:9e:eb
	inet6 fe80::214:22ff:fe38:9eeb%bge0 prefixlen 64 scopeid 0x1
	inet 192.168.1.44 netmask 0xffffff00 broadcast 192.168.1.255
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=3<RXCSUM,TXCSUM>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
	inet 127.0.0.1 netmask 0xff000000
[root at LBSD2:/usr/ports]#

 Also the rest of the network is currently working. I am writing this
to you from another machine on the same network as the bsd machien.

 I was able to download the ports tarball from the freebsd ftp site
and scp it over to the bsd host.  so that minor crisis has been
solved. (grin).

 But it is still quite necessary for me to get this host resolving
external hosts of course!

 And yes I now realize that csup is part of the base system. But in
order for me to use it I must resolve!

 Not sure how this might have cause this but I edited my fstab file
with some nfs mounts like so:

192.168.1.44:/mnt/nas    /mnt/nas   nfs    rsize=32768,wsize=32768,timeo=14,intr
192.168.1.44:/mnt/store /mnt/store nfs    rsize=32768,wsize=32768,timeo=14,intr
192.168.1.44:/mnt/home  /home      nfs    rsize=32768,wsize=32768,timeo=14,intr

And when I rebooted the host pretty much it all went haywire! LDAP,
DNS, Apache, MySQL, and even ALL NETWORKING which normally started
with the host stopped working. I now have to start each one by hand
whatever I try I can't seem to resolve external hosts, tho.

 So I restored the fstab file from backup and still I am stuck not resolving.

 /etc/resolv.conf looks ok to me so I would think I that I could ping
out of the network. Sadly this is not the case!

[root at LBSD2:/usr/ports]#cat /etc/resolv.conf
domain	summitnjhome.com
nameserver	192.168.1.44
nameserver      4.2.2.2
[root at LBSD2:/usr/ports]#ping yahoo.com
ping: cannot resolve yahoo.com: Host name lookup failure

[root at LBSD2:/usr/ports]#ping sum1.summitnjhome.com
PING lCent01.summitnjhome.com (192.168.1.42): 56 data bytes
64 bytes from 192.168.1.42: icmp_seq=0 ttl=64 time=0.273 ms
64 bytes from 192.168.1.42: icmp_seq=1 ttl=64 time=0.180 ms
64 bytes from 192.168.1.42: icmp_seq=2 ttl=64 time=0.186 ms

 thanks for your continued assistance with this problem!

On Mon, Oct 18, 2010 at 1:56 AM, Michael Powell <nightrecon at hotmail.com> wrote:
> Tim Dunphy wrote:
>
>> hello,
>>
>>  I accidentally deleted my ports tree thinking that cvsup was already
>> installed. it wasn't. :(
>
> csup is cvsup rewritten with C and exists in the base system. You no longer
> need to install cvsup, just use csup.
>
>>  I seem to be having a little trouble resolving external hosts tho my
>> trusty named server on this host is working fine to resolve the local
>> network. I need to reinstall my ports with sysinstall but to do that i
>> need to resolve externally of course. I think this problem could use a
>> fresh set of eyes.
>
> You do not have to use sysinstall just to install ports. It is available as
> a tarball you can download and decompress. Use csup afterwards for an update
> to ensure you have pulled in any changes which may have occurred after the
> tarball was generated.
>
> You will, of course, need to get your network working first.
>
>>  [root at LBSD2:/usr/home/bluethundr]#/etc/rc.d/netif restart
>> Stopping Network: lo0 bge0 plip0.
>> lo0: flags=8048<LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>> options=3<RXCSUM,TXCSUM>
>> inet6 ::1 prefixlen 128
>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
>> bge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
>> options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
>> ether 00:14:22:38:9e:eb
>> inet6 fe80::214:22ff:fe38:9eeb%bge0 prefixlen 64 scopeid 0x1
>
>> media: Ethernet autoselect (none)
>> status: no carrier
> ^^^^^^^^^^^^^^^
>
>> plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
>> Starting Network: lo0 bge0.
>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>> options=3<RXCSUM,TXCSUM>
>> inet6 ::1 prefixlen 128
>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
>> inet 127.0.0.1 netmask 0xff000000
>> bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>> options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
>> ether 00:14:22:38:9e:eb
>> inet6 fe80::214:22ff:fe38:9eeb%bge0 prefixlen 64 scopeid 0x1
>> inet 192.168.1.44 netmask 0xffffff00 broadcast 192.168.1.255
>
>> media: Ethernet autoselect (none)
>> status: no carrier
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Your network interface isn't connecting to anything, such as a hub, switch,
> or another computer via crossover cable at the physical layer. You need to
> fix this first, then worry about why the DNS is not working.
>
> Start with simple things such as substituting a known good cable from a
> working machine. Examine the LEDs on both the NIC and the hub/switch.
> Usually these will not be lit if there is no link. Is the hub/switch
> defective? Or locked up? I've seen hubs and switches lock up and a power
> cycle would make them operate again, for a while. Hubs or switches that lock
> up have an intermittent defect and should not be depended upon for the long
> run.
>
> Verify if you are using the correct driver. What version is the OS? Search
> bug reports and mail lists for known issues, e.g. such as someone else
> reported a problem with quite similar symptoms and the devs have already
> addressed it in HEAD and possibly MFC'd it to STABLE.
>
> Of course, if there is a fix you can't get at it until your network works.
> But you can also back up the train and tell us things like: did it used to
> work? and what did you do, or change, that made it begin not working? Some
> more details might give the 'fresh set of eyes' more to work with.
>
>
> [snip]
>
> -Mike
>
>
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>

-- 
Here's my RSA Public key:
gpg --keyserver pgp.mit.edu --recv-keys 5A4873A9

Share and enjoy!!