Showing physical interface addresses of gre tunnel

2003-02-27 Thread Frank Volf 

Hi,

If I configure a gre tunnel, between two end-points, I'm able to view the
point-to-point IP addresses of the tunnel using ifconfig, e.g.:

gre1: flags=b051 mtu 1476
inet6 fe80::2a0:c9ff:fea3:4b75%gre1 prefixlen 64 scopeid 0x5
inet 192.168.254.2 --> 192.168.254.1 netmask 0xff00

Unfortunately, I cannot find a way to show which physical IP addresses I
have configured for the tunnel (i.e. the addresses configured with ifconfig
gre1 tunnel src dst). 

Doe anyone know a command to show these (other than tcpdump :-)?

If it matters, this particular system is using FreeBSD 5.0 RELEASE.

Kind regards,

  Frank

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Re: Performance tuning hints of gigabit networking?

2003-02-27 Thread Attila Nagy 
Hello,

> 3. Usually thttpd use mmap() for caching contents in memory. Our
>service file(only static files) varies from 10k ~
>300Mbytes. Sometimes thttpd denies request with 500 internal error,
>resetting mmap() buffers.
I faced that problem years ago, contacted the authour, who said:
"don't serve big files with thttpd, use something else"

Great.
--[ Free Software ISOs - http://www.fsn.hu/?f=download ]--
Attila Nagy e-mail: [EMAIL PROTECTED]
Free Software Network (FSN.HU)phone @work: +361 210 1415 (194)
cell.: +3630 306 6758

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Re: Performance tuning hints of gigabit networking?

2003-02-27 Thread CHOI Junho 
From: Attila Nagy <[EMAIL PROTECTED]>
Subject: Re: Performance tuning hints of gigabit networking?
Date: Thu, 27 Feb 2003 11:18:48 +0100 (CET)

> Hello,
> 
> > 3. Usually thttpd use mmap() for caching contents in memory. Our
> >service file(only static files) varies from 10k ~
> >300Mbytes. Sometimes thttpd denies request with 500 internal error,
> >resetting mmap() buffers.
> I faced that problem years ago, contacted the authour, who said:
> "don't serve big files with thttpd, use something else"

Yes. thttpd tries to mmap() everything, when memory is full, it
releases all mmap()'ed entries, and reload again. That's why I try
thttpd patched to use sendfile() instead of mmap().

--
CHOI Junho  KFUG 
FreeBSD Project Web Data Bank 
Key fingerprint = 1369 7374 A45F F41A F3C0  07E3 4A01 C020 E602 60F5

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Source ip route lookup on incoming packets?

2003-02-27 Thread Sten Daniel Sørsdal 

 Has anyone made any patches to lookup the source ip for a packet to be routed
 so that it comes from the right interface? 
 I've heard alot of talk from people going to write patches to do this
 but no patches have turned up and no help from google.

 What i am looking for is a feature that basically prevents spoofing by looking
 the route for the source and match the incoming interface. 
 A firewall solves the problem but adds alot of administrative overhead and 
 leaves room for error.

 Is this feature even possible on FreeBSD?

- Sten

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

SO_USELOOPBACK's standard compliance

2003-02-27 Thread Mikhail Teterin 
Hello!

The define is ifdef-ed inside __BSD_VISIBLE on FreeBSD. It is not at all
present in RedHat-8's headers. Its description seems to suggest, it is
redundant, as the kernel should be using loopback if possible anyway,
should not it? Can someone clear it out? Thanks!

-mi


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Re: Checksum offload support for Intel 82550/82551

2003-02-27 Thread Attila Nagy 
Hello,

> I also modified the input handling so that it no longer uses the
> ng_ether_input_p hook. Now that FreeBSD 5.x has an ifp->if_input vector,
> it's not necessary to abuse this hook anymore. This avoids a collision
> with the ng_ether module, which is what was supposed to be using this
> hook in the first place.
What do you think, should this affect the VLAN problem, mentioned in my
previous mail? (.1q VLAN trunks do not work on fec interfaces)

> Let me know how this works.
I could ping my default gw.
Now I will try to dump a few TBs over the line and will report any
problems.

I will connect the machine to an other switch, maybe tomorrow to test
whether the VLAN trunking works or not.

Thanks a lot!

--[ Free Software ISOs - http://www.fsn.hu/?f=download ]--
Attila Nagy e-mail: [EMAIL PROTECTED]
Free Software Network (FSN.HU)phone @work: +361 210 1415 (194)
cell.: +3630 306 6758

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message