At 10:12 PM 12/22/2003, Barney Wolff wrote:
>It is odd that libalias picks a port number, and then, if the "use sockets"
>option is set, tries to open a socket on that port. Perhaps if the above
>option is set, it should bind port 0 and use the port the kernel assigns.
>
>If folks think that's a
On Mon, Dec 22, 2003 at 06:33:31PM -0600, Mike Silbersack wrote:
>
> On Fri, 12 Dec 2003, Brett Glass wrote:
>
> > It is also interesting that natd doesn't respect the
> > "hifirst..hilast" settings here. Shouldn't it look at
> > these variables and avoid assigning ports that the
> > machine on w
On Fri, 12 Dec 2003, Brett Glass wrote:
> net.inet.ip.portrange.lowfirst: 1023
> net.inet.ip.portrange.lowlast: 600
> net.inet.ip.portrange.first: 1024
> net.inet.ip.portrange.last: 5000
> net.inet.ip.portrange.hifirst: 49152
> net.inet.ip.portrange.hilast: 65535
>
> Why is "lowfirst" greater tha
Hi,
On Mon, Dec 22, 2003 at 02:12:16PM -0700, Mark Ogden wrote:
> I have built 0.35.9 and 0.35.10 on 4.9 and 4.8.
If you take a look at net/arla/Makefile, you can see why
it's broken in ports. It requires kernel sources and kerberos.
-Kirill
pgp0.pgp
Description: PGP signature
Synopsis: process exits but socket is still ESTABLISHED
State-Changed-From-To: open->feedback
State-Changed-By: andre
State-Changed-When: Mon Dec 22 13:10:42 PST 2003
State-Changed-Why:
Asking whether this is still a problem.
Responsible-Changed-From-To: freebsd-net->andre
Responsible-Changed-B
Mark Ogden on Mon, Dec 22, 2003 at 02:06:14PM -0700 wrote:
> Kirill Ponomarew on Mon, Dec 22, 2003 at 10:02:04PM +0100 wrote:
> > Hi,
> >
> > On Mon, Dec 22, 2003 at 01:48:06PM -0700, Mark Ogden wrote:
> > > Has anyone out there built arla on 5.1?
> >
> > If you meant net/arla, it's broken.
>
>
Hi,
On Mon, Dec 22, 2003 at 01:48:06PM -0700, Mark Ogden wrote:
> Has anyone out there built arla on 5.1?
If you meant net/arla, it's broken.
-Kirill
pgp0.pgp
Description: PGP signature
Has anyone out there built arla on 5.1?
--
Mark L Ogden
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
< said:
> As long as the chipsets are compliant, an 8 wire straight thru cable
> works as both a straight and a crossover. The GigE standard requires
> this behaviour.
"Crossover" isn't meaningful in the case of GigE: both stations
transmit and receive simultaneously on all four paris.
-GAWollm
Current FreeBSD problem reports
Critical problems
S Submitted Tracker Resp. Description
---
o [2002/03/09] conf/35726 net Won't let me use ifconfig on the interfac
1 problem total.
Serious problems
You can only transparently proxy unencrypted data streams. There is no
point in proxying port 443 because the SSL protocol is designed to
prevent exactly this from being possible.
So port 443 is out.. but there are a few others that are still viable..
and it's not very hard to setup.
Make sure yo
Hi folks,
I am using a FreeBSD server as transparent proxy server. To make this I use
ipfw to foward port 80 requests.
I have a doubt, I like that 443, 8080, 8000, 8081 ports and FTP pass through
proxy too.
How can I make this?
Thanks and regards.
Eicke.
12 matches
Mail list logo