[9fans] Creating alternative network directories

[9fans] Creating alternative network directories

[Thorn Avery]

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

Hello all!

I recently got a NIC for my tower, and I've been trying to no avail to mount the devices as /net is.

I have the following devices:
#l and #I, the motherboards inbuilt port
#l0 and #I0, with #l0/ether0
#l1 and #I1, with #l1/ether1

My goal is to end up with /net.alt.0 and /net.alt.1, which i then intend to bind over /net as needed.

I currently have the following in /rc/bin/cpurc.local (im creating in usr directory while tinkering):
#!/bin/rc
NETPATH=/usr/glenda/
for(n in 0 1)
    if(! test -e $NETPATH^net.alt.$n)
        mkdir $NETPATH^net.alt.$n
    bind -a '#l'^$n $NETPATH^net.alt.$n
    bind -a '#I'^$n $NETPATH^net.alt.$n
    mount -a /srv/cs $NETPATH^net.alt.$n
    mount -a /srv/dns $NETPATH^net.alt.$n
}
rm /env/NETPATH

which is what I saw in my namespaces file was being done for /net

after this, ip/ipconfig returns "no success with DHCP", whether i supply the details or not.

My questions are:
1: what are the important steps that go into creating a network stacks directory?
2: is the way Im doing so the correct course, or is there a best practice i should be following instead?

Thank you :) This is my first time on the mailing list so please be kind!
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc515db30bf944ee3-M54e602d1b4fd45f1690b4687
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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

Re: [9fans] Creating alternative network directories

[Lucio De Re]

#l and #l0 are identical, the latter is the software (for want of a
better term) instance of the latter, #1 is the second and #2 is the
third.

If you read the man page carefully - and I'm answering this not out of
 experience, but because I presume you want to at least try a
suggestion and go from there - you'll see that you may need to
describe each net adapter in the plan9.ini file. If you read the
/dev/kmesg file, you ought to find mention of #l0, #l1 and #l2 in it,
if the adapters are recognise.

(Careful now, I'm still drinking my first coffee of the day - but
everything you need is in the man pages.)

Lucio.

On 10/7/22, Thorn Avery <ta@p7.co.nz> wrote:
> Hello all!
>
> I recently got a NIC for my tower, and I've been trying to no avail to mount
> the devices as /net is.
>
> I have the following devices:
> #l and #I, the motherboards inbuilt port
> #l0 and #I0, with #l0/ether0
> #l1 and #I1, with #l1/ether1
>
> My goal is to end up with /net.alt.0 and /net.alt.1, which i then intend to
> bind over /net as needed.
>
> I currently have the following in /rc/bin/cpurc.local (im creating in usr
> directory while tinkering):
> #!/bin/rc
> NETPATH=/usr/glenda/
> for(n in 0 1)
>     if(! test -e $NETPATH^net.alt.$n)
>         mkdir $NETPATH^net.alt.$n
>     bind -a '#l'^$n $NETPATH^net.alt.$n
>     bind -a '#I'^$n $NETPATH^net.alt.$n
>     mount -a /srv/cs $NETPATH^net.alt.$n
>     mount -a /srv/dns $NETPATH^net.alt.$n
> }
> rm /env/NETPATH
> 
> which is what I saw in my namespaces file was being done for /net
> 
> after this, ip/ipconfig returns "no success with DHCP", whether i supply the
> details or not.
> 
> My questions are:
> 1: what are the important steps that go into creating a network stacks
> directory?
> 2: is the way Im doing so the correct course, or is there a best practice i
> should be following instead?
> 
> Thank you :) This is my first time on the mailing list so please be kind!


-- 
Lucio De Re
2 Piet Retief St
Kestell (Eastern Free State)
9860 South Africa

Ph.: +27 58 653 1433
Cell: +27 83 251 5824

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc515db30bf944ee3-Mdd18d03749d09c14ce89113b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] Creating alternative network directories

[Lucio De Re]

On 10/7/22, Lucio De Re <lucio.dere@gmail.com> wrote:
> #l and #l0 are identical, the latter is the software (for want of a
> better term) instance of the latter, #1 is the second and #2 is the
> third.
>
> If you read the man page carefully - and I'm answering this not out of
>  experience, but because I presume you want to at least try a
> suggestion and go from there - you'll see that you may need to
> describe each net adapter in the plan9.ini file. If you read the
> /dev/kmesg file, you ought to find mention of #l0, #l1 and #l2 in it,
> if the adapters are recognise.
>
> (Careful now, I'm still drinking my first coffee of the day - but
> everything you need is in the man pages.)
>
> Lucio.
>
> On 10/7/22, Thorn Avery <ta@p7.co.nz> wrote:
>> Hello all!
>>
>> I recently got a NIC for my tower, and I've been trying to no avail to
>> mount
>> the devices as /net is.
>>
>> I have the following devices:
>> #l and #I, the motherboards inbuilt port
>> #l0 and #I0, with #l0/ether0
>> #l1 and #I1, with #l1/ether1
>>
>> My goal is to end up with /net.alt.0 and /net.alt.1, which i then intend
>> to
>> bind over /net as needed.
>>
>> I currently have the following in /rc/bin/cpurc.local (im creating in usr
>> directory while tinkering):
>> #!/bin/rc
>> NETPATH=/usr/glenda/
>> for(n in 0 1)
>>     if(! test -e $NETPATH^net.alt.$n)
>>         mkdir $NETPATH^net.alt.$n
>>     bind -a '#l'^$n $NETPATH^net.alt.$n
>>     bind -a '#I'^$n $NETPATH^net.alt.$n
>>     mount -a /srv/cs $NETPATH^net.alt.$n
>>     mount -a /srv/dns $NETPATH^net.alt.$n
>> }
>> rm /env/NETPATH
>> 
>> which is what I saw in my namespaces file was being done for /net
>> 
>> after this, ip/ipconfig returns "no success with DHCP", whether i supply
>> the
>> details or not.
>> 
>> My questions are:
>> 1: what are the important steps that go into creating a network stacks
>> directory?
>> 2: is the way Im doing so the correct course, or is there a best practice
>> i
>> should be following instead?
>> 
>> Thank you :) This is my first time on the mailing list so please be kind!
>
>
> --
> Lucio De Re
> 2 Piet Retief St
> Kestell (Eastern Free State)
> 9860 South Africa
>
> Ph.: +27 58 653 1433
> Cell: +27 83 251 5824
>


-- 
Lucio De Re
2 Piet Retief St
Kestell (Eastern Free State)
9860 South Africa

Ph.: +27 58 653 1433
Cell: +27 83 251 5824

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc515db30bf944ee3-M9480d8049ff35448494c4a00
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription