Re: LAN w/ 2 Hubs
OK, I'll bite. Based on your questions I would say that you're fairly novice. If this is something that needs to work well right away I would simply use the uplink between the hubs. On that note, I would also purchase switches instead of hubs. Entry level switches are about the same price. If you've got time and you yearn to learn, set up the backbone using an extra NIC in the FreeBSD box. This will give you a change to learn about NAT / Firewalls and routing. Luke On Feb 9, 2004, at 10:21, Elsie Rae Bryan wrote: We are in the design phase for a small business LAN and want to use FreeBSD as our DSL router/gateway/firewall/DHCP. We need to run a backbone cable to a second hub in an adjacent building. Rather than connecting the two hubs via a switch box, can a third NIC be used to connect the second hub or should the second hub be connected thru the up-link port on the first hub? We are leaning toward LinkSys products for all our hardware (nics, adapters, hubs) and would appreciate any advice on hardware selection. This is our first eMail, please advise if we aren't following the appropriate protocol. Thanks eRae ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: dig/named - res_nsend: Protocol not supported
Yes, it was an IPV6 address in my hosts file. Had I specified the loopback IP instead of 'localhost' it would have worked. Luke Begin forwarded message: From: Saint Aardvark the Carpeted [EMAIL PROTECTED] Date: February 7, 2004 12:09:52 PST To: Luke Cowell [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: dig/named - res_nsend: Protocol not supported Luke Cowell disturbed my sleep to write: *Why* do I need to have IPV6 enable ? Is it some configuration option of named that I overlooked ? Hm...it could be that named is only listening on IPv6 localhost (::1) rather than IPv4 (127.0.0.1) by default, but that seems strange to me. Try grep localhost /etc/hosts and see if you've got entries for both. Are you running the default version of BIND, or a version from ports? Hugh -- Saint Aardvark the Carpeted [EMAIL PROTECTED] Because the plural of Anecdote is Myth. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dig/named - res_nsend: Protocol not supported
Ignore my previously stated question. What I meant to say was: *Why* do I need to have IPV6 enable ? Is it some configuration option of named that I overlooked ? On Feb 6, 2004, at 9:23, Luke Cowell wrote: Hi I'm running FreeBSD 4.9 and I'm having a little difficulty with named/dig. %uname -a FreeBSD polo.asap.bc.ca 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #1: Thu Feb 5 16:23:04 PST 2004 [EMAIL PROTECTED]:/usr/src/sys/compile/POLO i386 Here's what's happening. %dig @localhost ; DiG 8.3 @localhost ; (2 servers found) ;; res options: init recurs defnam dnsrch ;; res_nsend: Protocol not supported So, I did some reading this is an error that is coming up for those trying to enable IPV6 on their system. I'm not trying to do that , so I got the idea to re-enable IPV6 in the kernel. Well, what do you know, I know get normal output when issuing a dig command. My question is what do I need to have IPV6 enable ? Is it some configuration option of named that I overlooked ? Luke ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dig/named - res_nsend: Protocol not supported
Hi I'm running FreeBSD 4.9 and I'm having a little difficulty with named/dig. %uname -a FreeBSD polo.asap.bc.ca 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #1: Thu Feb 5 16:23:04 PST 2004 [EMAIL PROTECTED]:/usr/src/sys/compile/POLO i386 Here's what's happening. %dig @localhost ; DiG 8.3 @localhost ; (2 servers found) ;; res options: init recurs defnam dnsrch ;; res_nsend: Protocol not supported So, I did some reading this is an error that is coming up for those trying to enable IPV6 on their system. I'm not trying to do that , so I got the idea to re-enable IPV6 in the kernel. Well, what do you know, I know get normal output when issuing a dig command. My question is what do I need to have IPV6 enable ? Is it some configuration option of named that I overlooked ? Luke ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dig/named - res_nsend: Protocol not supported
Hi I'm running FreeBSD 4.9 and I'm having a little difficulty with named/dig. %uname -a FreeBSD polo.asap.bc.ca 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #1: Thu Feb 5 16:23:04 PST 2004 [EMAIL PROTECTED]:/usr/src/sys/compile/POLO i386 Here's what's happening. %dig @localhost ; DiG 8.3 @localhost ; (2 servers found) ;; res options: init recurs defnam dnsrch ;; res_nsend: Protocol not supported So, I did some reading this is an error that is coming up for those trying to enable IPV6 on their system. I'm not trying to do that , so I got the idea to re-enable IPV6 in the kernel. Well, what do you know, I know get normal output when issuing a dig command. My question is what do I need to have IPV6 enable ? Is it some configuration option of named that I overlooked ? Luke ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Try to delete files
For academic purposes, I'll provide this explanation.
Use find; this command would delete any files modified more than one year
ago.
Find /usr/ports -mtime +365 -xargs rm -ri {} \;
Luke
From: Nigel Taylor [EMAIL PROTECTED]
Date: Thu, 10 Jul 2003 19:21:42 +0800
To: [EMAIL PROTECTED]
Subject: Try to delete files
Hi all,
Hi, in my years of using freebsd i have collected alot of distfiles in
the ports tree and i want to free up some space on my harddrive and i
was wondering is there a command to delete files in the distfiles folder
that are less than the year 2000?
Or maybe there is a program that deletes all the older releases in the
distfiles? if someone could help i would be gratefully
Thanks
Nigel Taylor
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: funky dns required
If email is your only concern, then there's a much simpler solution. I have
implemented this before and I find it works well. I've only tested this
solution where the smtp server runs on my NAT box (NAT being required is
implicit... Was implicit).
Simply add this line to your nat config
rdr fxp0 0.0.0.0/0 port 25 - 127.0.0.1 port 25
Where fxp0 is the name of the inside interface on your NAT box. This tells
ipnat to redirect any traffic passing over fxp0 on port to redirect to port
25 of localhost.
Even if this implementation isn't suitable for you, I hope it gives you some
alternate ways of looking at this problem.
You may also want to look at your dhcp config and set up default domains for
internal users.
Luke
On 7/6/03 10:59 PM, Andrew Thomson [EMAIL PROTECTED] wrote:
I currently have a caching nameserver on my local domain that really
just caches and forwards to my primary nameserver.
A lot of laptop users connect to the public ip of my mailserver as this
is what they'd use if they were out of the office.
However when they are in the office, it doesn't work so well. I've got
some double nat magic on the firewall to attempt to overcome the problem
however it just doesn't seem to work so well.
As soon as I change the mailserver to the internal ip for these laptop
users, everything works great. However having the laptop users change
this everytime is not a workable solution.
What I want to do is setup on my caching nameserver something so that
when the laptop users requests the public name of my mailserver it
acutally returns the internal ip. Everyone's happy!
I could make the caching nameserver a master for the public domain of my
mailserver however I would also have to keep updating every other host
on the domain.
Can I change the dns for this one host??
mailserver.mydomain.com = public ip
mailserver.int.mydomain.com = private ip
And there's lots of other hosts on mydomain.com.
I want my caching nameserver to resolve mailserver.mydomain.com to
private ip as the only hosts querying this nameserver would be
internal hosts anyway!
Can I just be a master for a host???
zone mailserver.mydomain.com {
type master;
file master/mailserver.mydomain.com;
};
Long winded I know.. hopefully everything's clear!!
Thanks,
ajt.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
