tun-1.1 missing file vnode_if.pl FreeBSD 5.4

2005-10-20 Thread Vincent Stipo
When I try to install tun-1.1 I get a perl error, I'm not sure what to
do. Is there a package that includes vnode_if.pl?

perl \@/kern/vnode_if.pl -h \@/kern/vnode_if.src
Can't open perl script @/kern/vnode_if.pl: No such file or directory
*** Error code 2

--
Vincent Stipo
___
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


hdparm like program for freebsd?

2005-09-27 Thread Vincent Stipo
Is there a hdparm like program which can benchmark individual harddrives.
hdparm -tT
and give the burst rate, allong with sequencial read / write?

--
Vincent Stipo
___
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Problem connecting to http on port 81

2005-09-25 Thread Vincent Stipo
I have a problem connecting to webservers(http) that run on port 81 using
freebsd 5.4
 I can't get it to work with lynx, wget. BitTorrent cant connect to trackers
that run on 81 either.
 I don't have any firewalls or anything installed. I have no clue what the
problem is.
 For example.. my server can access http://filelist.org:80 just fine. but
when i try http://filelist.org:81 it fails to connect.
 Anyone have a clue what is happening here?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problem connecting to http on port 81

2005-09-25 Thread Vincent Stipo
I have a squid proxy running on the server. Don't know how that would affect
anything. When going through the proxy, I can't connect to any port 81
sites. There is no firewall. The server is located at a co-lo, as far as I
know, there shouldnt be any port blocking.
 If I for example.. set up an http daemon on the server to port 81, remote
hosts can connect just fine. So the port cant be blocked, unless there is
some reason they would block outbound tcp on port 81... its a burstable
100mbit pipe. the provider is calpop - http://calpop.com/ I want to find out
if there is somthing wrong with my setup before i send a ticket.

 On 9/25/05, albi [EMAIL PROTECTED] wrote:

 On Sun, 25 Sep 2005 16:09:33 -0700
 Vincent Stipo [EMAIL PROTECTED] wrote:

  I have a problem connecting to webservers(http) that run on port 81
 using
  freebsd 5.4
  I can't get it to work with lynx, wget. BitTorrent cant connect to
 trackers
  that run on 81 either.
  I don't have any firewalls or anything installed. I have no clue what
 the
  problem is.
  For example.. my server can access http://filelist.org:80 just fine. but
  when i try http://filelist.org:81 it fails to connect.

 - are you using any proxy-software or proxy-server from your ISP ?
 - is your ISP blocking port 81 ?
 - your modem or router doesn't have a firewall blocking port 81 ?

 --
 grtjs, albi
 gpg-key: lynx -dump http://scii.nl/~albi/gpg.asc | gpg --import

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


FreeBSD 5.4 Stable - Having problems with remote connections.

2005-09-22 Thread Vincent Stipo
Lets start off by saying I'm new to FreeBSD and im using the 5.4 stable version.

I'm having problems with remote connections.

I tried installing multiple programs that recieve outside connectons.

Squid Proxy
Bittorrent
Battlefield 2 Server

and they start up fine.

I cant connect to squid remotely. I cant download anything with
bittorrent, the bf2 server shows up on the server list but when you
connect you get a connection refused error.

So, is there some kind of default measure in place to stop remote
connections? From as far as I can tell no firewall is running. Do I
have to add the services in inetd?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]