Re: Introductory iproute2 documentation (Was Re: ifconfig network resolution)

2017-06-13 Thread Richard Owlett
On 06/13/2017 07:29 AM, Andy Smith wrote: Hi Richard, On Tue, Jun 13, 2017 at 05:11:47AM -0500, Richard Owlett wrote: Can you recommend a good introduction to iproute2 which ignores the existence of net-tools (start newbies with good habits)? Unfortunately I don't think I actually can. Being

Introductory iproute2 documentation (Was Re: ifconfig network resolution)

2017-06-13 Thread Andy Smith
Hi Richard, On Tue, Jun 13, 2017 at 05:11:47AM -0500, Richard Owlett wrote: > Can you recommend a good introduction to iproute2 which ignores the > existence of net-tools (start newbies with good habits)? Unfortunately I don't think I actually can. Being someone who started off with the

Re: ifconfig network resolution

2017-06-13 Thread Greg Wooledge
On Sat, Jun 10, 2017 at 04:18:42PM -0400, Cindy-Sue Causey wrote: > Anyone have tips for him right now *while he can read them* > related to the language appearing to switch teams on him? When pasting commands and output to an English-speaking mailing list, it's often a good idea to do

Re: ifconfig network resolution

2017-06-13 Thread Richard Owlett
On 06/10/2017 09:09 PM, Andy Smith wrote: [snip] Even the net-tools maintainers in Debian have wanted it removed from the base install for more than 8 years now. I'm not saying they would refuse to fix documentation bugs, but the motivation may be very low at this point. Some more info:

