(update for port 80) |
Puiterwijk (talk | contribs) (Add note on VPN) |
||
| Line 4: | Line 4: | ||
Many times at events, contributors need to access various network resources that may be restricted from the event network. In order to mitigate any issues like this, Fedora Infrastructure has created a proxy server in our openstack cloud that can be used as a proxy from event networks. | Many times at events, contributors need to access various network resources that may be restricted from the event network. In order to mitigate any issues like this, Fedora Infrastructure has created a proxy server in our openstack cloud that can be used as a proxy from event networks. | ||
=== Note on VPN usage === | |||
Because of routing issues, tunnelling a VPN through SSH (which is the solution used for FlockProxy) will NOT be going to work. | |||
So if the internet connection at your hotel or at the campus is limited so that VPN connections can not pass through, you will not have access to the VPN, also not through the FlockProxy. | |||
(this is because after setting the VPN up, the system updates the routing table so that everything is transmitted through the VPN, including the SSH tunnel through which the VPN tunnel just got set up...) | |||
== Transitory == | == Transitory == | ||
Revision as of 03:36, 7 August 2013
FlockProxy
Introduction
Many times at events, contributors need to access various network resources that may be restricted from the event network. In order to mitigate any issues like this, Fedora Infrastructure has created a proxy server in our openstack cloud that can be used as a proxy from event networks.
Note on VPN usage
Because of routing issues, tunnelling a VPN through SSH (which is the solution used for FlockProxy) will NOT be going to work.
So if the internet connection at your hotel or at the campus is limited so that VPN connections can not pass through, you will not have access to the VPN, also not through the FlockProxy.
(this is because after setting the VPN up, the system updates the routing table so that everything is transmitted through the VPN, including the SSH tunnel through which the VPN tunnel just got set up...)
Transitory
The current proxy instance will be active from Monday Aug 5th, to Wed Aug 14th. (For the flocktofedora conference).
Please do not store any data on this server, it will be completely and irrevocably deleted at the end of the conference.
Access
- You will need to have a ssh public key attached to your fedora account system account ( https://admin.fedoraproject.org/accounts )
- You will need to be in cla_done + one other group (the same requirements as access to fedorapeople.org).
- You will need to install sshuttle (available in Fedora and EPEL).
- Run:
(if dns is not working)
sshuttle -r yourfasname@209.132.184.151 0/0
or
(if dns is working)
sshuttle -r yourfasname@flockproxy.cloud.fedoraproject.org 0/0
or (if port 22 is blocked you can use port 80)
sshuttle -r yourfasname@209.132.184.151:80 0/0
or (if port 22 is blocked you can use port 80)
sshuttle -r yourfasname@flockproxy.cloud.fedoraproject.org:80 0/0
- Now all your network traffic should proxy via your ssh connection and you can get your work done.
Disclaimer
We reserve the right to block/close/stop anyone who is interfering with the network for others or otherwise using the proxy in a way that does not serve the best interested of the Fedora Project, our sponsors or our conference hosts. Please be considerate.