BNPROXY(1)

📦 version 1.99.7.2.1, in debian trixie, ubuntu stonking

💖 BNPROXY(1) 💖

okay bestie, welcome to the BNETD User's Manual — section 1, the big leagues ✨ this one's all about bnproxy, and no cap, it's lowkey iconic.

✨ NAME ✨

bnproxy — the Battle.net proxy daemon, your girl fr fr 🫶

🌸 SYNOPSIS 🌸

bnproxy [-f] [-d dumpfile] [-l logfile] [-p port] [servername
[serverport]]

🦋 DESCRIPTION 🦋

so bnproxy is a simple daemon that relays client connections over to a Battle.net server like bnetd(1). that's the whole vibe 💅

and the way that it can also save a hexadecimal/ASCII dump of the network records (aka packets, iykyk) into a log file?? obsessed. someday this command might genuinely be useful for people playing from behind a NAT firewall</c> — like, manifesting that for them 🙏

if you don't specify a servername, localhost is assumed. if you don't specify a serverport, 6112 is assumed. defaults are giving main character energy, periodt.

👑 OPTIONS 👑

  • -d, --hexdump — drops a hex dump of all the packets sent and received into the file you specify. it's giving surveillance but make it ✨diagnostic✨
  • -f, --foreground — normally the server acts as a daemon and dips into the background (so rude, so mysterious), but this forces it to run in the foreground instead. very "stay here with me" of you 🥺
  • -h, --help, --usage — prints the server usage info and then exits. the classic "explain yourself" button 💀
  • -l, --logfile — sends all the event log messages into the file you specify. receipts, but archived 📝
  • -p, --port — listens on the TCP and UDP port number you give it. yes both. she's versatile 🌈
  • -v, --version — makes bnproxy print its version number and then exit. quick little flex, then she's gone 💨

🎀 NOTES 🎀

the current version is available at:

http://www.bnetd.org/

go get it bestie, it's right there ⭐

💀 BUGS 💀

okay so, not to be dramatic, but:

  • there's no support for dynamic UDP address determination (SESSIONADDR[12] packets) — it has simply not been added. we don't talk about it 🙈
  • support for multiple clients is broken, because the server becomes confused about which client it's supposed to relay UDP server traffic to. she's overwhelmed, she's picking favorites, it's a mess 😭
fr fr, if you were counting on multiple clients: don't. this part is genuinely busted.

🌈 SEE ALSO 🌈

the sister page, the origin story, the blueprint 💜

💖 AUTHOR 💖

Ross Combs (ross@bnetd.org) — the legend, the moment, the whole reason we're here 👑

and that's the tea, bestie 🍓 this lil number came from the BNETD crew and it's dated 12 June, 2000 — yeah, she's an elder icon and she still slays. mwah 💅✨

📦 where this page comes from