Re: download cvsup?
Tim Dunphy wrote: hey listers!! sorry for all the trouble.. just as an FYI it turned out to NOT be a DNS issue at all!!! it was a routing issue... this command apparently did the trick... [r...@lbsd2:/usr/home/bluethundr]#/etc/rc.d/routing restart add net default: gateway 192.168.1.1 [r...@lbsd2:/usr/home/bluethundr]#ping google.com PING google.com (173.194.33.104): 56 data bytes 64 bytes from 173.194.33.104: icmp_seq=0 ttl=55 time=14.083 ms 64 bytes from 173.194.33.104: icmp_seq=1 ttl=55 time=14.537 ms 64 bytes from 173.194.33.104: icmp_seq=2 ttl=55 time=14.531 ms sometimes it's the simplest solutions under our noses. :) Sorry for not getting back any sooner, went camping in the mountains for a bit. Glad to hear it is resolved. The above is accomplished via this: defaultrouter=192.168.1.1 in your /etc/rc.conf. If you are using this machine as a gateway for the other machines and it is between your FIOS router and the other machines, the defaultrouter value for the other machines would point to the gateway box's internal facing address. -Mike ___ 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: download cvsup?
thanks for the suggestion! but the other machines on this network do not use the FreeBSD machine as a router. They merely reference it as their first choice of DNS servers. So as of now networking is good to go for all machines. best!! On Thu, Oct 28, 2010 at 2:32 AM, Michael Powell nightre...@hotmail.com wrote: Tim Dunphy wrote: hey listers!! sorry for all the trouble.. just as an FYI it turned out to NOT be a DNS issue at all!!! it was a routing issue... this command apparently did the trick... [r...@lbsd2:/usr/home/bluethundr]#/etc/rc.d/routing restart add net default: gateway 192.168.1.1 [r...@lbsd2:/usr/home/bluethundr]#ping google.com PING google.com (173.194.33.104): 56 data bytes 64 bytes from 173.194.33.104: icmp_seq=0 ttl=55 time=14.083 ms 64 bytes from 173.194.33.104: icmp_seq=1 ttl=55 time=14.537 ms 64 bytes from 173.194.33.104: icmp_seq=2 ttl=55 time=14.531 ms sometimes it's the simplest solutions under our noses. :) Sorry for not getting back any sooner, went camping in the mountains for a bit. Glad to hear it is resolved. The above is accomplished via this: defaultrouter=192.168.1.1 in your /etc/rc.conf. If you are using this machine as a gateway for the other machines and it is between your FIOS router and the other machines, the defaultrouter value for the other machines would point to the gateway box's internal facing address. -Mike ___ 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 -- Here's my RSA Public key: gpg --keyserver pgp.mit.edu --recv-keys 5A4873A9 Share and enjoy!! ___ 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: download cvsup?
hey listers!! sorry for all the trouble.. just as an FYI it turned out
to NOT be a DNS issue at all!!!
it was a routing issue...
this command apparently did the trick...
[r...@lbsd2:/usr/home/bluethundr]#/etc/rc.d/routing restart
add net default: gateway 192.168.1.1
[r...@lbsd2:/usr/home/bluethundr]#ping google.com
PING google.com (173.194.33.104): 56 data bytes
64 bytes from 173.194.33.104: icmp_seq=0 ttl=55 time=14.083 ms
64 bytes from 173.194.33.104: icmp_seq=1 ttl=55 time=14.537 ms
64 bytes from 173.194.33.104: icmp_seq=2 ttl=55 time=14.531 ms
sometimes it's the simplest solutions under our noses. :)
Sincere thanks for all your input and all your help!
On Fri, Oct 22, 2010 at 11:01 PM, Tim Dunphy bluethu...@gmail.com wrote:
guys,
thanks for the input. busy couple of days sorry for not following up sooner.
at any rate, I tried many suggestions.
Here is the current state of things:
This is a working resolv.conf on the rest of the network which are
CentOS machines:
[r...@lbsd2:/usr/home/bluethundr]#cat /etc/resolv.conf
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 71.250.0.12
nameserver 4.2.2.2
I rsync'ed this file to the bsd server from a CentOS machine and this
is what happens when you try to resolve internally, then externally
(also tried editing it manually of course):
[r...@lbsd2:/usr/home/bluethundr]#host bsd2
bsd2.summitnjhome.com has address 192.168.1.44
[r...@lbsd2:/usr/home/bluethundr]#host sum1
sum1.summitnjhome.com is an alias for lCent01.summitnjhome.com.
lCent01.summitnjhome.com has address 192.168.1.42
[r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com
ping: cannot resolve yahoo.com: Host name lookup failure
this is how my named.conf looks:
options {
// Relative to the chroot directory, if any
directory /etc/namedb;
pid-file /var/run/named/pid;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
Also i notice it's
[r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com
ping: cannot resolve yahoo.com: Host name lookup failure
with forwarders commented out
and
[r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com
PING yahoo.com (72.30.2.43): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
with forwarders enabled:
forwarders {
71.250.0.12; 4.2.2.2;
};
or even just
forwarders {
192.168.1.1;
};
enabled.. I'm still quite puzzled.. I'm hoping that this problem won't
require me to backup my most important configurations (DNS, LDAP,
Apache) and reinstall.. cuz that's uhmmm.. cheating! ;) not to mention
a pain in the firggin' arse... guh
// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
#listen-on { 127.0.0.1; };
listen-on { 127.0.0.1; 192.168.1.44; };
allow-recursion {127.0.0.1; 192.168.1.0/24;};
On Wed, Oct 20, 2010 at 5:38 AM, Michael Powell nightre...@hotmail.com
wrote:
Dick Hoogendijk wrote:
Are the forwarders in your named.conf file OK?
That was the next thing I was about to suggest. His FIOS router should be
running DNS itself by default, with it pointing to Verizon's name servers.
So he could try using 192.168.1.1 in his named.conf forwarders directive.
This would just recurse out to Verizon's name servers and should get a basic
external resolution going, provided he has not altered the default router
setup.
Example from mine: (don't just cut and paste but adjust as required)
options {
directory /etc/namedb;
pid-file /var/run/named/pid;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
listen-on { 127.0.0.1; 192.168.10.1; };
allow-recursion {127.0.0.1; 192.168.10.0/24;};
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
forwarders {
208.67.222.222; 208.67.220.220; 192.168.1.1;
};
// query-source address * port 53;
};
---/ Below are snipped out zone file directives for my local stuff /---
The first two IP addresses in my forwarders clause are for OpenDNS. You
could delete them so as to only have 192.168.1.1 and your FreeBSD's DNS
server will then forward requests to your FIOS router which will then
request from Verizon. Use of the listen-on and allow-recursion is not
necessary, but if you decide to utilize make sure they reflect values which
apply to your situation. Do rndc reload or reboot to take effect.
I think he has some other issues pending as well, but one thing at a time.
:-)
-Mike
Re: download cvsup?
guys,
thanks for the input. busy couple of days sorry for not following up sooner.
at any rate, I tried many suggestions.
Here is the current state of things:
This is a working resolv.conf on the rest of the network which are
CentOS machines:
[r...@lbsd2:/usr/home/bluethundr]#cat /etc/resolv.conf
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 71.250.0.12
nameserver 4.2.2.2
I rsync'ed this file to the bsd server from a CentOS machine and this
is what happens when you try to resolve internally, then externally
(also tried editing it manually of course):
[r...@lbsd2:/usr/home/bluethundr]#host bsd2
bsd2.summitnjhome.com has address 192.168.1.44
[r...@lbsd2:/usr/home/bluethundr]#host sum1
sum1.summitnjhome.com is an alias for lCent01.summitnjhome.com.
lCent01.summitnjhome.com has address 192.168.1.42
[r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com
ping: cannot resolve yahoo.com: Host name lookup failure
this is how my named.conf looks:
options {
// Relative to the chroot directory, if any
directory /etc/namedb;
pid-file/var/run/named/pid;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
Also i notice it's
[r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com
ping: cannot resolve yahoo.com: Host name lookup failure
with forwarders commented out
and
[r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com
PING yahoo.com (72.30.2.43): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
with forwarders enabled:
forwarders {
71.250.0.12; 4.2.2.2;
};
or even just
forwarders {
192.168.1.1;
};
enabled.. I'm still quite puzzled.. I'm hoping that this problem won't
require me to backup my most important configurations (DNS, LDAP,
Apache) and reinstall.. cuz that's uhmmm.. cheating! ;) not to mention
a pain in the firggin' arse... guh
// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
#listen-on { 127.0.0.1; };
listen-on{ 127.0.0.1; 192.168.1.44; };
allow-recursion {127.0.0.1; 192.168.1.0/24;};
On Wed, Oct 20, 2010 at 5:38 AM, Michael Powell nightre...@hotmail.com wrote:
Dick Hoogendijk wrote:
Are the forwarders in your named.conf file OK?
That was the next thing I was about to suggest. His FIOS router should be
running DNS itself by default, with it pointing to Verizon's name servers.
So he could try using 192.168.1.1 in his named.conf forwarders directive.
This would just recurse out to Verizon's name servers and should get a basic
external resolution going, provided he has not altered the default router
setup.
Example from mine: (don't just cut and paste but adjust as required)
options {
directory /etc/namedb;
pid-file /var/run/named/pid;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
listen-on { 127.0.0.1; 192.168.10.1; };
allow-recursion {127.0.0.1; 192.168.10.0/24;};
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
forwarders {
208.67.222.222; 208.67.220.220; 192.168.1.1;
};
// query-source address * port 53;
};
---/ Below are snipped out zone file directives for my local stuff /---
The first two IP addresses in my forwarders clause are for OpenDNS. You
could delete them so as to only have 192.168.1.1 and your FreeBSD's DNS
server will then forward requests to your FIOS router which will then
request from Verizon. Use of the listen-on and allow-recursion is not
necessary, but if you decide to utilize make sure they reflect values which
apply to your situation. Do rndc reload or reboot to take effect.
I think he has some other issues pending as well, but one thing at a time.
:-)
-Mike
___
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
--
Here's my RSA Public key:
gpg --keyserver pgp.mit.edu --recv-keys 5A4873A9
Share and enjoy!!
___
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: download cvsup?
Are the forwarders in your named.conf file OK? ___ 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: download cvsup?
Dick Hoogendijk wrote:
Are the forwarders in your named.conf file OK?
That was the next thing I was about to suggest. His FIOS router should be
running DNS itself by default, with it pointing to Verizon's name servers.
So he could try using 192.168.1.1 in his named.conf forwarders directive.
This would just recurse out to Verizon's name servers and should get a basic
external resolution going, provided he has not altered the default router
setup.
Example from mine: (don't just cut and paste but adjust as required)
options {
directory /etc/namedb;
pid-file/var/run/named/pid;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
listen-on { 127.0.0.1; 192.168.10.1; };
allow-recursion {127.0.0.1; 192.168.10.0/24;};
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
forwarders {
208.67.222.222; 208.67.220.220; 192.168.1.1;
};
// query-source address * port 53;
};
---/ Below are snipped out zone file directives for my local stuff /---
The first two IP addresses in my forwarders clause are for OpenDNS. You
could delete them so as to only have 192.168.1.1 and your FreeBSD's DNS
server will then forward requests to your FIOS router which will then
request from Verizon. Use of the listen-on and allow-recursion is not
necessary, but if you decide to utilize make sure they reflect values which
apply to your situation. Do rndc reload or reboot to take effect.
I think he has some other issues pending as well, but one thing at a time.
:-)
-Mike
___
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: download cvsup?
This is the current state of affairs: [r...@lbsd2:/usr/home/bluethundr]#host bsd2 bsd2 has address 199.101.28.20 Host bsd2 not found: 3(NXDOMAIN) [r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com PING yahoo.com (69.147.125.65): 56 data bytes ping: sendto: No route to host ping: sendto: No route to host I made sure these services were commented out or set to no in /etc/rc.conf and /etc/defaults/rc.conf and that they were not running [r...@lbsd2:/usr/home/bluethundr]#ps auxwww | grep rpcbind root1781 0.0 0.1 3492 1212 5 S+ 12:12AM 0:00.00 grep rpcbind [r...@lbsd2:/usr/home/bluethundr]#ps auxwww | grep nfs_server root1783 0.0 0.1 3492 1216 5 S+ 12:13AM 0:00.00 grep nfs_server [r...@lbsd2:/usr/home/bluethundr]#ps auxwww | grep nfs_client root1785 0.0 0.1 3492 1216 5 S+ 12:13AM 0:00.00 grep nfs_client [r...@lbsd2:/usr/home/bluethundr]# Once I was sure those services weren't running I tried these flavors of /etc/fstab: [r...@lbsd2:/usr/home/bluethundr]#cat /etc/resolv.conf domain summitnjhome.com nameserver 192.168.1.44 nameserver 71.250.0.12 nameserver 4.2.2.2 With this here config I can resolve internally but not externally [r...@lbsd2:/usr/home/bluethundr]#host bsd2 bsd2.summitnjhome.com has address 192.168.1.44 [r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com ping: cannot resolve yahoo.com: Host name lookup failure [r...@lbsd2:/usr/home/bluethundr]# With this suggested config I actually get neither internal nor external resolution! [r...@lbsd2:/usr/home/bluethundr]#host bsd2 bsd2 has address 199.101.28.20 ^^ Not any ip that's on MY network! ;) Host bsd2 not found: 3(NXDOMAIN) [r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com PING yahoo.com (72.30.2.43): 56 data bytes ping: sendto: No route to host ping: sendto: No route to host And if I'm not resolving externally I really wonder how I get THAT IP [r...@virtcent05:~]#whois 199.101.28.20 [Querying whois.arin.net] [whois.arin.net] # # Query terms are ambiguous. The query is assumed to be: # n 199.101.28.20 # # Use ? to get help. # # # The following results may also be obtained via: # http://whois.arin.net/rest/nets;q=199.101.28.20?showDetails=trueshowARIN=false # NetRange: 199.101.28.0 - 199.101.31.255 CIDR: 199.101.28.0/22 OriginAS: NetName:SKYE-1 NetHandle: NET-199-101-28-0-1 Parent: NET-199-0-0-0-0 NetType:Direct Assignment NameServer: AUTH1.SKYEBYNOMINUM.COM NameServer: AUTH2.SKYEBYNOMINUM.COM RegDate:2009-03-20 Updated:2009-03-20 Ref:http://whois.arin.net/rest/net/NET-199-101-28-0-1 OrgName:SKYE OrgId: NOMIN-4 Address:2000 Seaport Blvd. Address:Suite 400 City: Redwood City StateProv: CA PostalCode: 94063 Country:US RegDate:2009-03-11 Updated:2009-03-11 Ref:http://whois.arin.net/rest/org/NOMIN-4 Weird man... Back to this config: [r...@lbsd2:/usr/home/bluethundr]#cat /etc/resolv.conf domain summitnjhome.com nameserver 192.168.1.44 nameserver 71.250.0.12 nameserver 4.2.2.2 It's back to the same old routine of resolving internally but not externally! [r...@lbsd2:/usr/home/bluethundr]#host bsd2 bsd2.summitnjhome.com has address 192.168.1.44 [r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com ping: cannot resolve yahoo.com: Host name lookup failure [r...@lbsd2:/usr/home/bluethundr]#nslookup sum1.summitnjhome.com Server: 192.168.1.44 Address:192.168.1.44#53 sum1.summitnjhome.com canonical name = lCent01.summitnjhome.com. Name: lCent01.summitnjhome.com Address: 192.168.1.42 My gateway is a FiOS router at 192.168.1.1 I have a semi-fancy netgear switch that provides wired connectivity to my farm of 6 machines. 1) FreeBSD (God machine) that is SSH gateway, DNS/BIND server, OpenLDAP server, Apache22 server and MySQL 5.1 server. 2) Centos 1 machine - host xen instances that are stored on a san 3) Centos 2 machine - hosts the rest of the xen instances all of which are stored in the same NFS nas mount (/mnt/store/xen). 4) FreeNAS 1 5) FreeNAS 2 6) Client machine (non server) The BSD really kinda runs the show I use that as the base from which to operate. But now it's hobbled with only semi-functioning DNS! Thanks for your help!!! On Tue, Oct 19, 2010 at 1:00 AM, Michael Powell nightre...@hotmail.com wrote: Tim Dunphy wrote: 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. [r...@lbsd2:/usr/ports]#ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,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 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseT full-duplex)
Re: download cvsup?
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. [r...@lbsd2:/usr/ports]#ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,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 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseT full-duplex) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST metric 0 mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 [r...@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 nfsrsize=32768,wsize=32768,timeo=14,intr 192.168.1.44:/mnt/store /mnt/store nfsrsize=32768,wsize=32768,timeo=14,intr 192.168.1.44:/mnt/home /home nfsrsize=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! [r...@lbsd2:/usr/ports]#cat /etc/resolv.conf domain summitnjhome.com nameserver 192.168.1.44 nameserver 4.2.2.2 [r...@lbsd2:/usr/ports]#ping yahoo.com ping: cannot resolve yahoo.com: Host name lookup failure [r...@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 nightre...@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. [r...@lbsd2:/usr/home/bluethundr]#/etc/rc.d/netif restart Stopping Network: lo0 bge0 plip0. lo0: flags=8048LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 bge0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,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=8810POINTOPOINT,SIMPLEX,MULTICAST metric 0 mtu 1500 Starting Network: lo0 bge0. lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,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 0xff00 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
Re: download cvsup?
Tim Dunphy wrote:
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.
[r...@lbsd2:/usr/ports]#ifconfig
bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=9bRXCSUM,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 0xff00 broadcast 192.168.1.255
media: Ethernet autoselect (1000baseT full-duplex)
status: active
^
OK - I see it is truly up.
plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST metric 0 mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
options=3RXCSUM,TXCSUM
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff00
[r...@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.
Even with IPv6 enabled things should still function even though IPv6 may not
actually be in use. Sometimes it happens with DNS lookups it will try
looking for an record first [IPv6], then time out and fall back to the
normal IPv4 A record. This will just show as a short wait period and
ultimately eventually resolves.
I suspect that you are not even getting this far and the problem is
something else. Just for the sake of simplifying things you could eliminate
IPv6 from the picture if you are truly not using it. However, I do not think
it is actually the cause (I could always be wrong here).
[snip - forgetting about csup and ports for now]
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
This truly has me confused. In the above ifconfig output it is showing an IP
address assigned of 192.168.1.44 netmask 0xff00 broadcast 192.168.1.255.
What I do not understand at all is why you would be wanting to NFS mount
from 192.168.1.44 *to* 192.168.1.44, as indicated by the above fstab
entries.
Again, for the sake of simplification with divide and conquer, make sure all
mountd, rpcbind, nfs_server, and nfs_client daemons are deactivated.
Eliminate all things superfluous to troubleshooting the DNS problem. Once
DNS gets fixed you can add stuff back one at a time.
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.
Yes - leave fstab with no remote mounting/NFS stuff for now.
/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!
You should be able to ping by IP any/all machines within your local network.
Sounds like this does work, but confirm and don't 'assume'. Next try and
ping by IP to a host out on the Internet. Since you cannot resolve any names
here is the IP to www.netbsd.org: 204.152.190.12. If you cannot ping by
IP out from your network to the outside you do not have basic gateway
connectivity working. If this is the case it will have to get fixed first.
[r...@lbsd2:/usr/ports]#cat /etc/resolv.conf
domainsummitnjhome.com
nameserver192.168.1.44
nameserver 4.2.2.2
[r...@lbsd2:/usr/ports]#ping yahoo.com
ping: cannot resolve yahoo.com: Host name lookup failure
If you are attempting this from the same machine as you are running BIND on,
it might be better for it's resolv.conf to look like this instead:
nameserver 127.0.0.1
nameserver 192.168.1.1
192.168.1.1 is my FIOS router which has it's own DNS server. It is also
pointed at the same OpenDNS servers as my forwarders directive (a snippet
from my named.conf below:)
listen-on { 127.0.0.1; 192.168.10.1; };
allow-recursion {127.0.0.1; 192.168.10.0/24;};
forwarders {
208.67.222.222; 208.67.220.220; 192.168.1.1;
};
My local DNS on my gateway/firewall box is a hybrid which only has zones for
my local .test.zip 192.168.10.0/24 LAN. All other requests get forwarded out
and cached. Here is what sockstat -4l looks like on this box:
bind named 835 20 tcp4 192.168.10.1:53 *:*
bind named 835 21 tcp4 127.0.0.1:53 *:*
bind named 835 22 tcp4 127.0.0.1:953 *:*
bind named 835 512 udp4 192.168.10.1:53 *:*
bind named 835 513 udp4 127.0.0.1:53 *:*
I do not listen on the
download cvsup?
hello, I accidentally deleted my ports tree thinking that cvsup was already installed. it wasn't. :( 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. [r...@lbsd2:/usr/home/bluethundr]#/etc/rc.d/netif restart Stopping Network: lo0 bge0 plip0. lo0: flags=8048LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 bge0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,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=8810POINTOPOINT,SIMPLEX,MULTICAST metric 0 mtu 1500 Starting Network: lo0 bge0. lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,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 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (none) status: no carrier [r...@lbsd2:/usr/home/bluethundr]#cat /etc/resolv.conf domain summitnjhome.com nameserver 192.168.1.44 nameserver 151.202.0.84 nameserver 4.2.2.2 [r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com ping: cannot resolve yahoo.com: Host name lookup failure [r...@lbsd2:/usr/home/bluethundr]#host bsd2 bsd2.summitnjhome.com has address 192.168.1.44 I've cycled the network interface (bge0) several times now and even bounced the host to no avail. Thoughts? thanks! -- Here's my RSA Public key: gpg --keyserver pgp.mit.edu --recv-keys 5A4873A9 Share and enjoy!! ___ 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: download cvsup?
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. [r...@lbsd2:/usr/home/bluethundr]#/etc/rc.d/netif restart Stopping Network: lo0 bge0 plip0. lo0: flags=8048LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 bge0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,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=8810POINTOPOINT,SIMPLEX,MULTICAST metric 0 mtu 1500 Starting Network: lo0 bge0. lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,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 0xff00 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: download cvsup?
On Sun, 17 Oct 2010 23:44:42 -0400 Tim Dunphy bluethu...@gmail.com wrote: I accidentally deleted my ports tree thinking that cvsup was already installed. it wasn't. :( csup is part of the system, no need to use cvsup from the ports any longer. 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. For a start take a look at the cable/connection. media: Ethernet autoselect (none) status: no carrier Andreas -- GnuPG key : 0x2A573565|http://www.gnupg.org/howtos/de/ Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565 pgpx4ZwAOBVFk.pgp Description: PGP signature
