The correct way to go about it would be to put your BGW210 in IP Passthroug mode so only Netgate PFSense were exposed. You'll need to find MAC address of your PFSense and make appropriate changes to BGW210:

On your DNS speculations, by default modern Netgate PFSense uses Unbound and its setup as DNS Resolver mode.   It can work as full resolver or forward-only (say if you insist on using 8.8.8.8 or 1.1.1.1 fully recursive-resolver for doing on the work) - but you need to check Enable Forwarding Mode under Service > DNS Resolver. These are well documented at https://docs.netgate.com/pfsense/en/latest/services/dns/resolver.html

BGW210 or BGW320 (taken from https://www.att.com/support/article/u-verse-high-speed-internet/KM1322413/) can be set to DMZ mode.
From a computer connected to your Wi-Fi gateway:

    Go to your gateway settings.
    Select Firewall and then Advanced.
    Enter your Device Access Code, if asked. You can find this on a sticker on your gateway.
    Turn off everything in Firewall Advanced.
    Select IP Passthrough and set the following:
        Allocation Mode to Passthrough
        Passthough Mode to DHCPS-fixed
    Enter the MAC address of the device to be set up in the Passthrough Fixed MAC address field.
    Select Save and Restart Now.

Good to know: You may have to reboot your computer and Wi-Fi gateway to force a new IP assignment.


if this doesn't work then  might want to look at mapping
since it's PF based, what does /etc/pf.conf looks like on netgate PFSense?

You might want to use tcpdump on /dev/pflog0 to troubleshoot and see what exactly your rules are missing (or insight on rules that isn't working as it should).

good place to start would be https://docs.netgate.com/pfsense/en/latest/diagnostics/packetcapture/tcpdump.html

But these are advanced kung-fu that I don't think average user would possess. (more likely firmware / Embedded DevOp)

after recovered damaged WIF key about a yr ago got abit passive and failed to download all wallet.aes.json in time for the walletID that are known (email) but password and seeds were unknown because fireproof bag was hidden and forgotten.

Long story short really old skewl stacks of 2013-'15 era blockchain.info printed paper wallets were recently found in fireproof bag, with wallet ID entered in the following format:
??-?-?-?-???
and password
and of 19 word non standard blockchain.info recovery seeds.

few walletID paper even had what I believed was backup: several QR code - no its not contain QR code to WIF (in earlier days you could print sheet with all P2PKH + WIF keys but this is not it), but after scanning each one consecutively and concatenate together it appears to be encrypted json backup of sort. pbkdf2_iterations version 2 payload "blahblahblahveryverylongstringcompleteblahblah" is shown.  This was dumped from javascript console from var/obj that believed to hold the encrypted wallet back in 2016 or so (before download-blockchain-wallet.py) was available, and extra attempts were made to try to backup from client side .js memory - as I believe (at the time) that blockchain.info is doing java script kung-fu in memory and session data had all the information needed relating to each wallet-guid instance.

knowing one day I would eventually encounter lost hand hodl (now diamond hand hodl) bag (just as predicted, by accident), back in 2022 I even made attempt to download wallet.aes.json for one that I remembered to have most balance (after scrolling thru email), and waited.

btw contrary to belief blockchain email don't actually contain backup of wallet.aes.json.  was using recovery download-blockchain-wallet.py 3 years ago to download encrypted wallet.aes.json but still unable to open it because did not have time to btcrecover with different wallet guid / possible password pairs.  Now password and non BIP39 mnemonic in the fireproof bag was found it should be super easy to recover if wallet.aes.json for each guid can be retrieved.

as BTC is approaching 99999 finally I started to think that blockchain.com won't easily make it diamond hand hodl friendly.  So I begin to unseal / access the fake make belief self-custody wallet.  Sure enough:

When hitting Blue Continue button, following messages (in the order which) appears briefly

obtain account info
Decrypt wallet data
obtaining encrypted data
Migrating Data

Then red "Invalid Token" is than shown below Email or Wallet ID Field!

the password is correct, because if incorrect password entered field  "Password" would throw different error - "Password doesn't match.  Try again." would appear

and when using login.blockchain.com/beta/auth/recovery "Input your Recovery Phrase" error - "Invalid Recovery Phrase" error was thrown.

I tried ?-?-?-?-???">https://login.blockchain.com/beta/legacy-pages/forgot-password.html?guid=??-?-?-?-???

but it throws Unknown word rejecting
Unknown word midas or tickers
Unknown word incessant
...
...
and so on.

Then I tried to recover with wallet.aes.json from most valuable wallet I believe that was downloaded in 2022 with download-blockchain-wallet.py assist actually turned out to be super easy to recover, since no cracking was needed (passwords were correct as they were written down on wallet paper backup)

I did python3.11 btcrecover.py --wallet wallet.aes.json --dump-wallet wallet2.txt --correct-wallet-password mypasswordfoundinfireprofbagpaperwallets2024 and waalaa! all the WIF and Pubkey was found when cat wallet2.txt.

bcore28 importdescriptors (getdescriptorinfo "wpkh(WIF) found hasprivatekeys:true and has #?? checksum  ) works and recovery was successful

Now I wish there are ways to make ?-?-?-?-???">https://login.blockchain.com/beta/legacy-pages/forgot-password.html?guid=??-?-?-?-??? available again, or make download-blockchain-wallet.py work again (which it throws errors)
Traceback (most recent call last):
  File "download-blockchain-wallet.py", line 76, in <module>
    auth_token = do_request_json("sessions", "")["token"]  # a POST request
  File "download-blockchain-wallet.py", line 72, in do_request_json
    return json.load(do_request(query, body))
  File "download-blockchain-wallet.py", line 66, in do_request
    return urllib2.urlopen(req, cadefault=True)  # calls ssl.create_default_context() (despite what the docs say)
  File "/usr/local/lib/python2.7/urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/local/lib/python2.7/urllib2.py", line 429, in open
    response = self._open(req, data)
  File "/usr/local/lib/python2.7/urllib2.py", line 447, in _open
    '_open', req)
  File "/usr/local/lib/python2.7/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/usr/local/lib/python2.7/urllib2.py", line 1241, in https_open
    context=self._context)
  File "/usr/local/lib/python2.7/urllib2.py", line 1198, in do_open
    raise URLError(err)
urllib2.URLError: <urlopen error [Errno 8] Name does not resolve>

I don't think we're getting to 10k anytime soon.

we had so many 70k visit, so now would be nice to revisit 35k,

I am sure this will solve cash storage that pilled top of filled cabinets starting at 70k.

Hi Op,
can you ban trade chat from being between buyer / seller on your platform involving
*agarodesk.com*

I'm pretty sure people here at bitcointalk is no stranger to cyber squatting and login credential harvesting.

below link is an example why this ban should take precedence before member's bitcoin wallet gets drained.

https://agarodesk[.]com/ad/47758a06-4144-4fb4-b58a-064144afb434/

Keep in mind draining non custodial wallet can be done without login onto your website and type in password (which should be same as above), if they know how to use the offset from password phishing link above to compute the xprv key to allow it determine related utxo and priv key pairs. 

I had similar situation and it turned out some coin generated were not moved for quite sometime.

It is very important to go offline with once you synced to current block height on a new bitcoin core install.

for security and anonymity I would recommend dumpwallet and manually export those address to another machine (because address =public key due to P2PK).  Query those bitcoin address using another machine via tor with blockstream or mempool.space to maintain anonymity as these days communication lines are rspan tapped by nation state actors.

 If my memory served me correctly dumpprivkey won't work in those early version clients there is a separate process that is required to extract private key value, which I believe someone on this forum will be able to cite earlier bitcointalk threads to better help you with this.

台姊妹們大概都夠熟習直接用英語po文吧!
小學2-3年級就開始放學後被送去補習班k英文拉~
不知道對岸情況如何?

History tells us countries like China are buying physical gold and have it shipped just quietly stack physical gold and are de-dollerizing as we speak. 

Why buy? To be successful in doing the same thing for BTC isn't exactly difficult: secretly shut down mining farm, making confusing scam-syndicate claims against bitcoiner saying you all have something to do with money laundering whilst confiscate mining equipment and nationalize hash power to gain traction on acquiring newly mined bitcoins.

Based on those alternatives, there is no point for the money changer to buy it with either depositors fund or reinvest their revenues

There are those whom had done face to face trade for quite sometime so there is no need to get around KYC at all.  Many trade contact from past just needs to be updated and passed on to an fair and firm OG when you are ready to retire from trading due to age and health.

While some advocate for non F2F E-payment and other screening mechanism citing safety concerns are valid, keep in mind good member of bitcoin community are human too and we live in an age that should go back to simpler time and meet everyone and exchange on cyberspace.  Freedom of association is a right, not a privilege.  Exchanging stories and ideas are what made f2f trade enduring in my opinion.

judging by what I've read thus far one must assume KYC is increasing an issue for new bitcoin users and it can slow but unable to stop ongoing bitcoin adoption.  KYC is very expensive and it is financed by drafting ALL depositor's fund in the current centralized financial system to make it into an reality.

To stop bitcoin an nation state or monetary authority may declare Bitcoin illegal just like making it an into national currency actually this helps its adoption, so this is where KYC and lacks of firm regulatory framework comes in.  Uncertainty in national and regulatory policy makes it easy to make arbitrary decisions against members of the bitcoin community, and it will not change until we are the majority.  KYC buys valuable time to introduce centralized digital payment framework similar to Union Pay, wechat pay, TaoBao, AliPay, WeiShin and countless other centralized platforms. 

As bitcoin price hit new low it is getting hard to justify selling bitcoin to pay for GPU rentals - so I'm trying to think outside of the box for finding public key for damaged WIF backup (see post#https://bitcointalk.org/index.php?topic=5380095) that happened approx. an year ago -

but Since the address in question (P2PKH) contains newly generated block rewards from solo hashing over a good period of time, but none of which were spent (unfortunately, and neither do I have an signed message for this P2PKH address) - is there any reason why scriptSig from generation transaction recorded on main net not providing me my public key?  maybe the offset I'm copying is incorrect - or it is just impossible all together

The other place I think May be of help is digging thru stratum blocks logs on the server - which had been sit dormant for about an decade in storage - but this opens up whole range of new issues (log analysis, damage to hardware not used for long time, etc)

Hi ya,

Depends where you're at some places you maybe able to use SMS to bypass internet availability issues.
Wallet such as Machankura is one of them.

https://machankura.com/

for other locations I use https://blockstream.info/tx/push or http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion/tx/push with private tor bridge nodes to push my transaction to bitcoin main net and avoids censorship.

as far as getting your full node sync'ed to full height, one cheap method would be to use blockchain streaming services, some of which is free, which can be found at https://blockstream.com/satellite/#satellite_network-coverage

You can build your own satellite kit or keep your own node up and in sync like I did, but its effectiveness rely depend where you set sail.  Generally speaking you need somewhere close to 2Kbyte/sec of download speed to maintain sync for an full node (for receive payment), but much lesser if you want to send payment (most likely around 200-300 bytes, less if done via PW2PKH)

food court vendors taking bitcoins consumes several dozens blank address daily and now I can wrap this around with script to pump out pre-made QR code wallets that get crontab'ed daily for ssh ftp download to receive payment.  Your script makes unique payment for each microtransaction feasible and so stupidly easy!

What you might not be aware is that it saves me hours of Photoshop cut and paste weekly + Really appreciate this!

Hi and thanks generous comment from everyone~

I found the temporary work around and it works great since last night: generate 40 native bech32 addresses and save it as .png., replace bitcoin:BC1q*** QR photo with what each .png file actually says bc1q**** with .png / .jpg generated from another QR code generator.  merge 4 of those unique bech32 request payment QRs and Print them out + cut it up nightly to have 40 unique wallet address for the next morning.  took me bet. 10-15 minutes for all this.

Then on 10xA4 sized paper @ with 4 native bech32 addresses with modified QR image with correct lower case bc1q*** encoding.

^We have no control: Neither our establishment nor street food vendors renting space at lobby / courtesy areas selling rice balls (飯糰), fish balls, or soy milk had much say on which wallet tourist / bitcoin user should use.  Maybe across the straight in mainland China is better@mandate things - for example: either use compliant wallet like Muun to receive BTC or be outright banned.

The "tool" we use is bCore 23. What is odd about it is when operator press "Create new receiving address" what the QR shown on screen along with code (lower case) don't match what QR really is.  Since no one wants to wait for confirmation with lowest fees when merchant received some payment unconfirmed on modified QR image wallet we have script that analyzes it to make sure transactions are ledgit.  If not screening Bcore node LINE vendor directly with txt description of potential issues so they can bring it up with bitcoin sender in seconds.

can't seems to get BCore 23 to put out images that matches what encode on the QR.
The QR really says bitcoin:BC1q****<SNIP>. we have to instead find another in-house quick-fix ASP.NET app to re-encodes saved .png it into bc1q****<SNIP> and all problem went away.


^ our 40 bech32 address work around QR image on paper @day seems rather equitable for now, until a more permanent solution similar to cypherpunkpay.org (not perfect) that works behind RFC1918 closed network being fully implemented.  

I guess we'll just have to take those 25, 30, 45NTD payments more than once from different non-compliant wallet users on the same lower case bc1q paper wallet when we ran out (you know, some bitcoin-er travels in group. we have no control of that either)

To put in perspective mining fees for each incoming is approx 45NTD (approx $1.45) for non-native segwit alternative.  For room reservation/checkouts that is fine, but for those vending joints in the lobby native segwit becomes significant: breakfast costs 85-120NTD on average, but those problematic native segwit users pays 5-10NTD(~$0.25) minimal fees.  Maybe I'll exploit better alternative with bc1p addresses to make direct bitcoin payment effective.  There are alternatives, of course (LINE Pay, 旺 PAY, or YoYoPay 悠遊付 merchant integration).  

Then there are incoming LN payments as well but settle fund out of it daily for accounting seems rather expensive.  Freedom isn't cheap - even A4 paper prices are out of control.

Hi Guys,

sometime meals/lodging were being paid but by default Bech32 (Segwit) were auto selected on the dropdown box of BCore 23.
this is creating a bit of confusion for our cashiers - had remember to either uncheck create bech32 address to change dropdown to select Base58 so it creates a bit of confusion.

This had to do with wallet implementations I think - because not all can process upper case bech32 addresses. some of them won't even allow prefix / substring that starts with bitcoin:BC1Q*******. (it is a bit irony that bitcoin: part is lower case, whilst address isn't)

