Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

okey, I'm a complete NAP, so take it easy on me :)

My Situation; My computer is in this stupid cooperate network of the company i work for. They have alot of policies and stuff, so its not possible to make a tunnel/connect to github.com through the normal network interface. But because we still need to be able to do whatever we want, we have wireless, that is open. Smart, eeeh?! The good part; my machine has two interface; wired and wireless.

What I want; I want to route all traffic to github.com through my wireless connection. Nothing more than this, so that I can go and do a "git fetch origin" or similar.

What I found out, tried and failed; My first thought was "ah yeah, lets just add a route!", so thats what I did! But because I cant add a domain, I did a nslookup to find the IP of github, which is 207.97.227.243, so I added a rule like so; "ip route add 207.97.227.240/28 dev wlan0", but if I want to do a "git fetch origin", it says "the remote end hung up unexpectedly". (I configured 'origin' like so; "git remote add origin git@github.com/myusername/mygit.git")

What I hope for; some ingenious guru that bashes my noob-knowledge and points me in the right direction!

thank you so much for any hint..

share|improve this question

closed as too localized by rozcietrzewiacz, Michael Mrozek Oct 14 '11 at 16:25

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

add comment

1 Answer

I was able to figure out what the problem was; I found, that the github repo is actually on 207.97.227.239, therefor my subnetmask was wrong. Changed the routing rule to 207.97.227.0/24, and the traffic started routing, but still failed. I additionally had the problem, that my lease of the dhcp on my wireless was outdated and the gateway had changed.. so a "dhclient3 wlan0" did the trick and now I'm happy like a pumpkin!

share|improve this answer
1  
Since it turned out to be a very localized problem, you should consider closing the question. Otherwise, you could try to think about some additional potential value of this to other users and modify the question. –  rozcietrzewiacz Oct 14 '11 at 11:21
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.