Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I've been researching everywhere and couldn't solve the problem. I'm receiving the error:
"Status: Failure-Test failed: IO Error: Got minus one from a read call." when trying to connect to the Oracle server running on the VirtualBox in my Macbook.
What I did so far:
Installed Windows 10 x64 with default configuration on VirtualBox
Installed Oracle 11 XE 112 Win 64 on the Windows installed in the step #1
Installed SQL Developer 4.0.2.15 on my Macbook (OS X El Captain)
On VirtualBox, went to Network (Attached to NAT) and added port forwarding with:
host IP: 127.0.0.1
host port: 1521
guest ip: tried empty and after tried using my mac ip (192.168.2.68)
guest port: 1521
I also tried adding a Bridged second adapter. No luck.
Tested the Oracle local connection on Windows with the sql command line utility ("connect hr/hr") and could connect successfully.
Tested the Oracle listener on Windows using the lsnrctl utility ("status") and could see the "xe" listener active.
On my Mac, tried to connect using SQL Developer with every possible combination that I could imagine:
username/password: hr/hr
hostname: 127.0.0.1 / localhost / 10.0.2.15 (that's the virtual Windows ip)
service name: xe / xexdb / orcl
tried the same for SID.
Every time that I click in test, I receive the error mentioned before.
Disabled the firewall on the virtual Windows
Please, I researched everywhere here, google, oracle community, VirtualBox community and nothing. Thank you so much in advance.
ifconfig on my mac:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.94.0.2 netmask 0xff000000
inet 127.94.0.1 netmask 0xff000000
nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 54:26:96:e0:e7:57
inet6 fe80::5626:96ff:fee0:e757%en0 prefixlen 64 scopeid 0x4
inet 192.168.2.68 netmask 0xffffff00 broadcast 192.168.2.255
nd6 options=1<PERFORMNUD>
media: autoselect
status: active
en1: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
options=60<TSO4,TSO6>
ether 32:00:1b:a0:70:e0
media: autoselect <full-duplex>
status: inactive
en2: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
options=60<TSO4,TSO6>
ether 32:00:1b:a0:70:e1
media: autoselect <full-duplex>
status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
ether 06:26:96:e0:e7:57
media: autoselect
status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
ether 6a:0e:9b:1d:78:7b
inet6 fe80::680e:9bff:fe1d:787b%awdl0 prefixlen 64 scopeid 0x8
nd6 options=1<PERFORMNUD>
media: autoselect
status: active
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 56:26:96:0e:29:00
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 5 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 6 priority 0 path cost 0
nd6 options=1<PERFORMNUD>
media: <unknown type>
status: inactive
vboxnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:27:00:00:00
inet 192.168.56.1 netmask 0xffffff00 broadcast 192.168.56.255
ipconfig on the virtual Windows box:
Your VirtualBox port forwarding configuration is incorrect, guest IP should be 10.0.2.15, not your host IP address. After that, you should be able to connect through 127.0.0.1:1521 on your host OS.
I couldn't find a solution installing Windows 10, but it worked super fine following the instructions of this post
Related
Getting this action for days in Ubuntu 19.04 in wsl2 on Windows.
$ git clone https://github.com/gohugoio/hugo.git
Cloning into 'hugo'...
error: RPC failed; curl 56 GnuTLS recv error (-12): A TLS fatal alert has been received.
fatal: The remote end hung up unexpectedly
I tried recompiling git to use openssl, didn't do anything.
I tried both ssh and https.
I tried to modify git settings for http.
I modified all kinds of git memory settings.
Nothing currently on Stack Overflow is correct for this issue.
I completely reinstalled Windows. Nope, still hosed.
Four days of Whiskey Tango Foxtrot... then I found it.
The latest Windows Hyper-V has issues with your wifi driver. You need to get the latest from https://downloadcenter.intel.com/download/28876/Windows-10-Wi-Fi-Drivers-for-Intel-Wireless-Adapters?v=t
Once the new drivers are installed, you can marvel at how git in wsl2 totally does what it is supposed to. I will never get those 5 days of my life back. I hope this will keep you from losing 5 days of yours.
Here is the issue: https://github.com/microsoft/WSL/issues/4253
Update Nov. 2020: the latest comments on WSL2 4253 point out to:
set MTU to 1350 (same as VPN interface):
sudo ifconfig eth0 mtu 1350
# or
ip link set dev eth0 mtu 1350
Check your MTU:
PS C:\> netsh interface ipv4 show subinterface
MTU MediaSenseState Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
4294967295 1 0 117945 Loopback Pseudo-Interface 1
1500 1 879583365 308029141 Wi-Fi
...
1500 1 3616963 2778319 vEthernet (WSL)
vs.
➜ ip addr | grep mtu
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
A Windows 10 build 20231 might be needed to ensure issue 5821 "WSL vEthernet adapter shows up as disconnected" is fixed.
B. Agustín Amenábar Larraín explains:
Until this issue I never had heard of MTU, and it was hard for me to believe that was the cause, well it is.
I'm having isues when my Pulse Secure VPN is connected and I'm trying to connect to the internal self-hosted Gitlab.
SSH traffic to the regular internet is fine.
I'm using WSL2 Ubuntu 20.04, if I drop it to WSL1, all works as expected (Same for Debian).
Try upgrading your drivers first, that thidn't work for me.
First open a PowerShell prompt and type:
netsh interface ipv4 show subinterface
You will get an output like the following:
MTU MediaSenseState Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
4294967295 1 0 5974969 Loopback Pseudo-Interface 1
1500 1 2678641808 213293706 Wi-Fi
1500 5 0 0 Local Area Connection* 1
1500 5 0 0 Local Area Connection* 2
1500 1 0 529702 vEthernet (Default Switch)
1300 1 2106 509236 vEthernet (WSL)
1200 1 553027168 20290571 Local Area Connection* 13
1500 1 0 22759124 VirtualBox Host-Only Network #3
1500 5 0 0 Bluetooth Network Connection 4
The key is in the Local Area Connection 13 MTU* (The name and value can change from machine to machine), that is the VPN interface. In my case it's 1200 which is why
set MTU to 1350 (same as VPN interface):
sudo ifconfig eth0 mtu 1350
didn't work for me... and I didn't know how to get the VPN Interface MTU.
(I also hated to install ifconfig which is deprecated in favor of ip).
Now that we know, you can change the VPN MTU from Windows it in a PowerShell with Elevated Privileges,
netsh interface ipv4 set subinterface "Local Area Connection* 13" mtu=1400 store=persistent
If you want to skip the next step, you can set it to 1500, but you are leaving no room for the VPN to wrap the packets, for example I have had trouble with Github because of setting it to 1500.
Then, inside your WSL2 distro, you can check your current MTU values with:
❯ ip addr | grep mtu
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
5: sit0#NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
We care about eth0 (the virtual ethernet connection to Windows), you have to set a matching MTU to where you left it in the previous step.
sudo ip link set eth0 mtu 1400
Sadly both settings get resetted every time you start a new VPN session, or restart the WSL2, or even switch from WLAN to LAN.
Leonardo Oliveira adds:
Your solution to the problem was similar to mine, however I changed the Ethernet MTU inside on my WSL2 to the same numbering I saw in windows power shell (Ethernet WSL), and that way it worked for me.
I am running a VM (Debian) on MacOs using VMware Fusion. The VM has fixed IP address (required) and the networking is bridged. It all works very well in my local network under 192.168.1.XXX ip range. The problem is when I leave home and connect to internet via 4G or some public wifi etc. In this situation my Host OS (Mac) obviously gets a different ip address and the VM (Debian) becomes inaccessible from the host mac os. I would really like to be able to keep the VM on the fixed 192.168.1.XXX address even outside of my home network. That is to be able to connect to the guest from the host and also to connect from the guest to the outside internet (as I am able to do when on the home network). Could you please advise on ways how to achieve that. Thank you.
EDIT1:
More googling gained this link .. I followed the steps and created adapter as per the screenshot attached. I am now able to ssh to the VM from the MacOs host (progress!), however the connectivity from the Debian VM to the internet still does not work. Ping 8.8.8.8 fails. My network setup on the Debian VM is:
/etc/network/interfaces:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.177
netmask 255.255.255.0
gateway 192.168.1.1
/etc/resolv.conf:
nameserver 192.168.1.1
nameserver 8.8.4.4
EDIT2:
netstat -nr on the host:
Destination Gateway Flags Refs Use Netif Expire
default 172.20.10.1 UGSc 141 64 en0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 5 420 lo0
169.254 link#10 UCS 0 0 en0 !
172.16.37/24 link#19 UC 2 0 vmnet1 !
172.16.37.255 ff:ff:ff:ff:ff:ff UHLWbI 0 9 vmnet1 !
172.20.10/28 link#10 UCS 1 0 en0 !
172.20.10.1/32 link#10 UCS 1 0 en0 !
172.20.10.1 XXXXXXXXXXXXXXXXX UHLWIir 56 440 en0 1192
172.20.10.6/32 link#10 UCS 0 0 en0 !
172.20.10.15 ff:ff:ff:ff:ff:ff UHLWbI 0 9 en0 !
192.168.1 link#20 UC 2 0 vmnet3 !
192.168.1.177 0:50:56:35:35:b UHLWIi 2 756 vmnet3 1180
192.168.1.255 ff:ff:ff:ff:ff:ff UHLWbI 0 9 vmnet3 !
192.168.114 link#21 UC 2 0 vmnet8 !
192.168.114.255 ff:ff:ff:ff:ff:ff UHLWbI 0 9 vmnet8 !
224.0.0/4 link#10 UmCS 2 0 en0 !
224.0.0.251 1:0:5e:0:0:fb UHmLWI 0 0 en0
239.255.255.250 1:0:5e:7f:ff:fa UHmLWI 0 54 en0
255.255.255.255/32 link#10 UCS 1 0 en0 !
255.255.255.255 ff:ff:ff:ff:ff:ff UHLWbI 0 128 en0 !
According to the VMware docs here, the ping from the guest to the outside should "just work" in this setup, but it does not.
Try using a host-only or NAT network setup instead of bridged. A bridged adaptor will always give your VM an IP address from whatever wireless/ethernet network your host machine resides in at a given time. Using a host-only or NAT setup should allow you to create a private network between your host and VM in which you can get a static IP for your VM. The link I posted is for VMware Workstation, but the network options should be relevant to Fusion as well.
Talking to VMware support gained a solution that is acceptable. They recommended setup with 2 adapters. This way both ssh into (via one adapter that keeps the same fixed internal IP address) and connections to the internet (second adapter with dhcp) work fine.
I am trying to understand what happens when I put on mac in monitor mode. Without the monitor mode, using ifconfig, I find that 'en0' is the active interface. However, in monitor mode, this is what I get:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether 70:56:81:b9:43:e5
nd6 options=1<PERFORMNUD>
media: autoselect (<unknown type>)
status: inactive
en1: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
options=60<TSO4,TSO6>
ether 32:00:1a:7f:0a:40
media: autoselect <full-duplex>
status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
ether 02:56:81:b9:43:e5
media: autoselect
status: inactive
awdl0: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> mtu 1484
ether ee:85:08:e0:ba:17
nd6 options=1<PERFORMNUD>
media: autoselect
status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 72:56:81:9b:d1:00
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 5 priority 0 path cost 0
nd6 options=1<PERFORMNUD>
media: <unknown type>
status: inactive
I am trying to use scapy for sniffing wireless network. So, when I run scapy, it shows iface as 'lo0' and it does not capture any packet. I have looked at a lot of answers regarding this, but most of them are for ubuntu and say that when you put your system in monitor mode, you get 'mon0' interface and then pass this to your scapy and sniff. But in mac, I am not getting anything like the 'mon0', in fact all the interfaces goes inactive in monitor mode. Could some one please help me understand what is happening?
PS: WireShark and Tcpdump work just fine in monitor mode and scapy too captures frames when not in monitor mode. But I am interested in management frames, so I need scapy to capture those on monitor mode. TIA:)
This is an old question, here is the answer:
with older versions of scapy, it simply was not possible
with newer scapy versions (2.4.0+), simply sniff using the monitor argument
sniff([args], monitor=True)
It shows all packets !
I think you're looking for something like this: How can I put mac os x en1 interface into monitor mode to use with python3 scapy?
It is possible, shouldn't be a problem to switch between python3 and python27
I know this is a old question but I had the same problem. I'm unsure as to why en0 appears to be deactivated after running airportd en0 sniff 1 or airport sniff.
To keep the device active while monitoring you can instead use tcpdump.
Example:
$ sudo tcpdump -nnvs0 -I -i en0 -w output.pcap
$ ifconfig
...
en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether 60:03:08:a5:fa:0c
inet 192.168.1.33 netmask 0xffffff00 broadcast 192.168.1.255
media: autoselect
status: active
Hope this helps :)
on my MacbookPro 15'' Retina, with OSX 10.9.4, I want to be able to:
route all single ip traffic to localhost.
My Goal is this:
I type http://192.168.1.54/test.html in the browser and I get what I normally get from
http://localhost/test.html
This is what I tried (en4 is the one I get internet connection from):
______$ sudo route add 192.168.1.54 localhost -ifp en4
checking the list
______$ sudo route add 192.168.1.54 localhost -ifp en4
add host 192.168.1.54: gateway localhost
______$ netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 42 4 en4
127 127.0.0.1 UCS 0 3 lo0
127.0.0.1 127.0.0.1 UH 50 15380 lo0
...
192.168.1.54 127.0.0.1 UGHS 0 0 en4
...
But the ping of 192.168.1.54 isn't working
I tried also the loopback interface with
______$ sudo route add 192.168.1.54 localhost -ifp lo0
getting the same result: nothing.
I'm kind of a newbie in this stuff, so any help will be great
Fire up your Terminal and type the following:
sudo ifconfig lo0 alias 192.168.66.66
After entering your password, that will redirect requests for 192.168.66.66 to the localhost/loopback adapter.
And if you need to remove this redirect, try
sudo ifconfig lo0 -alias 192.168.66.66
Source: http://www.vincecutting.co.uk/web-development/redirect-ip-address-back-to-localhost-on-mac-osx/
You'll need to create a mac virtual interface pointing to 192.168.1.54. Otherwise there is no one to reach at 192.168.1.54 and hence why your ping is failing.
In linux it's pretty straight forward to create additional virtual interfaces.
On my mac osx machine I was able to go into Systems Preferences --> Network
then hit the + sign to add an additional interfaces.
I picked Ethernet as my interface type and assigned the address of 192.168.1.54, 255.255.255.0 subnet mask and 192.168.1.1 as the default router.
Now both my primary 192.168.1.10 and my virtual 192.168.1.54 interfaces are up and pingable.
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
ether 0c:4d:e9:9a:1c:a3
inet6 fe80::e4d:e9ff:e936:1ca3%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255
inet 192.168.1.54 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=1<PERFORMNUD>
media: autoselect (100baseTX <full-duplex>)
status: active
My-Book-Pro:~ root# ping 192.168.1.10
PING 192.168.1.10 (192.168.1.10): 56 data bytes
64 bytes from 192.168.1.10: icmp_seq=0 ttl=64 time=0.095 ms
64 bytes from 192.168.1.10: icmp_seq=1 ttl=64 time=0.101 ms
My-MacBook-Pro:~ root# ping 192.168.1.54
PING 192.168.1.54 (192.168.1.54): 56 data bytes
64 bytes from 192.168.1.54: icmp_seq=0 ttl=64 time=0.085 ms
64 bytes from 192.168.1.54: icmp_seq=1 ttl=64 time=0.091 ms
I'm trying to connect to a webserver that's running on my mac OSX 1.6. I'm able to connect to it locally using http://127.0.0.1:8888/myapp but when I attempt to connect to it using my machine's local IP address (http://192.168.1.15:8888/myapp IP shown below) from the same machine (or another on the network) I cannot connect. I can ping the LAN IP address.
I've tried adding IP forwarding to my router for port 8888 but it didn't help.
I've checked and the OSX firewall is disabled
Can anyone suggest what else is blocking the connection?
Here's what I get when I run ifconfig:
~ :ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1f:5b:e8:16:4d
media: autoselect status: inactive
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::21e:c2ff:febf:4809%en1 prefixlen 64 scopeid 0x5
inet 192.168.1.15 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:1e:c2:bf:48:09
media: autoselect status: active
supported media: autoselect
fw0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:1f:5b:ff:fe:2b:b3:3c
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
en5: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether 00:1e:c2:8e:0f:45
media: autoselect status: inactive
supported media: none autoselect 10baseT/UTP <half-duplex>
en2: flags=8922<BROADCAST,SMART,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether 00:1c:42:00:00:00
media: autoselect status: inactive
supported media: autoselect
en3: flags=8922<BROADCAST,SMART,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether 00:1c:42:00:00:01
media: autoselect status: inactive
supported media: autoselect
Your webserver is probably binding to the loopback interface by default. Applications can "bind" to specific interfaces - if it only listens on the loopback interface, you'll be able to connect via a 127.x.x.x ip but not an external ip. You can look at the "Network Utility" -> Netstat -> display state of all socket connections, which will display all open sockets. Further debugging will require the relevant lines from this (probably the one on port 8888) and potentially what webserver you're running...
This was working fine for me and then it just stopped working all of a sudden. I don't believe I changed anything in my Run/Debug configurations, but maybe I did.
Regardless, the answer is to add the --address=0.0.0.0 parameter to the Run/Debug configuration. To do this:
Right-click your project.
Choose Run As... -> Run Configurations
Make sure your project is selected in the Run Configurations dialog and choose the Arguments tab.
Insert the argument: --address=0.0.0.0
As I said, this was working for me right along and I hadn't set this parameter before that I remember. Anyway, I added it and now things work fine.
TR
Unless this is programming related this question might belong on ServerFault or SuperUser.
In any case, if you are writing an application on Mac OS perhaps you need to specify
the exact interface your application is listening on.
BTW - I think this was user error. I think I was probably running GWT in hosted mode with a Firefox plugin. There was no webserver running or listening to port 8888 which is why it didn't show up!