Re: ifconfig network resolution (Re: pointers to material for using netbook's wireless as access point)

2017-06-11 Thread Joe
On Sun, 11 Jun 2017 17:03:40 +0900 Joel Rees wrote: > On Sun, Jun 11, 2017 at 4:57 PM, Joe wrote: > > > > I've seen this kind of behaviour a very long time ago, and I can't > > really believe it is still happening, but... > > See the other

Re: ifconfig network resolution (Re: pointers to material for using netbook's wireless as access point)

2017-06-11 Thread Joel Rees
On Sun, Jun 11, 2017 at 4:57 PM, Joe wrote: > On Sat, 10 Jun 2017 10:57:47 +0900 > Joel Rees wrote: > >> Experimenting from the command line, I find myself puzzled about the >> arguments for ifconfig. >> >> Reading the manual, it would appear that the

Re: ifconfig network resolution (Re: pointers to material for using netbook's wireless as access point)

2017-06-11 Thread Joe
On Sat, 10 Jun 2017 10:57:47 +0900 Joel Rees wrote: > Experimenting from the command line, I find myself puzzled about the > arguments for ifconfig. > > Reading the manual, it would appear that the arguments for ifconfig > should be something like this: > > ifconfig

Re: ifconfig network resolution

2017-06-11 Thread Joel Rees
On Sun, Jun 11, 2017 at 2:04 PM, Lisi Reisz wrote: > On Saturday 10 June 2017 21:18:42 Cindy-Sue Causey wrote: >> My apologies in advance because I'm asking that without knowing if he >> does or does not actually speak Japanese. He might be able to read >> that quite well.

Re: ifconfig network resolution

2017-06-11 Thread Joel Rees
On Sun, Jun 11, 2017 at 11:09 AM, Andy Smith wrote: > Hi Joel, > > On Sun, Jun 11, 2017 at 07:55:50AM +0900, Joel Rees wrote: >> # If the address to be assigned is given first, which I think everyone >> # pretty much does: >> >> myadm@mycomp:~$ env LANG=en_US.UTF-8 sudo

Re: ifconfig network resolution

2017-06-10 Thread Lisi Reisz
On Saturday 10 June 2017 21:18:42 Cindy-Sue Causey wrote: > My apologies in advance because I'm asking that without knowing if he > does or does not actually speak Japanese. He might be able to read > that quite well. In that case, I'm envious because that's on a #Life > to-do bucket list for me..

Re: ifconfig network resolution

2017-06-10 Thread Andy Smith
Hi Joel, On Sun, Jun 11, 2017 at 07:55:50AM +0900, Joel Rees wrote: > # If the address to be assigned is given first, which I think everyone > # pretty much does: > > myadm@mycomp:~$ env LANG=en_US.UTF-8 sudo ifconfig eth0:1 down > myadm@mycomp:~$ env LANG=en_US.UTF-8 sudo ifconfig eth0:1 >

Re: ifconfig network resolution

2017-06-10 Thread Joel Rees
erk On Sun, Jun 11, 2017 at 7:55 AM, Joel Rees wrote: > [...] > Which is confusing to my middle-aged brain. So I could suggest editing > the man page, something along the lines of the following > > - > [...] > {add} > NOTES >The

Re: ifconfig network resolution

2017-06-10 Thread Joel Rees
Okay, here it is in the common language: - myadm@mycomp:~$ env LANG=en_US.UTF-8 sudo ifconfig eth0:1 down myadm@mycomp:~$ env LANG=en_US.UTF-8 sudo ifconfig eth0:1 eth0:1Link encap:Ethernet HWaddr 53:bc:81:02:21:bb UP BROADCAST RUNNING MULTICAST

Re: ifconfig network resolution

2017-06-10 Thread Joel Rees
Sorry, again, On Sat, Jun 10, 2017 at 11:36 PM, Joel Rees wrote: > On Sat, Jun 10, 2017 at 8:16 PM, Pascal Hambourg > wrote: >> Le 10/06/2017 à 12:13, Joel Rees a écrit : >>> >>> On Sat, Jun 10, 2017 at 3:52 PM, Pascal Hambourg

Re: ifconfig network resolution

2017-06-10 Thread Cindy-Sue Causey
On 6/10/17, Cindy-Sue Causey wrote: > On 6/10/17, Joe wrote: >> On Sat, 10 Jun 2017 23:36:06 +0900 >> Joel Rees wrote: >> >> >>> - >>> myadm@mycomp:~$ sudo ifconfig eth0:1 down >>>

Re: ifconfig network resolution

2017-06-10 Thread Cindy-Sue Causey
On 6/10/17, Joe wrote: > On Sat, 10 Jun 2017 23:36:06 +0900 > Joel Rees wrote: > > >> - >> myadm@mycomp:~$ sudo ifconfig eth0:1 down >> myadm@mycomp:~$ sudo ifconfig eth0:1 >> eth0:1Link encap:イーサネット

Re: ifconfig network resolution

2017-06-10 Thread Joe
On Sat, 10 Jun 2017 23:36:06 +0900 Joel Rees wrote: > - > myadm@mycomp:~$ sudo ifconfig eth0:1 down > myadm@mycomp:~$ sudo ifconfig eth0:1 > eth0:1Link encap:イーサネット ハードウェアアドレス > 50:af:73:12:64:aa UP BROADCAST RUNNING MULTICAST

Re: ifconfig network resolution

2017-06-10 Thread Joel Rees
On Sat, Jun 10, 2017 at 8:16 PM, Pascal Hambourg wrote: > Le 10/06/2017 à 12:13, Joel Rees a écrit : >> >> On Sat, Jun 10, 2017 at 3:52 PM, Pascal Hambourg >> wrote: >>> >>> Le 10/06/2017 à 03:57, Joel Rees a écrit : ifconfig

Re: ifconfig network resolution

2017-06-10 Thread Pascal Hambourg
Le 10/06/2017 à 12:13, Joel Rees a écrit : On Sat, Jun 10, 2017 at 3:52 PM, Pascal Hambourg wrote: Le 10/06/2017 à 03:57, Joel Rees a écrit : ifconfig eth0 netmask 255.255.255.224 netmask 255.255.255.224 broadcast 10.19.23.223 10.19.23.94 But the command returns

Re: ifconfig network resolution

2017-06-10 Thread Joel Rees
On Sat, Jun 10, 2017 at 3:52 PM, Pascal Hambourg wrote: > Le 10/06/2017 à 03:57, Joel Rees a écrit : >> >> Experimenting from the command line, I find myself puzzled about the >> arguments for ifconfig. >> >> Reading the manual, it would appear that the arguments for

Re: ifconfig network resolution

2017-06-10 Thread Pascal Hambourg
Le 10/06/2017 à 03:57, Joel Rees a écrit : Experimenting from the command line, I find myself puzzled about the arguments for ifconfig. Reading the manual, it would appear that the arguments for ifconfig should be something like this: ifconfig eth0 netmask 255.255.255.224 netmask

Re: ifconfig network resolution (Re: pointers to material for using netbook's wireless as access point)

2017-06-10 Thread Joel Rees
Sorry my typing is so lame. On Sat, Jun 10, 2017 at 10:57 AM, Joel Rees wrote: > Experimenting from the command line, I find myself puzzled about the > arguments for ifconfig. > > Reading the manual, it would appear that the arguments for ifconfig > should be something like

ifconfig network resolution (Re: pointers to material for using netbook's wireless as access point)

2017-06-09 Thread Joel Rees
Experimenting from the command line, I find myself puzzled about the arguments for ifconfig. Reading the manual, it would appear that the arguments for ifconfig should be something like this: ifconfig eth0 netmask 255.255.255.224 netmask 255.255.255.224 broadcast 10.19.23.223 10.19.23.94