Re: Trouble to connect FreeBSD 4.5 to internet

2002-03-16 Thread Dmitry A. Bondareff




Hmm.
It's too strange configuration. 
The ISP must to do translation to 
195.14.167.39 on him box.
May be he think that you must do 
it.
Try to using NAT on your box.
 
And netmask wrong too !
 
Regards,
aka Dimasic.
 
 
- Original Message - 

  From: 
  Xawiers 
  To: [EMAIL PROTECTED] 
  Sent: Thursday, March 14, 2002 6:22 
  PM
  Subject: Trouble to connect FreeBSD 4.5 
  to internet
  
  Hello,
  I have trouble to connect FreeBSD to internet.
  Our ISP gave me these datas about network
  Gateway: 192.168.100.254
  My external IP: 195.14.167.39
  Netmask: 255.255.255.254
   
  what i did:
  First I added alias, because I cant see my gateway - no ping response 
  (not in the same subnet)
   
  ifconfig ed0 inet 192.168.100.253 netmask 255.255.255.0 alias
   
  And I add default gateway:
   
  route add default 192.168.100.254
   
  now my GW responses for ping, but internet - no 
  How I coud resolve this problem.
   
  P.S. sorry for my english
  Best regards
  Xawiers


Unsupported TRENDnet ethernet card

2002-03-16 Thread J . S .

Hi.

I recently bought this TRENDnet TE100-PCIWN ethernet card which integrity
I now strongly doubt:

1. Device unknown at bootup
2. No reference in LINT
3. Minimal documentation

I was hoping you guys would be so kind and make it available to, most
likely, a lot of people.

Chip 1: GTS FC-515LS
Chip 2: RMC RTL8139C

pci0:  (vendor=0x10ec, dev=0x8139) at 14.0 irq 10

Thanks.

Regards,
Johann Sharizan

(Alfred, you there?)

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



Re: Unsupported TRENDnet ethernet card

2002-03-16 Thread Alfred Perlstein

* J. S. <[EMAIL PROTECTED]> [020316 02:34] wrote:
> Hi.
> 
> I recently bought this TRENDnet TE100-PCIWN ethernet card which integrity
> I now strongly doubt:
> 
> 1. Device unknown at bootup
> 2. No reference in LINT
> 3. Minimal documentation
> 
> I was hoping you guys would be so kind and make it available to, most
> likely, a lot of people.
> 
> Chip 1: GTS FC-515LS
> Chip 2: RMC RTL8139C
> 
> pci0:  (vendor=0x10ec, dev=0x8139) at 14.0 irq 10
> 
> (Alfred, you there?)

Er, yes, what version of FreeBSD are you running?  It looks like
the latest 4.5 version has this chipset...  You aren't
running an older release or a custom kernel are you?

It should work with the 'rl' driver if you've got 4.5.

-- 
-Alfred Perlstein [[EMAIL PROTECTED]]
'Instead of asking why a piece of software is using "1970s technology,"
 start asking why software is ignoring 30 years of accumulated wisdom.'
Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/

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



Re: Trouble to connect FreeBSD 4.5 to internet

2002-03-16 Thread Xawiers



Hello again
so how shoult I config that with natd 
?
Could someone write any examples?
 
Xawiers
 
- Original Message - 

  From: 
  Dmitry A. Bondareff 
  
  To: [EMAIL PROTECTED] 
  Sent: Saturday, March 16, 2002 10:58 
  AM
  Subject: Re: Trouble to connect FreeBSD 
  4.5 to internet
  
  
  Hmm.
  It's too strange configuration. 
  
  The ISP must to do translation to 
  195.14.167.39 on him box.
  May be he think that you must do 
  it.
  Try to using NAT on your box.
   
  And netmask wrong too !
   
  Regards,
  aka Dimasic.
   
   
  - Original Message - 
  
From: 
Xawiers 
To: [EMAIL PROTECTED] 
Sent: Thursday, March 14, 2002 6:22 
PM
Subject: Trouble to connect FreeBSD 4.5 
to internet

Hello,
I have trouble to connect FreeBSD to internet.
Our ISP gave me these datas about network
Gateway: 192.168.100.254
My external IP: 195.14.167.39
Netmask: 255.255.255.254
 
what i did:
First I added alias, because I cant see my gateway - no ping response 
(not in the same subnet)
 
ifconfig ed0 inet 192.168.100.253 netmask 255.255.255.0 alias
 
And I add default gateway:
 
route add default 192.168.100.254
 
now my GW responses for ping, but internet - no 
How I coud resolve this problem.
 
P.S. sorry for my english
Best regards
Xawiers


Re: SACK (and older TCP stack) availability?

2002-03-16 Thread Harkirat Singh


Hello,

I am sorry due to some reasons I have not been able to check this mail
account in the past.

I faced problem in validation of Implementation due to lack of efficient
tools, I used wireless bed so by default tcpdump (at wi0 interface) was in
promiscuous-mode and one packet was dumped appx three times.

I used Ostermann's tcptrace and tcpdump and then did a packet by pkt
trace, SACK was behaving as desirable. However, I wish if there would have
been more efficient tool.

I also verified implementation in a wireless testbed of 3 hop network and
using Dummynet for creating reorder, loss, delay etc..(many thanks to
Rizzo for such a magnificent tool!). SACK showed higher thruput than Reno
and Newreno under various test conditions.

I was doing an Energy performance of Reno, NewReno and SACK part of my
thesis and I used kernel.GENERIC (FreeBSD4.3) for reno and NewReno.

Please let me know if I can be of any of help.

Regards,

Harkirat


On Thu, 21 Feb 2002, Julian Elischer wrote:

> tehn we need to tell teh author..
> he seems to want then to be used . I'm sure he'd be reponsive to being
> told about the problems..
>
>
> On Thu, 21 Feb 2002, Luigi Rizzo wrote:
>
> > On Thu, Feb 21, 2002 at 01:54:20AM +, Mike Silbersack wrote:
> > >
> > > > I tracked a thread from Aug 2001 in which Harkirat Singh announced his
> > > > SACK implementation.  But, this thread seems to have ended prematurely and
> > > > grep'ing for SACK in current does not turn up anything interesting.  What
> > > > is it's status?  Was the 4.3 SACK diff stable?
> > >
> > > I never got time to test it, nor did any other committer I'm aware of.
> > > If someone were to do some good testing of the patch and post the results,
> > > that would be highly helpful in getting it on the road to being committed.
> > > Unadvocated patches ususally don't get committed.
> >
> > I actually looked at the patches, and by visual inspection,
> > they broke the flow for standard TCP connections when SACK
> > was disabled. This was also verified with TBIT.
> > So even if the SACK implementation was correct
> > (which I haven't checked in detail) they are a no-go
> > unless someone puts significant work on them.
> >
> > cheers
> > luigi
> > --+-
> >  Luigi RIZZO, [EMAIL PROTECTED]  . ICSI (on leave from Univ. di Pisa)
> >  http://www.iet.unipi.it/~luigi/  . 1947 Center St, Berkeley CA 94704
> >  Phone: (510) 666 2927
> > --+-
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-net" in the body of the message
> >
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-net" in the body of the message
>


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



[no subject]

2002-03-16 Thread [EMAIL PROTECTED]

Hi,
I would appreciate it if you could suggest
some soft for traffic monitoring on a
 Freebsd 4.5 default router.

I need to monitor the incoming and outgoing
traffic of all the subnets for which this machine
is the defaultrouter.


Many thanks in anticipation,
Adam







__
Scanned and protected by Inflex
http://pldaniels.com/inflex


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