[9fans] Getting drawterm to work in Leopard (again)

[9fans] Getting drawterm to work in Leopard (again)

[Pietro Gagliardi]

Hello. I'm trying to get drawterm to work in Leopard again. Here is my
command line:

	drawterm-osx-intel -c 'tcp!127.0.0.1!17010' -a 'tcp!127.0.0.1!2567' -
s 'tcp!127.0.0.1!5356' -u pietro

The problem was that it told me the connection refused. I told the
firewall to open ports 17010, 2567, and 5356, and I got "AS protocol
botch" after entering my password. I then told it to open all ports
1-32768, and QEMU failed to start.

What are the correct ports? Thanks.

Re: [9fans] Getting drawterm to work in Leopard (again)

[erik quanstrom]

> Hello. I'm trying to get drawterm to work in Leopard again. Here is my
> command line:
>
> 	drawterm-osx-intel -c 'tcp!127.0.0.1!17010' -a 'tcp!127.0.0.1!2567' -
> s 'tcp!127.0.0.1!5356' -u pietro
>
> The problem was that it told me the connection refused. I told the
> firewall to open ports 17010, 2567, and 5356, and I got "AS protocol
> botch" after entering my password. I then told it to open all ports
> 1-32768, and QEMU failed to start.
>
> What are the correct ports? Thanks.

; for(i in guard ticket secstore exportfs rexexec cpu)
	ndb/query tcp $i
tcp=guard port=566
tcp=ticket port=567
tcp=secstore port=5356
tcp=exportfs port=17007
tcp=rexexec port=17009
tcp=cpu port=17013

the easiest way to derive this information is by looking in /rc/bin/service
and eliminating the ones you know aren't used.

btw, this command line is equivalent:

	drawtern-osx-intel -c 127.0.0.1 -a 127.0.0.1

- erik

Re: [9fans] Getting drawterm to work in Leopard (again)

[Iruata Souza]

On Thu, Jun 19, 2008 at 3:08 PM, Pietro Gagliardi <pietro10@mac.com> wrote:
> Hello. I'm trying to get drawterm to work in Leopard again. Here is my
> command line:
>
>        drawterm-osx-intel -c 'tcp!127.0.0.1!17010' -a 'tcp!127.0.0.1!2567'
> -s 'tcp!127.0.0.1!5356' -u pietro
>

is connecting to 127.0.0.1 really what you want? i ask 'cause i dont
know how qemu networking under osx works.

iru

Re: [9fans] Getting drawterm to work in Leopard (again)

[Pietro Gagliardi]

All the ports except the guard and ticket (56[67]) work, and AS is
still botched, so I believe AS has to do with one of those two (most
likely ticket. This port problem might have to do with OS X. I'll ask
around.

On Jun 19, 2008, at 2:50 PM, erik quanstrom wrote:

>> Hello. I'm trying to get drawterm to work in Leopard again. Here is
>> my
>> command line:
>>
>> 	drawterm-osx-intel -c 'tcp!127.0.0.1!17010' -a 'tcp!127.0.0.1!
>> 2567' -
>> s 'tcp!127.0.0.1!5356' -u pietro
>>
>> The problem was that it told me the connection refused. I told the
>> firewall to open ports 17010, 2567, and 5356, and I got "AS protocol
>> botch" after entering my password. I then told it to open all ports
>> 1-32768, and QEMU failed to start.
>>
>> What are the correct ports? Thanks.
>
> ; for(i in guard ticket secstore exportfs rexexec cpu)
> 	ndb/query tcp $i
> tcp=guard port=566
> tcp=ticket port=567
> tcp=secstore port=5356
> tcp=exportfs port=17007
> tcp=rexexec port=17009
> tcp=cpu port=17013
>
> the easiest way to derive this information is by looking in /rc/bin/
> service
> and eliminating the ones you know aren't used.
>
> btw, this command line is equivalent:
>
> 	drawtern-osx-intel -c 127.0.0.1 -a 127.0.0.1
>
> - erik
>
>

Re: [9fans] Getting drawterm to work in Leopard (again)

[erik quanstrom]

> All the ports except the guard and ticket (56[67]) work, and AS is
> still botched, so I believe AS has to do with one of those two (most
> likely ticket. This port problem might have to do with OS X. I'll ask
> around.

unix typically doesn't let normal users open ports below 1024.

- erik

Re: [9fans] Getting drawterm to work in Leopard (again)

[Federico G. Benavento]

maybe unrelated, but does the pass you entered with auth/changeuser
for bootes matches the one in nvram?

On Thu, Jun 19, 2008 at 7:24 PM, Pietro Gagliardi <pietro10@mac.com> wrote:
> All the ports except the guard and ticket (56[67]) work, and AS is still
> botched, so I believe AS has to do with one of those two (most likely
> ticket. This port problem might have to do with OS X. I'll ask around.
>
> On Jun 19, 2008, at 2:50 PM, erik quanstrom wrote:
>
>>> Hello. I'm trying to get drawterm to work in Leopard again. Here is my
>>> command line:
>>>
>>>        drawterm-osx-intel -c 'tcp!127.0.0.1!17010' -a
>>> 'tcp!127.0.0.1!2567' -
>>> s 'tcp!127.0.0.1!5356' -u pietro
>>>
>>> The problem was that it told me the connection refused. I told the
>>> firewall to open ports 17010, 2567, and 5356, and I got "AS protocol
>>> botch" after entering my password. I then told it to open all ports
>>> 1-32768, and QEMU failed to start.
>>>
>>> What are the correct ports? Thanks.
>>
>> ; for(i in guard ticket secstore exportfs rexexec cpu)
>>        ndb/query tcp $i
>> tcp=guard port=566
>> tcp=ticket port=567
>> tcp=secstore port=5356
>> tcp=exportfs port=17007
>> tcp=rexexec port=17009
>> tcp=cpu port=17013
>>
>> the easiest way to derive this information is by looking in
>> /rc/bin/service
>> and eliminating the ones you know aren't used.
>>
>> btw, this command line is equivalent:
>>
>>        drawtern-osx-intel -c 127.0.0.1 -a 127.0.0.1
>>
>> - erik
>>
>>
>
>
>



--
Federico G. Benavento

Re: [9fans] Getting drawterm to work in Leopard (again)

[Jeff Sickel]

On Jun 19, 2008, at 5:24 PM, Pietro Gagliardi wrote:

> All the ports except the guard and ticket (56[67]) work, and AS is
> still botched, so I believe AS has to do with one of those two (most
> likely ticket. This port problem might have to do with OS X. I'll
> ask around.

Leopard added a new firewall feature that defaults to blocking all
incoming connections for each process/application.  You can see which
applications have been set up to allow connections in by going to the
System Preferecnes -> Security -> Firewall panel.

I'm not sure what Qemu sets up for its network layer these days, but I
run VMware and it created two entries in the firewall table: vmnet-
natd and natd that need to be set to allow incoming connections.  You
can also use ipfw to look at/shape the connections:

   sudo ipfw list

should tell you if you've got some ports still blocked--possible from
upgrading from a Tiger install.

Question: can you get from your Qemu Plan 9 instance to anything on
the outside network?  I found that a problem when trying to use Qemu--
I could never get my Plan 9 instance to get any packets out, let alone
in.

-jas