If everything went as expected your new IP should be the same as the public WAN IP of the SSH host you connected to. The two curl invocations show you your WAN IP address before and after the command. alias stun='curl -4 & sshuttle -dns -daemon -pidfile=/tmp/sshuttle.pid -x -r host 0/0 & curl -4 'Īlias xtun='] & kill $(cat /tmp/sshuttle.pid)'Ĭonfiguration of bash aliases varies a lot per OS so I won't include how to set that up here but those two lines above (typically they live in ~/.bashrc) enable you to type stun and then have your traffic appear as if it originates via the target host. You can get started via the command line but `sshuttle` really comes into its own when wrapped with some bash aliases. You can also use pip to install sshuttle which is documented here. Installation on Linux is simple via most package managers. This simple tool is incredibly useful and allows me to route my DNS requests through an SSH tunnel enabling circumvention of firewalls, geo-location content blocks and even protects your traffic from the casual coffee shop packet sniffer. Try again, eliminating the changes one by one to get to the root of the problem.A few years ago I discovered one of those game changing tools. If you get it working, then one of the changes (or a combination of the changes), has "fixed" the problem. Do these things one at a time and test in between. os/x86_64/').Ģ) I'm not sure how your network is really supposed to work (perhaps an ASCII diagram would help?) You have a sock connection going out and then it ssh's back to you machine?īut beyond that, try it with SELinux in permissive mode (the port you're using is not the "normal" ssh port) and also switch the firewall off at both ends. I then had to use a mirror name (as in wget '. So when I tried that same command, I got a list of mirrors (which is expected because that's what we're asking for). Have a look at the file for a clue as to what is going on. 64&repo=os' - that should output the output to a file (which wget will tell you about). Just enclose it in '' as in tsocks wget '. Yeah, wget's not installed by default - RHEL installer tends to use curl.ġ) The shell is interpreting your URL and not passing it properly. They both just keep going so i just kill the process. failed: Transport endpoint is not connected. One of them is going to look like this: - x, - proxy protocol:// host: port Link to GitHub Note that x is small, and it is case-sensitive. This is the tsocks config i use for all servers /etc/nf file: Command line argument to set proxy in cURL Open terminal and type the following command, and press Enter: curl - help Link to GitHub The output is going to be a huge list of options. But in some cases, we may need to disable the current proxy configuration for curl and connect directly. This makes usage of the curl easier and less typing. Yum-config-manager -save -setopt=.skip_if_unavailable=trueĬannot find a valid baseurl for repo: base/7/x86_64 The curl proxy can be configured in the curl configuration file or in the environment variables. Proxy credentials may also be passed in the proxy string and will be URL decoded by Curl. If it is a very temporary problem though, this is often a nice To use a proxy with Curl, you must pass the required proxy address using the -x (or -proxy) command-line option and proxy credentials using the -U (or -proxy-user) command-line switch. So will have to try and fail each time (and thus. Note that yum will try to contact the repo. Configure the failing repository to be skipped, if it is unavailable. If you are using a username and a password to connect, ssh -D 5001 If you are using a public / private key. Just ignore the repository until you permanently enable it again or useĤ. SSH port forwarding or tunneling allows you to forward otherwise insecure TCP traffic inside a secure SSH tunnel from local to destination server. Step 1 Connect to your Server with SSH and create a Tunnel. Disable the repository, so yum won't use it by default. Packages for the previous distribution release still work).ģ. This is most often useful if you are using a newerĭistribution release than is supported by the repository (and the for the repository, to point to a working Contact the upstream for the repository and get them to fix the problem.Ģ. There are a few ways to work "fix" this:ġ. One of the configured repositories failed (Unknown),Īnd yum doesn't have enough cached data to continue. Code: Select all Loaded plugins: fastestmirrorĬould not retrieve mirrorlist $infra error was
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |