From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Firewall blocking access to monotone server?
Date: Sat, 01 Dec 2007 14:00:29 +0100 [thread overview]
Message-ID: <47515AED.1000900@gmx.net> (raw)
In-Reply-To: <A0AACB011FF0474492071F3E72FB188F958C5A@USSYML02.ad.sjm.com>
[-- Attachment #1: Type: text/plain, Size: 2544 bytes --]
Hi,
regarding your firewall issue. Once upon a time port 4691 was blocked on
my internet connection, too (I am connected through a community-operated
public wireless meshnetwork called Freifunk).
Thanksfully I have SSH access to a box ('peking') at my university.
First I created a SSH tunnel:
ssh -L4691:org.openembedded.dev:4691 peking -N
and then led all traffic go to through it:
mtn --db OE.mtn pull localhost org.openembedded.dev
Worked like a charm. :)
If outgoing ssh is blocked by the companies' firewall you should ask
them to open it though.
Regards
Robert
Tiller, Jason schrieb:
> Hello, OE folx!
>
> I approached the list a couple of weeks ago asking about running OE under Cygwin. The overwhelming consensus was that I shouldn't even embark on that headache-laden path and instead scare up a Linux box for my OE work. Well, I took your considered advice and now I'm trying to get OE running.
>
> I'm running on a 400MHz P-III with 256MB of memory running RHEL 4. The OS is mandated by my IT guys. I got everything down, finally got everything built (well, so far), including git, svn, mtn, boost, (1.33.1), bb, and a whole host of other packages. My poor little box has been compiling its little brains out. I think I have everything in place.
>
> I read the tutorial and got stuck at the actual retrieval of the mtn database. I downloaded the mtn 0.36 OE snapshot, but when I try to do the first "mtn pull" against monotone.openembedded.org, the connection hangs. It also hangs against the other servers that have been mentioned. I think this is due to our company's draconian firewall policy.
>
> If I were to go to my IT guys and ask them (nicely) to help me out, what do I need to tell them in terms of the port/protocol issues? I'll need to convince them that this is a safe proposition, but I'm sure exactly what I'm asking for.
>
> Thanks in advance. I *really* want to give this a try since WindRiver quoted me $60k+ for a WRLinux distro/tools/support, just for the first year. Geez, I'm the *only* programmer at my site - there's no way my boss will fork over that kind of money. So, I may end up having to roll my own.
>
> Wish me luck!
>
> ---Jason
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2007-12-01 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 17:21 OE/snapshots is not really for different mtn ver John Lee
2007-11-29 19:09 ` Leon Woestenberg
2007-11-29 19:51 ` Koen Kooi
2007-11-30 2:30 ` Grant Edwards
2007-11-30 15:45 ` Grant Edwards
2007-11-30 5:41 ` Firewall blocking access to monotone server? Tiller, Jason
2007-11-30 7:25 ` Hans Henry von Tresckow
2007-11-30 17:51 ` Florian Boor
2007-12-01 13:00 ` Robert Schuster [this message]
2007-12-01 18:39 ` Cliff Brake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47515AED.1000900@gmx.net \
--to=thebohemian@gmx.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.