While exploring ODK Aggregate, we encountered this:
1.Installed Aggregate 0.9 on our Linxux Suse, Local Instance. opened http://localhost:8080 on Suse. looks good and ok.
2.The problem, outside Suse, at a client PC within LAN, we are unable
to open Aggregate on http://IPXXXXX:8080.
3.Seems, we cant send anything to Aggregate Server, unable to access
to the above Aggregate.
I got this to work by doing the following in a terminal:
ipfw add [#] fwd 127.0.0.1,8080 tcp from any to me 80
where [#] is fairly arbitrary, like 5. You can see what numbers are already
used with: ipfw list.
-Carl
···
On Tue, Dec 21, 2010 at 2:25 PM, razieq wrote:
Dear Waylon, Yaw
Hi there ODK Enthusiasts,
While exploring ODK Aggregate, we encountered this:
1.Installed Aggregate 0.9 on our Linxux Suse, Local Instance. opened http://localhost:8080 on Suse. looks good and ok.
2.The problem, outside Suse, at a client PC within LAN, we are unable
to open Aggregate on http://IPXXXXX:8080.
3.Seems, we cant send anything to Aggregate Server, unable to access
to the above Aggregate.
Following the above advice I am now able to use IP address to access
ODK Aggregate. Eg, http://192.168.0.12:8080 from PC where ODK
Aggregate is installed. The command that I used in terminal:
···
On Dec 21, 11:02 pm, Carl Hartung wrote:
> I got this to work by doing the following in a terminal:
> ipfw add [#] fwd 127.0.0.1,8080 tcp from any to me 80
>
> where [#] is fairly arbitrary, like 5. You can see what numbers are already
> used with: ipfw list.
> -Carl
>
> On Tue, Dec 21, 2010 at 2:25 PM, razieq wrote:
> > Dear Waylon, Yaw
>
> > Hi there ODK Enthusiasts,
>
> > While exploring ODK Aggregate, we encountered this:
>
> > 1.Installed Aggregate 0.9 on our Linxux Suse, Local Instance. opened
> >http://localhost:8080on Suse. looks good and ok.
> > 2.The problem, outside Suse, at a client PC within LAN, we are unable
> > to open Aggregate onhttp://IPXXXXX:8080.
> > 3.Seems, we cant send anything to Aggregate Server, unable to access
> > to the above Aggregate.
>
> > We read and followed the post about http://10.0.2.2:8080@
>
> >http://groups.google.com/group/opendatakit/browse_thread/thread/c7791...
>
> > Still no result yet, any advice?
>
> > tanks
>
> > --
> > Post: opendatakit@googlegroups.com
> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> > Options:http://groups.google.com/group/opendatakit?hl=en
Following the above advice I am now able to use IP address to access
ODK Aggregate. Eg, http://192.168.0.12:8080 from PC where ODK
Aggregate is installed. The command that I used in terminal:
···
On Dec 21, 11:02 pm, Carl Hartung wrote:
> I got this to work by doing the following in a terminal:
> ipfw add [#] fwd 127.0.0.1,8080 tcp from any to me 80
>
> where [#] is fairly arbitrary, like 5. You can see what numbers are already
> used with: ipfw list.
> -Carl
>
> On Tue, Dec 21, 2010 at 2:25 PM, razieq wrote:
> > Dear Waylon, Yaw
>
> > Hi there ODK Enthusiasts,
>
> > While exploring ODK Aggregate, we encountered this:
>
> > 1.Installed Aggregate 0.9 on our Linxux Suse, Local Instance. opened
> >http://localhost:8080on Suse. looks good and ok.
> > 2.The problem, outside Suse, at a client PC within LAN, we are unable
> > to open Aggregate onhttp://IPXXXXX:8080.
> > 3.Seems, we cant send anything to Aggregate Server, unable to access
> > to the above Aggregate.
>
> > We read and followed the post about http://10.0.2.2:8080@
>
> >http://groups.google.com/group/opendatakit/browse_thread/thread/c7791...
>
> > Still no result yet, any advice?
>
> > tanks
>
> > --
> > Post: opendatakit@googlegroups.com
> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> > Options:http://groups.google.com/group/opendatakit?hl=en