From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: Grunditz Mikael - migu To: "9fans@cse.psu.edu (E-mail)" <9fans@cse.psu.edu> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C10B7E.A460D9C0" Subject: [9fans] ipconfig Date: Fri, 13 Jul 2001 11:31:49 +0200 Topicbox-Message-UUID: c944ffc0-eac9-11e9-9e20-41e7f4b1d025 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C10B7E.A460D9C0 Content-Type: text/plain; charset="iso-8859-1" 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 ------_=_NextPart_001_01C10B7E.A460D9C0 Content-Type: text/html; charset="iso-8859-1" ipconfig

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

------_=_NextPart_001_01C10B7E.A460D9C0-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: presotto@plan9.bell-labs.com To: 9fans@cse.psu.edu Subject: Re: [9fans] ipconfig MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-ylpniprzncrhdfrfrplgkzipwl" Message-Id: <20010713125307.C4D4E199E4@mail.cse.psu.edu> Date: Fri, 13 Jul 2001 08:53:05 -0400 Topicbox-Message-UUID: ca1d22e2-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-ylpniprzncrhdfrfrplgkzipwl Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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. --upas-ylpniprzncrhdfrfrplgkzipwl Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Fri Jul 13 05:33:23 EDT 2001 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Fri Jul 13 05:33:21 EDT 2001 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 71CEB199E6; Fri, 13 Jul 2001 05:33:09 -0400 (EDT) Received: from mail-gw.im.se (mail-gw.im.se [193.14.22.222]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 1B207199C0 for <9fans@cse.psu.edu>; Fri, 13 Jul 2001 05:32:43 -0400 (EDT) Received: from MSXSTH1.im.se (msxsth1.im.se [193.14.16.108]) by mail-gw.im.se (8.11.0/8.11.0) with ESMTP id f6D9OvF36276 for <9fans@cse.psu.edu>; Fri, 13 Jul 2001 11:24:57 +0200 Received: by MSXSTH1.im.se with Internet Mail Service (5.5.2653.19) id ; Fri, 13 Jul 2001 11:31:59 +0200 Message-ID: From: Grunditz Mikael - migu To: "9fans@cse.psu.edu (E-mail)" <9fans@cse.psu.edu> MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C10B7E.A460D9C0" Subject: [9fans] ipconfig Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.5 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Fri, 13 Jul 2001 11:31:49 +0200 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C10B7E.A460D9C0 Content-Type: text/plain; charset="iso-8859-1" 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 ------_=_NextPart_001_01C10B7E.A460D9C0 Content-Type: text/html; charset="iso-8859-1" ipconfig

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

------_=_NextPart_001_01C10B7E.A460D9C0-- --upas-ylpniprzncrhdfrfrplgkzipwl-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam To: <9fans@cse.psu.edu> In-Reply-To: <5038f53ceb07079e037b1d023183e543@plan9.bell-labs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [9fans] ipconfig Date: Thu, 24 Apr 2003 16:03:06 -0400 Topicbox-Message-UUID: 98ac369c-eacb-11e9-9e20-41e7f4b1d025 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: David Presotto To: 9fans@cse.psu.edu Subject: Re: [9fans] ipconfig In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-khfiklpgojgzbrufxhbbhzlpsk" Date: Thu, 24 Apr 2003 16:56:32 -0400 Topicbox-Message-UUID: 98b977da-eacb-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-khfiklpgojgzbrufxhbbhzlpsk Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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). --upas-khfiklpgojgzbrufxhbbhzlpsk Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Thu Apr 24 16:44:24 EDT 2003 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Thu Apr 24 16:44:22 EDT 2003 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 52EA219BC8; Thu, 24 Apr 2003 16:44:10 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from athena.softcardsystems.com (mail.softcardsystems.com [12.34.136.114]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 6703F19BC8 for <9fans@cse.psu.edu>; Thu, 24 Apr 2003 16:43:16 -0400 (EDT) Received: from athena (athena [12.34.136.114]) by athena.softcardsystems.com (8.12.8/8.12.8) with ESMTP id h3OK36m8026688 for <9fans@cse.psu.edu>; Thu, 24 Apr 2003 16:03:06 -0400 From: Sam X-Sender: To: <9fans@cse.psu.edu> In-Reply-To: <5038f53ceb07079e037b1d023183e543@plan9.bell-labs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [9fans] ipconfig Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 24 Apr 2003 16:03:06 -0400 (EDT) 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 --upas-khfiklpgojgzbrufxhbbhzlpsk-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <51aa11ff10795cb516d214a870b017be@plan9.bell-labs.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] ipconfig From: "Russ Cox" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-aenquxehjtavrkoycvscjqkkgw" Date: Sun, 27 Apr 2003 17:20:19 -0400 Topicbox-Message-UUID: 998689dc-eacb-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-aenquxehjtavrkoycvscjqkkgw Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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 --upas-aenquxehjtavrkoycvscjqkkgw Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Thu Apr 24 16:57:18 EDT 2003 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Thu Apr 24 16:57:16 EDT 2003 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 27AF919BD4; Thu, 24 Apr 2003 16:57:11 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from plan9.cs.bell-labs.com (plan9.bell-labs.com [204.178.31.2]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id F00B019ACE for <9fans@cse.psu.edu>; Thu, 24 Apr 2003 16:56:33 -0400 (EDT) Message-ID: From: David Presotto To: 9fans@cse.psu.edu Subject: Re: [9fans] ipconfig In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-khfiklpgojgzbrufxhbbhzlpsk" Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 24 Apr 2003 16:56:32 -0400 This is a multi-part message in MIME format. --upas-khfiklpgojgzbrufxhbbhzlpsk Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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). --upas-khfiklpgojgzbrufxhbbhzlpsk Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Thu Apr 24 16:44:24 EDT 2003 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Thu Apr 24 16:44:22 EDT 2003 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 52EA219BC8; Thu, 24 Apr 2003 16:44:10 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from athena.softcardsystems.com (mail.softcardsystems.com [12.34.136.114]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 6703F19BC8 for <9fans@cse.psu.edu>; Thu, 24 Apr 2003 16:43:16 -0400 (EDT) Received: from athena (athena [12.34.136.114]) by athena.softcardsystems.com (8.12.8/8.12.8) with ESMTP id h3OK36m8026688 for <9fans@cse.psu.edu>; Thu, 24 Apr 2003 16:03:06 -0400 From: Sam X-Sender: To: <9fans@cse.psu.edu> In-Reply-To: <5038f53ceb07079e037b1d023183e543@plan9.bell-labs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [9fans] ipconfig Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 24 Apr 2003 16:03:06 -0400 (EDT) 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 --upas-khfiklpgojgzbrufxhbbhzlpsk-- --upas-aenquxehjtavrkoycvscjqkkgw--