did look for command line arguments on wallet options but to no avail (so can be specified when starting Bitcoin core).  Any tips on an work-around are appreciated!

due to wallet content this assessment is quite feasible, not factoring in amount of time I must spent to address development related issues...

Issue had now been shifted to parallel almost hundreds, or almost near a thousands of those GPUs so recovery reasonable amount of time.  This require significant retooling of existing tools available and have it parallelized without incurring excessive space complexity penalties.  I guess will be spending quite a bit of time diving into those topics.

I am afraid you are correct..  blocks were mined approx 5 years ago with dozens of coinbase transactions went into it.
Should have kept wallet for each block mined, something satoshi have done and now I understands why.

Satoshi probably would never have to worry about it since in those days it was P2PK

my WIF paper wallet from around 2013 was damaged due to rats chowing thru area where it was stored, it held majority of my bitcoin holdings from years of solo-mining and after consulting various local experts it appears to require significant computing resources to have it recovered

Now I am giving bitcointalk a try to see if someone here could shed some light on actual algorithmic complexity so to have an idea when would it be technologically / economically feasable to have it recovered

I am using the following example to give you guys an idea on scope of damage:

Let

5KFE3ScWZMf4TdAuVNYKDU7UtTBmHf9M           LHs1AkbD

be the damaged key, and:

