Re: {Disarmed} Re: Sending IP Address in Emails

[Dimitri Yioulos <dy...@onpointfc.com>]

As to the second computer, the reason you can connect  to OM using an inside 
address, but not an outside one, may be a function of your firewall/router.  In 
our environment, we can't go outside to come inside.  It's a security thing.  
We can connect to our OM server using its internal IP address.  But, we can't 
use the external IP address, because we'd be going outside to come back and, as 
Jake pointed out, that door is locked.


On Friday 28 September 2012 3:55:36 pm David Takle wrote:
> Jake:
> Thanks for the data. Most of the IP stuff makes perfect sense. The first
> main thing I was missing was I did not know about the settings in
> red5.properties (I don't recall ever seeing that file or those settings
> mentioned in any of the docs).
>
> But I'm still having trouble with connecting the 2nd computer to the room.
> It does in fact connect when I use the internal IP address 192.x.x.x But
> when I try using the modem's IP address, I get "unable to connect." Based
> on what I see in the other responses, it looks like I need to get access to
> my modem's admin and set something for port 5080. Is that correct?
>
> ~David
>
> > The IP you’re seeing, 192.xx.xx.xxx, is an internal IP address. The way
> > the internet is setup, there are billions of networks connected together.
> > Imagine the router and all other computers that are connected to that
> > router, as your network.
> >
> > All computers have low firewall settings within their own network. So
> > naturally, connecting to 192.xx.xx.xx from another 192.xx.xx.x machine
> > won’t cause nearly as many security issues as connecting to the external
> > IP address.
> >
> > The way your router communicates with the world, is it has it’s own IP
> > address. Just like your mailing address; they’re all unique. Your router
> > determines WHICH internal computer(rather it be 192.168.0.1, or
> > 192.168.0.2) made the request and it handles the processing of that
> > request.
> >
> > Think of your router as your internet middle man. Whenever you make a
> > request to the internet, it first goes through your router. Your router
> > gets the request, something in the form of, “REQUEST FROM <computer name>
> > TO <wherever> SESSIONSTAMP <stamp> TTYL<time to live>”
> > When that request comes back from <wherever>, your router KNOWS which
> > local computer made the request; thus delivering the information to the
> > computer.
> >
> >
> >
> > Your external IP address, is your REAL ip address that is used for
> > communication with any and ALL computers on your network. If you wish to
> > access ANY resource from a networked computer, you MUST use the REAL ip
> > address(your routers IP.) Your router will take care of handling all of
> > your requests, so don’t worry about that. Just open up the ports that you
> > need, and start your service.
> >
> > Be sure you have opened the port in Windows Firewall(or whatever OS) AS
> > WELL as the router.(assuming you have more than one layer of security.)
> >
> >
> > Now, once you have that set. locate the file “red5.properties”(typically
> > within the /dist/ folder of your openmeetings directory.) If you still
> > cannot find it, search your machine for it.
> >
> >
> > I was able to do a ctrl+h(replace all) and replace ALL instances of
> > “.host=0.0.0.0” with “.host=YourIPHere”.
> >
> >
> > Hopefully this will give you a thourough understanding of what
> > communication is going on between your machine, your router, and the rest
> > of the internet.
> >
> > Remember, the internet is nothing more than billions of networks that
> > communicate with eachother.
> >
> > -Jake
> >
> >  *From:* David Takle <dj...@gmail.com>
> > *Sent:* Friday, September 28, 2012 3:30 PM
> > *To:* openmeetings-user@incubator.apache.org
> > *Subject:* Re: Sending IP Address in Emails
> >
> > Please elaborate --- I don't understand that sentence.
> > ~David
> >
> > On Fri, Sep 28, 2012 at 3:16 PM, Jacob Gaiski <jg...@emich.edu> wrote:
> >>   Did you set the bindings to your external IP address in
> >> red5.properties?
> >>
> >>
> >>
> >>
> >>  *From:* David Takle <dj...@gmail.com>
> >> *Sent:* Friday, September 28, 2012 3:13 PM
> >> *To:* openmeetings-user@incubator.apache.org
> >> *Subject:* Re: Sending IP Address in Emails
> >>
> >>  Dimitri,
> >> Your comment raises a lot of questions for me.
> >> First, are you using a laptop/desktop for your server? If so, how did
> >> you get a domain name for it?
> >> Second, using 'ipconfig' on my XP, I got a 192.168.x.x address that
> >> worked fine from my 2nd computer. Was that only because it is on the
> >> same side of the modem? Would that address not work for the rest of the
> >> world to use?
> >> Thanks!
> >> ~David
> >>
> >> On Fri, Sep 28, 2012 at 3:04 PM, Dimitri Yioulos 
<dy...@onpointfc.com>wrote:
> >>> I've found that you need to log into OM with the FQDN of your OM server
> >>> (e.g.
> >>> http://openmeetings.mydomain.tld:5080/openmeetings).  At first, I was
> >>> using the
> >>> internal address of the OM server, so my invitees were instructed to go
> >>> to the
> >>> meeting at http://192.168.x.x<meeting_id>.  Clearly, that didn't work.
> >>> Others
> >>> may know of another way to accomplish what you're after.
> >>>
> >>> Dimitri
> >>>
> >>> On Friday 28 September 2012 2:56:08 pm David Takle wrote:
> >>> > The Derby DB went nutso on me, so I started over with MySQL.
> >>> > Things are working nicely now.
> >>> > However, when I send out an email invite, it says "localhost" which
> >>>
> >>> means
> >>>
> >>> > nothing to the recipient.
> >>> > How do I send my IP address in the email?
> >>> >
> >>> > Further, how do I get the IP address of my PC when it goes through a
> >>> > wireless router? If I go to a website that provides my IP address, it
> >>>
> >>> gives
> >>>
> >>> > the address of my router, not the PC. If I substitute that IP address
> >>>
> >>> in
> >>>
> >>> > the email invitation, it does not connect to OpenMeetings because the
> >>> > router does not recognize the request.
> >>> >
> >>> > ~David
> >>>
> >>> --
> >>> This message has been scanned for viruses and
> >>> dangerous content by MailScanner, and is
> >>> believed to be clean.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.