{"action":"opened","issue":{"url":"https://api.github.com/repos/ethereum/go-ethereum/issues/3046","repository_url":"https://api.github.com/repos/ethereum/go-ethereum","labels_url":"https://api.github.com/repos/ethereum/go-ethereum/issues/3046/labels{/name}","comments_url":"https://api.github.com/repos/ethereum/go-ethereum/issues/3046/comments","events_url":"https://api.github.com/repos/ethereum/go-ethereum/issues/3046/events","html_url":"https://github.com/ethereum/go-ethereum/issues/3046","id":179390380,"number":3046,"title":"New geth version will not accept --nat=none","user":{"login":"newmzy","id":17661766,"avatar_url":"https://avatars.githubusercontent.com/u/17661766?v=3","gravatar_id":"","url":"https://api.github.com/users/newmzy","html_url":"https://github.com/newmzy","followers_url":"https://api.github.com/users/newmzy/followers","following_url":"https://api.github.com/users/newmzy/following{/other_user}","gists_url":"https://api.github.com/users/newmzy/gists{/gist_id}","starred_url":"https://api.github.com/users/newmzy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/newmzy/subscriptions","organizations_url":"https://api.github.com/users/newmzy/orgs","repos_url":"https://api.github.com/users/newmzy/repos","events_url":"https://api.github.com/users/newmzy/events{/privacy}","received_events_url":"https://api.github.com/users/newmzy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-27T03:39:50Z","updated_at":"2016-09-27T03:39:50Z","closed_at":null,"body":"Ever since I started using it many months ago, the only way for me to use the Mist wallet on my Windows 10 desktop machine has been to run geth first with (at least) the following switches\r\n\r\n--nat=none --rpc\r\n\r\n...then run the wallet. If I run geth without any switches, it gets as far as \"starting server\" and that's it. If I run the wallet on its own (where I think it runs geth first anyway) I get the same result but with the following error messages:\r\n\r\n![wallet_output01](https://cloud.githubusercontent.com/assets/17661766/18859167/3bb295d4-84a4-11e6-89f2-469e6714af49.jpg)\r\n\r\nI have been doing it this way for months, after I read about someone with a similar problem to mine. Until quite recently - when the first memory leak bug happened, it has actually worked OK as long as I run geth with those switches first, then run the wallet. Since the latest two versions,  4.1.12 & 4.1.13 - if I use the --nat=none switch geth just spits out a few pages of what looks like programming code to me and then halts. I have been getting geth as binary files and I have noticed that up to 4.1.11 the filesize of geth was slowly increasing, but the newer ones are smaller. Is it possible that the developers have removed some functionality which includes that switch?\r\n\r\nI do have an installation of Linux Mint on a laptop and I have considered that maybe I should use geth and the mist wallet there since it's probably developed in Linux, but I have no idea how to transfer a wallet between different machines and operating systems, and I am far less confident using Linux than I am with Windows.\r\n\r\nI can run Parity in geth mode and then run the Mist wallet and it syncs but then I have another problem with the wallet not being able to send ETH, which I have send a fault notice about to the wallet repo.\r\n\r\nThe photos below are the output from (an admin level) Windows command line, after I run:\r\n\r\ngeth --nat=none\r\n\r\n![geth_output01](https://cloud.githubusercontent.com/assets/17661766/18858895/14b898f4-84a2-11e6-8f70-0d543073b319.jpg)\r\n![geth_output02](https://cloud.githubusercontent.com/assets/17661766/18858896/14bb89ba-84a2-11e6-8ab3-5a1ab7c70411.jpg)\r\n![geth_output03](https://cloud.githubusercontent.com/assets/17661766/18858894/14b6b32c-84a2-11e6-81a8-a900101d2795.jpg)\r\n![geth_output04](https://cloud.githubusercontent.com/assets/17661766/18858893/14b6a92c-84a2-11e6-99e8-b7274eefd5f4.jpg)\r\n![geth_output05](https://cloud.githubusercontent.com/assets/17661766/18858897/14bd953e-84a2-11e6-9d9a-c5fa96fd6207.jpg)\r\n\r\nSInce I have multiple issues, and quite a lot of ETH (to me anyway - over 300) in the wallet - this is very stressful. I am actually mining ETH - not on the machine with this problem, and the account on the wallet is where my mining pool shares go.\r\n\r\n#### System information\r\n\r\nGeth version: 1.4.13\r\nOS & Version: Windows 10\r\n\r\n#### Expected behaviour\r\n\r\nI expect geth to connect to the network and start syncing\r\n\r\n\r\n#### Actual behaviour\r\n\r\ngeth spits out a whole lot of what looks like raw code to me (I'm not a programmer) and then stops.\r\n\r\n#### Steps to reproduce the behaviour\r\n\r\nstart using latest version of geth (this started happening 1 or 2 versions ago).\r\n\r\nrun geth with --nat=none (and --rpc) switch appended to it - if I run it without --nat=none it runs but will not sync - I believe it cannot connect to other nodes. \r\n\r\n[backtrace]\r\n````\r\n"}}
{"actor":{"display_login":"newmzy"}}