Re: NIS client does perform Ok when my duplex is right (Was: Re:

2001-10-18 Thread Daniel O'Connor 


On 17-Oct-2001 Peter S. Housel wrote:
  At Wed, 17 Oct 2001 18:32:15 +0900 (JST), Daniel O'Connor wrote:
  Either hack the startup script, or man 5 dhclient.conf :)
  (Look for medium)
  
  And then use media instead, because dhclient.conf(5) is wrong.

Ahh, interesting.

Obviously I haven't used the feature in question :)

Can the man page be changed?

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum

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

Re: NIS client does perform Ok when my duplex is right (Was: Re: NIS client performance seems very poor under network load)

2001-10-17 Thread Mike Smith 

 Should the below work ?
 
 ifconfig_xl0=DHCP media 100baseTX mediaopt full-duplex

I don't think so.  Try using the start_if script stuff to pre-set your 
media options before DHCP gets hold of the interface; I'm pretty sure 
that'll work.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E



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

RE: NIS client does perform Ok when my duplex is right (Was: Re:

2001-10-17 Thread Daniel O'Connor 


On 17-Oct-2001 Thyer, Matthew wrote:
  P.S. I would still like to try using DHCP but *NOT* autonegotiating.
  
  Is this possible ?

Either hack the startup script, or man 5 dhclient.conf :)
(Look for medium)

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum

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

Re: NIS client does perform Ok when my duplex is right (Was: Re:

2001-10-17 Thread Peter S. Housel 

At Wed, 17 Oct 2001 18:32:15 +0900 (JST), Daniel O'Connor wrote:
 Either hack the startup script, or man 5 dhclient.conf :)
 (Look for medium)

And then use media instead, because dhclient.conf(5) is wrong.

-Peter-

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

Re: NIS client does perform Ok when my duplex is right (Was: Re:

2001-10-17 Thread John Baldwin 


On 17-Oct-01 Mike Smith wrote:
 Should the below work ?
 
 ifconfig_xl0=DHCP media 100baseTX mediaopt full-duplex
 
 I don't think so.  Try using the start_if script stuff to pre-set your 
 media options before DHCP gets hold of the interface; I'm pretty sure 
 that'll work.

Yes, this works great.  I use it on one of my alpha's that doesn't autoneg by
default.  You don't set ifconfig_xl0 to anything, but instead create a
start_if.xl0 file similar to this:

 cat /etc/start_if.dc0 
/sbin/ifconfig dc0 media auto
#/sbin/ifconfig dc0 media 10baseT/UTP
/sbin/dhclient dc0

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/

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

Re: NIS client does perform Ok when my duplex is right (Was: Re: NIS client performance seems very poor under network load)

2001-10-17 Thread Bernd Walter 

On Wed, Oct 17, 2001 at 06:00:42PM +0930, Thyer, Matthew wrote:
 It was my problem.
 
 My network interface was in 100Mbps half-duplex instead of
 100Mbps full-duplex (the switch was in 100 full).
 
 I was using DHCP to configure the interface and for some
 reason it came up as half (even though a 4.3-BETA box elsewhere
 around here comes up in full-duplex).
 
 It seems that Cisco equipment doesn't autonegotiate well as we
 have seen this problem on other UNIX systems (HP-UX in particular)
 so we try to tie everything down these days.

You must always set both sides identic.
This means if you want autonegotiate to work you must not set one
side to fix configuration.

Nevertheless it's saver to use fix configuration whenever possible.

-- 
B.Walter  COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup   [EMAIL PROTECTED]


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

Re: NIS client does perform Ok when my duplex is right (Was: Re:

2001-10-17 Thread Andrew Gallatin 


John Baldwin writes:
  
  On 17-Oct-01 Mike Smith wrote:
   Should the below work ?
   
   ifconfig_xl0=DHCP media 100baseTX mediaopt full-duplex
   
   I don't think so.  Try using the start_if script stuff to pre-set your 
   media options before DHCP gets hold of the interface; I'm pretty sure 
   that'll work.
  
  Yes, this works great.  I use it on one of my alpha's that doesn't autoneg by
  default.  You don't set ifconfig_xl0 to anything, but instead create a

Non-autoneg is a feature -- the tulip drivers listen to the SRM
console's media settings and bases the tulip's default behaviour on them.
This is for compat with Tru64 and VMS..

If you want it to augoneg, do 'set ewa0_mode auto' at the SRM console
prompt and it will act like any other freebsd nic on any platform.

Drew

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