[9fans] ipconfig

[9fans] ipconfig

[Grunditz Mikael - migu]

[-- Attachment #1: Type: text/plain, Size: 218 bytes --]

Does ip/ipconfig ether /dev/ether0 192.168.0.2 -g 192.168.0.1 255.255.255.0

give me an interface with 192.168.0.2 and with default gateway 192.168.0.1 ?

Or how do I set my default gateway ?

/Michael Grunditz

[-- Attachment #2: Type: text/html, Size: 663 bytes --]

Re: [9fans] ipconfig

[presotto]

[-- Attachment #1: Type: text/plain, Size: 351 bytes --]

The options have to happen before any of the ppsitional arguments.
You really want

ip/ipconfig -g 192.168.0.1 ether /dev/ether0 192.168.0.2 255.255.255.0

Alternately, you could leave out the '-g 192.168.0.1' and just use

echo -n 'add 0 0 192.168.0.1' > /net/iproute

I think the ipconfig is easier but the other lets you change it later.

[-- Attachment #2: Type: message/rfc822, Size: 2792 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 218 bytes --]

Does ip/ipconfig ether /dev/ether0 192.168.0.2 -g 192.168.0.1 255.255.255.0

give me an interface with 192.168.0.2 and with default gateway 192.168.0.1 ?

Or how do I set my default gateway ?

/Michael Grunditz

[-- Attachment #2.1.2: Type: text/html, Size: 663 bytes --]

Re: [9fans] DHCP weirdness?

[David Presotto]

I think rob saw this also.  Could you send me the ip/ipconfig line
that you're using.  I changed it to fix arg processing and sysname
defaulting (i.e. setting something useful in /net/ndb's sys= entry)
but can't see what would have caused things to be completely ignored.

All our systems run at boot.  Perhaps I broke something for systems
running ipconfig out of termrc.

[9fans] ipconfig

[Sam]

Just to clarify this for me, is there any reason
ipconfig needs to be in termrc for bootp'd terminals?

I think our termrc has been around since 3rd ed
which had ipconfig by default (iirc).  If it's
redundant I'd like to pull it.

Sam

Re: [9fans] ipconfig

[David Presotto]

[-- Attachment #1: Type: text/plain, Size: 163 bytes --]

9load doesn't currently pass the IP address it got to the kernel
Therefore, the booted kernel runs dhcp when it comes up (and can
get more info than bootp does).

[-- Attachment #2: Type: message/rfc822, Size: 1693 bytes --]

From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] ipconfig
Date: Thu, 24 Apr 2003 16:03:06 -0400 (EDT)
Message-ID: <Pine.LNX.4.30.0304241556210.26650-100000@athena>

Just to clarify this for me, is there any reason
ipconfig needs to be in termrc for bootp'd terminals?

I think our termrc has been around since 3rd ed
which had ipconfig by default (iirc).  If it's
redundant I'd like to pull it.

Sam

Re: [9fans] ipconfig

[Russ Cox]

[-- Attachment #1: Type: text/plain, Size: 255 bytes --]

if booting with root from the network the kernel
will run it using /ipconfig in order to dial the file
server.  it doesn't need to be in termrc.  if you
want a termrc that works in both places you can
do

if(! test -e /net/ipifc/0/ctl) ip/ipconfig

[-- Attachment #2: Type: message/rfc822, Size: 3453 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 163 bytes --]

9load doesn't currently pass the IP address it got to the kernel
Therefore, the booted kernel runs dhcp when it comes up (and can
get more info than bootp does).

[-- Attachment #2.1.2: Type: message/rfc822, Size: 1693 bytes --]

From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] ipconfig
Date: Thu, 24 Apr 2003 16:03:06 -0400 (EDT)
Message-ID: <Pine.LNX.4.30.0304241556210.26650-100000@athena>

Just to clarify this for me, is there any reason
ipconfig needs to be in termrc for bootp'd terminals?

I think our termrc has been around since 3rd ed
which had ipconfig by default (iirc).  If it's
redundant I'd like to pull it.

Sam