Re: [9fans] dns suddenly not working - Plan9
This is a discussion on Re: [9fans] dns suddenly not working - Plan9 ; ip/ipconfig -g 199.98.16.1 ether /net/ether0 199.98.17.238 255.255.248.0 >…
That should be fine as long as you're running the latest ipconfig or
an old one. For a few days, ipconfig needed an explicit verb, like this:
ip/ipconfig -g 199.98.16.1 ether /net/ether0 ...
-
Re: [9fans] dns suddenly not working
ip/ipconfig -g 199.98.16.1 ether /net/ether0 199.98.17.238 255.255.248.0 >…
That should be fine as long as you're running the latest ipconfig or
an old one. For a few days, ipconfig needed an explicit verb, like this:
ip/ipconfig -g 199.98.16.1 ether /net/ether0 add 199.98.17.238 255.255.248.0
-
Re: [9fans] dns suddenly not working
On 4/26/07, geoff@plan9.bell-labs.com wrote:
> For a few days, ipconfig needed an explicit verb, like this:
> ip/ipconfig -g 199.98.16.1 ether /net/ether0 add 199.98.17.238 255.255.248.0
Nope, that doesn't fix anything.
Is there some way to invoke ndb/dns so it tells me more than "can't
find my ip address"?
--Joel
-
Re: [9fans] dns suddenly not working
myipaddr() calls readipifc(), so "cat /net/ipifc0/?/status" might be
revealing, particularly if you put it in termrc just before starting dns.