suppose the DHiTxZ8xUrg portion was damaged (rat chewed it away..), where the full key *if* successfully recovered in this example should be

5KFE3ScWZMf4TdAuVNYKDU7UtTBmHf9MDHiTxZ8xUrgLHs1AkbD

with 11 char missing now the complexity for recovery is somewhere around 2498664400016553792, or 2.5 x 10^19!

The problem is further complicated by the fact that WIF algorithmically requires 2 rounds of sha256 calculation, which is very slow to checksum in my poor attempt to "guess at" even with access to computing resources with large number of cores (like AWS).

Not sure if someone can offer some formal asymptotic analysis on the aforesaid situation.  Maybe I am not approaching this problem correctly, but I guess someone might have a better idea in similar situations

and of course Happy new year all! 恭喜發財!

If USA rush to actually do this it would be horrible for BTC because it will cause huge surge in bitcoin on-chain transactions.  Any move by USA to actually adopt BTC as legal tender would most likely crush bitcoin network and likely be successfully to bring bitcoin network to an halt; unless all merchants in United States are require to run their own lightening node to accept payment; which obviously can be done by passing new infrastructure bill.

Bitcoin is my bank.

bank holds assets. Assets includes tangible things that are other than properties. Example would be Central bank
bank also makes investment. Example of this would be JP Morgan.

