possible bug

[Elliot Finley]

NetNameResolver localHostName. '0.0.0.0'

NetNameResolver localHostAddress. #[0 0 0 0]

That corresponds to the following ifconfig output from my macbook pro:

the-macbook:~ efinley$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether 60:33:4b:21:26:2b
media: <unknown subtype> (<unknown type>)
status: inactive
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether c4:2c:03:34:53:bb
inet6 fe80::c62c:3ff:fe34:53bb%en0 prefixlen 64 scopeid 0x5
inet 10.215.90.59 netmask 0xffffff00 broadcast 10.215.90.255
media: autoselect (100baseTX <full-duplex,flow-control>)
status: active
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 60:33:4b:ff:fe:95:b0:b0
media: autoselect <full-duplex>
status: inactive
vnic0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1c:42:00:00:08
inet 10.211.55.2 netmask 0xffffff00 broadcast 10.211.55.255
media: autoselect
status: active
vnic1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1c:42:00:00:09
inet 10.37.129.2 netmask 0xffffff00 broadcast 10.37.129.255
media: autoselect
status: active

as you can see, my address is 10.215.90.59, but yet the error is
'ConnectionTimedOut:
Cannot connect to 10.215.90.74:51001'.

When I remove the wired connection on the 10.215.90.0/24 network and turn on
the wireless connection on the 67.22.168.0/24 network, then the client
connects to the server just fine, and I get the following output:

NetNameResolver localHostName. 'prcowifi-67-22-168-209.etv.net'

NetNameResolver localHostAddress.  #[67 22 168 209]

the-macbook:~ efinley$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 60:33:4b:21:26:2b
inet6 fe80::6233:4bff:fe21:262b%en1 prefixlen 64 scopeid 0x4
inet 67.22.168.209 netmask 0xffffff00 broadcast 67.22.168.255
media: <unknown subtype>
status: active
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether c4:2c:03:34:53:bb
media: autoselect
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 60:33:4b:ff:fe:95:b0:b0
media: autoselect <full-duplex>
status: inactive
vnic0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1c:42:00:00:08
inet 10.211.55.2 netmask 0xffffff00 broadcast 10.211.55.255
media: autoselect
status: active
vnic1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1c:42:00:00:09
inet 10.37.129.2 netmask 0xffffff00 broadcast 10.37.129.255
media: autoselect
status: active

I'm not really sure what you mean by class-B address.  It's on an RFC1918
(i.e. private) address when I'm on the 10.215.90.0/24 network (A class-C
subnet).  And yes, just for testing, when I'm on the 67.22.168.0/24 subnet,
it's a publicly routable address.

It would be nice to be able to plug in some sort of
encryption/authentication between the server and client.  Until that happens
though, we can always just use a SSH tunnel.

I appreciate you taking the time to look into this.  It appears to be a
problem with the answer from NetNameResolver when I'm on the private
network.  I'm not sure where to go from here though.

On Thu, Sep 30, 2010 at 9:53 AM, Chris Muller <asqueaker at gmail.com> wrote:

> Elliot, you have specified a class-B address??  Do you really have the
> Magma server running on the Net?
>
> Why do you want to use addresses instead of hostnames?  What does
>
>  NetNameResolver localHostName
>
> and
>
>  NetNameResolver localHostAddress
>
> answer for you?
>
>  - Chris
>
> On Mon, Sep 27, 2010 at 6:09 PM, Elliot Finley <efinley.lists at gmail.com>
> wrote:
> > Hello,
> >      I just started playing with Magma, so it may be just me not knowing
> how
> > to use it.  I have a server running in image A on my machine.  In image B
> on
> > the same machine I have the following in a workspace:
> > mySession :=
> > (MagmaRemoteLocation
> > host: '10.215.90.59'
> > port: 51001) newSession.
> > mySession connectAs: 'elliot'.
> > myRoot := mySession root.
> > If I use '127.0.0.1' or 'localhost' as the host, then I get a timeout
> error
> > when calling mySession>>connectAs:
> > It says 'ConnectionTimedOut: Cannot connect to 10.215.90.74:51001'
> > (10.215.90.74 is an address that I've had at one time).  If I
> specifically
> > use '10.215.90.59' as the host, then connectAs: works as normal, but then
> > the following statement 'myRoot := mySession root.' fails with the
> > 'ConnectionTimedOut: Cannot connect to 10.215.90.74:51001' error.
> > Has anyone seen this before?  What am I doing wrong?
> > Thanks in advance,
> > Elliot
> >
> > _______________________________________________
> > Magma mailing list
> > Magma at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/mailman/listinfo/magma
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/magma/attachments/20100930/3977732a/attachment.htm