Re: Bridge, networking, wireless cards, and ypbind.... (*sigh*

2006-06-10 Thread Wes Santee
Paul Pathiakis wrote: On Saturday 10 June 2006 01:00, you wrote: Paul Pathiakis wrote: Seems that once I rebooted, both interfaces came up in promiscuous mode, so that's a no go now. I still believe it to be a frag/UDP/RPC issue. Wes do you or anyone else have any further insight?

Re: Bridge, networking, wireless cards, and ypbind.... (*sigh*

2006-06-09 Thread Wes Santee
Paul Pathiakis wrote: my rc.conf has: ifconfig_ath0=inet 192.168.1.24 netmask 0xff00 ssid my_ap mode 11g mediaopt adhoc defautrouter=192.168.1.12 nis_client_enable=YES ifconfig -a shows: ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6

Re: hosts.allow ?

2006-03-19 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Karol Kwiatkowski wrote: Gerard Seibert wrote: Chris Maness wrote: Also, sshd can't be started in rc.conf, it has to be started in inetd.conf. Make sure you do a /etc/rc.d/inetd restart after you make changes. Just out of curiosity, why can

Re: How to Stop Bruit Force ssh Attempts?

2006-03-18 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris Maness wrote: In my auth log I see alot of bruit force attempts to login via ssh. Is there a way I can have the box automatically kill any tcp/ip connectivity to hosts that try and fail a given number of times? Is there a port or

Re: hosts.allow ?

2006-03-18 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris Maness wrote: I tried running sshd off of inetd instead of in daemon mode. It still didn't work. here is the file: Notice anything strange about the top? # Start by allowing everything (this prevents the rest of the file # from

cbq not borrowing fully from parent queue

2006-03-14 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Greetings. I'm running 6-STABLE using pf and altq/cbq to manage bandwidth on my wireless adapter. The setup from pf.conf is this: altq on $ext_if bandwidth 54Mb cbq queue { internal, external } queue internal bandwidth 53104Kb priority 7

Re: Building a Jail in FreeBSD or NetBSD for a hosting environment

2006-02-27 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Nick Larsen wrote: [snip] Also do I need an individual IP for each jail? because each physical server will have 1 IP unless the customer requests a dedicated IP. Any help would be appreciated, and I have tried to research it but end up going

Re: dovecot-1.0.alpha5 + mysql

2006-02-24 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 fa wrote: Hi. Sorry if this is a wrong place to ask. I've just compiled dovecot-1.0.alpha5 with mysql support.from freebsd ports (FreeBSD 6.0-RELEASE). It looks like dovecot has problems connecting to mysql. In the log I'm getting: dovecot:

linux-expat fails to install

2006-02-03 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello! I'm doing a general ports update using portmanager -u on my 6-STABLE box. This is from a portsnap updated today. Portmanager updated linux-base to 8.8.0_12, and is now trying to update linux-expat (no version change, just because it was

Gnome port forcing Apache 2.0 on me during install

2005-12-15 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Greetings, I run Apache 1.3+ssl on a computer that I'm installing Gnome 2.12.2 via the meta-port in x11/gnome2. As part of that install, it builds and installs www/gnome-user-share. *That* port forces the www/apache20 port upon me. Since my

Re: Gnome port forcing Apache 2.0 on me during install

2005-12-15 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Michael C. Shultz wrote: | On Thursday 15 December 2005 10:32, Wes Santee wrote: | |Greetings, | |I run Apache 1.3+ssl on a computer that I'm installing Gnome 2.12.2 via |the meta-port in x11/gnome2. As part of that install, it builds

Portmanager 0.3.9 asserting

2005-11-25 Thread Wes Santee
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Just updated to portmanager 0.3.9 from 0.3.7 and now every command (except --help) is causing an assert: $ sudo portmanager --version rParseCommandLine 0.3.9_1 $ sudo portmanager --status MGdbRead error: unable to open file

Removing pre-6.0 libraries

2005-11-12 Thread Wes Santee
Greetings! I've done a buildworld/kernel/installworld/mergemaster update from 5.4-STABLE to 6.0-RELEASE. Everything went without a hitch. I'm in the process of completely rebuilding all my installed ports (portmanager -u -f). After that, I'll be removing 'options COMPAT_FREEBSD5' from my

Re: Removing pre-6.0 libraries

2005-11-12 Thread Wes Santee
dick hoogendijk wrote: On Sat, 12 Nov 2005 12:35:51 -0800 Wes Santee [EMAIL PROTECTED] wrote: I'm in the process of completely rebuilding all my installed ports (portmanager -u -f). After that, I'll be removing 'options COMPAT_FREEBSD5' from my kernel. Is there anything else I'll need to do

LAN unreachable after 5.3 install

2004-11-15 Thread Wes Santee
Greetings all, I've just completed update from 4.9 to 5.3 and so far not much is working. I went the format and install route to minimize incompatibilities. After the install, the first thing I wanted to do was get my network up and running. I've got a pretty standard setup: LAN on one NIC,

Re: LAN unreachable after 5.3 install

2004-11-15 Thread Wes Santee
On Mon, 15 Nov 2004 12:39:49 +, Josh Paetzel [EMAIL PROTECTED] wrote: On Monday 15 November 2004 18:22, Wes Santee wrote: my problem is that after install, I can't see my LAN. From the FreeBSD box I try this: ping -S 10.0.0.1 10.0.0.254 but none of the pings are responded

Re: [SOLVED] LAN unreachable after 5.3 install

2004-11-15 Thread Wes Santee
On Mon, 15 Nov 2004 11:02:11 -0800, Wes Santee [EMAIL PROTECTED] wrote: On Mon, 15 Nov 2004 12:39:49 +, Josh Paetzel [EMAIL PROTECTED] wrote: On Monday 15 November 2004 18:22, Wes Santee wrote: my problem is that after install, I can't see my LAN. From the FreeBSD box I try

Re: how to make bind listen only to 127.0.0.1

2003-01-06 Thread Wes Santee
On Mon, Jan 06, 2003 at 11:20:53PM +0100, Wiroth Didier wrote: Hey, I would like to run bind as a caching only server (v 8.3.3 from 4.7-release). I would also like that it only listens on port 127.0.0.1, but how? I tried this entry in named.conf, but it didn't work: query-source address