When prices are high, you can purchase things with bitcoin. Example includes gold, silver, education, training, and hosting services.

When prices are low, you can buy back with bitcoin.

as an user of Bitcoin you need to realize Bitcoin is your bank, but it is not an bank that someone manages it for you so you just get money when you like.  The bank you were think of are the North Korean bank where Royal-Court system economy are in practice.  This is, however different than what Bitcoin can offer to individual and entities. 

with that said, Hopefully you understand there is an distinction between royal court economy banking and banking (which includes investments and management of custodianship to various types of liquid assets)

Lets be clear:

Governmental power can be usurped by an small group of elite and powerful families.

The Governmental system, in its ideal form do not want control.  It is by the people and for the people.

With money comes with power.  With power it can influence and exerts control. This is what you saw increasing in the USA today with elimination of middle class.  Power can mean progress or lack of progress for mankind.

situation USA right now is rock in the hard place, because society wants free subsidies, housing, welfare, disability benefits, but no middle class remains.  So either you automates everything, or everything will becomes more expensive because government must print money to overcome the lost of tax base and productive capacity that results in expected revenue growth.

So control, including on-ramp and off ramp to the bitcoin eco-system is a must, because government itself is fight for survival.  This is different then the governmental system - the system as chartered ideally does not require an standard, only those who administers it whom wish to perpetuate its current control for the sake of usurping power and maintain the ability to embezzle from constituency.

Socialism and Maxist sounds very appealing in theory, however it is miserable in practice.

twatter having issues outside of Marxist USA of 2021?
feel so bad they got censored!

just use Gab and get over it.  You can spent some bitcoin there too and go Pro all the way.
Freedom is not free.
Free speech is not free either.
Nothing is Free.  Someone had to pay.
Twitter got US banking cartel / Chicom sponsored stooges front their funds.
If they don't ban free speech than money stop coming.

How hard is it for people to grasp this concept?  It is behooving.