On Mar 30, 12:19 pm, 9f...@hamnavoe.com (Richard Miller) wrote:
> >> So, save for the ipwg, everything seems ok. The server akenaton as
>
> > that could be your problem. there's no route out.
>
> > - erik
>
> But that's not relevant when trying to reach machines
> on the same subnet:
>
> > I have
On Mar 30, 9:38 am, quans...@quanstro.net (erik quanstrom) wrote:
> > So, save for the ipwg, everything seems ok. The server akenaton as
>
> that could be your problem. there's no route out.
>
> - erik
I have ipwg delcared in my server's ndb file, but still it does not
show up in cat /netndb in m
>
> I think the real problem is trying to resolve unqualified names without
> a 'dnsdomain' defined -- see ndb(6)
I tried with:
ip/ping akenaton.amarna.net
and yes, it works with a qualified name for the server. So that seems
to be the problem with dns. I then tried the line:
dnsdomain=amarna.n
> I have ipwg delcared in my server's ndb file
s/ipwg/ipgw/
Is it spelled correctly in server's /lib/ndb/local?
>> I have ipwg delcared in my server's ndb file
>
> s/ipwg/ipgw/
>
> Is it spelled correctly in server's /lib/ndb/local?
... and is it really necessary for the terminal to have its own ndb
file? At best, it's redundant, at worst, conflicting.
++L
> iirc, you can load it, but it requires some hoops. getting a hoop-free
> version requires a whcl sig, and that costs $75 and a few days of tests.
You can load it in either two ways, you can boot into test mode, which
disables signature checking and writes "Test mode" in the bottom right
corner
> I then tried the line:
>
> dnsdomain=amarna.net
>
> in my terminal's ndb file, but it keeps failing with unqualified
> names.
You need something more like this:
ipnet=localnet ip=10.0.0.0 ipmask=255.255.255.0
dnsdomain=amarna.net
> By the way, I am trying to connect as ezequiel with
> ... and is it really necessary for the terminal to have its own ndb
> file? At best, it's redundant, at worst, conflicting.
Simplest practice is for the terminal to get its root file system from
the server, so they are sharing /lib/ndb/local. If the terminal has
its own root, it needs its own
On Apr 2, 6:58 am, 9f...@hamnavoe.com (Richard Miller) wrote:
> > I then tried the line:
>
> > dnsdomain=amarna.net
>
> > in my terminal's ndb file, but it keeps failing with unqualified
> > names.
>
> You need something more like this:
>
> ipnet=localnet ip=10.0.0.0 ipmask=255.255.255.0
>
> I think I have isolated the problem.
> I configured my server ndb file with auth and fs using the server
> fully qualified name.
> As a result, now, my terminal ndb info looks more promising:
>
> cat /net/ndb
> sys=nefertiti
> dom=nefertiti.amarna.net
> fs=10.0.0.2
> auth=10.0.0.2
> dn
After patching ndb/cs and running nfactotum, I'm still having
some trouble getting the new ssh to successfully login to a
remote system:
term% ssh2 openbsd
The following key has been offered by the server:
ek=10001
n=DA58E23128A865ABF57DCEEBB31529854F0EFBB0D50ADC5D930F29D7B5592724E9C8A1D74D011407
On Mon Apr 2 10:28:28 EDT 2012, s...@9front.org wrote:
> After patching ndb/cs and running nfactotum, I'm still having
> some trouble getting the new ssh to successfully login to a
> remote system:
>
> term% ssh2 openbsd
> The following key has been offered by the server:
> ek=10001
> n=DA58E231
> there are two ways you can get a short name to work
> - use a sys=xyz entry. if you also want to use dns to
> reach this node it would be conventional to have sys=xyz dom=xyz.dom.
That was the first thing I did. My tipical entry en ndb looks like:
ip=10.0.0.2 ether=jhgsfs7sfs788 sys=akenaton
On Mon Apr 2 10:31:33 EDT 2012, aragonezequ...@gmail.com wrote:
>
> > there are two ways you can get a short name to work
> > - use a sys=xyz entry. if you also want to use dns to
> > reach this node it would be conventional to have sys=xyz dom=xyz.dom.
>
> That was the first thing I did. My ti
> See? It seems everything is well configured, but still no short name
> resolution.
> What puzzles me more is, the same dnsquery used at the server give
> identical good results for both the short and large names:
Do you have in /lib/ndb/local on the terminal as I suggested:
ipnet=localnet ip=10
> Loading a kernel mode binary doesn't require a WHQL cross-signature,
> but WHQL will disable some yellow warnings otherwise shown to the
> user. WHQL is very expensive, depends on the type of driver, for what
> I was doing it was in the order of $2k/test. Every new version of the
> binary require
On Mon Apr 2 10:30:50 EDT 2012, quans...@quanstro.net wrote:
> On Mon Apr 2 10:28:28 EDT 2012, s...@9front.org wrote:
> > After patching ndb/cs and running nfactotum, I'm still having
> > some trouble getting the new ssh to successfully login to a
> > remote system:
[...]
>
> we're working on it
Trying to compile, but it seems like armv7 is not supported.
Anything I could try or do?
arch=`uname -m|sed 's/i.86/386/;s/Power Macintosh/power/; s/x86_64/amd64/'`; \
(cd posix-$arch && make)
cd: 2: can't cd to posix-armv7l
make: *** [libmachdep.a] Error 2
> After patching ndb/cs and running
> nfactotum, I'm still having
> some trouble getting the new ssh to successfully login to a
> remote system:
>
> term% ssh2 openbsd
> The following key has been offered by the server:
> ek=10001
> ...
>
> Add this key? (yes, no, session) yes
> ssh2: dial: hands
https://bitbucket.org/9nut/drawterm-arm-patch
On Mon, Apr 2, 2012 at 8:43 AM, hiro <23h...@googlemail.com> wrote:
> Trying to compile, but it seems like armv7 is not supported.
> Anything I could try or do?
>
>
> arch=`uname -m|sed 's/i.86/386/;s/Power Macintosh/power/; s/x86_64/amd64/'`; \
>
> Add this key? (yes, no, session) yes
> ssh2: dial: handshake failed
One other thing that might be instructive is to look
at the logs. The client side logs will be in /sys/log/ssh
and the server's are often in something like /var/log.
They might have something that will help us pinpoint
where it
After rebuilding nfactotum and starting it in a fresh window,
I'm able to login to all of the previously tried remote hosts.
-sl
> The client side logs will be in /sys/log/ssh
This was not created on my system.
-sl
> > The client side logs will be in
> /sys/log/ssh
>
> This was not created on my system.
My bad. He only uses syslog when he's in the role
of server, not client.
BLS
> After rebuilding nfactotum and starting it in a fresh window,
> I'm able to login to all of the previously tried remote hosts.
It seems to be failing only when factotum is already populated with
keys (I should point out: keys unrelated to the hosts I'm trying to
login to with the new ssh):
term
> After rebuilding nfactotum and
> starting it in a fresh window,
> I'm able to login to all of the previously tried remote
> hosts.
For the reference of future search engines I have a guess
on what you might have been seeing. If in the original
window, you had attempted to run ssh with an instan
> It seems to be failing only when factotum is already
> populated with
> keys (I should point out: keys unrelated to the hosts I'm
> trying to
> login to with the new ssh):
>
> term% sshtun -d
>
> term% ssh2 openbsd
> Verifying server signature
> In rsa_verify for connection: 0
> got error in fa
> While it is possible to get it confused with keys already
> stored in factotum (the reason the -z option is there), in
> this particular case, the "unknown role verify" from factotum
> seems to suggest it's talking to the old factotum.
You're right.
I forgot that 9front starts a factotum that w
can reproduce it here. the problem is 9fronts implementaiton
of ioprocs. instead of posting notes, we added a "interrupt" and
"nointerrupt" ctl messages to /proc/n/ctl that interrupts without
posting a note.
the problem was that notes could be scheduled before we even did
the syscall making them u
>> How big is the dependency on p9p factotum? Is it just syntactic or
>> is there some needed functionality in p9p factotum which the sources
>> version doesn't provide?
>
> Quite big. Actually, ssh is the reason we backported p9p
> factotum at Coraid.
I think sshv2 is a Great Leap Forward (tha
> also, you'll find that the old factotum doesn't handle things like
> flushes (prime example: del at passwd prompt to cancel) very well.
I've never noticed this - can you give a simple example scenario
where it goes wrong?
Thanks, it works.
But I had to change tas to use ldrex and strex instead of swp. And gcc
inline asm sucks.
On Mon, Apr 2, 2012 at 18:19, Skip Tavakkolian
wrote:
> https://bitbucket.org/9nut/drawterm-arm-patch
>
> On Mon, Apr 2, 2012 at 8:43 AM, hiro <23h...@googlemail.com> wrote:
>> Trying to com
I did this a while back (with Russ' help). I think I recall Russ also
suggesting the change you made, but my devices -- Sheeva/Guru Plug
(i.e. ARMv5) -- don't have ldrex/strex.
-Skip
On Mon, Apr 2, 2012 at 3:16 PM, hiro <23h...@googlemail.com> wrote:
> Thanks, it works.
> But I had to change tas
On 2012-04-02, at 1:08 PM, Richard Miller wrote:
> I've attempted a minimal conservative addition to standard factotum
> to make it useable with ssh2, and that seems to work for me. If anyone else
> wants to try it, just replace /sys/src/cmd/auth/factotum/rsa.c with
> /n/sources/contrib/miller/f
On 2012-04-02, at 7:27 PM, Lyndon Nerenberg wrote:
> I haven't tried genning up a CPU kernel with the new factotum yet.
Sorry, I meant to say "with Richard's patched original factotum."
has anyone done anything with this? it appears to be kindred to the chips
covered by pc/sdmv50xx.c, but with two ports per chip and no bridges.
or maybe there really are bridges and the kw sheet doesn't mention them.
thanks,
tristan
--
All original matter is hereby placed immediately under the
On Mon Apr 2 22:46:26 EDT 2012, 9p...@imu.li wrote:
> has anyone done anything with this? it appears to be kindred to the chips
> covered by pc/sdmv50xx.c, but with two ports per chip and no bridges.
>
> or maybe there really are bridges and the kw sheet doesn't mention them.
yes, i have a drive
scp seems a bit unhappy with the new ssh as well. Single file copies work in
both directions, and copying multiple files to plan9 works, but copying
multiple files from plan9 to remote unix systems barfs:
: lyndon@gandalf:/sys/src/cmd/unix/u9fs; lc
LICENSE convM2S.c
38 matches
Mail list logo
