Hi All,
Alright. I made the move from Ubuntu to Debian on the BBS system. So far, I've had a few hiccups, but overall I'm liking it.
I am having one problem with DOSEMU though. When I try to run a door, I'm seeing a brief flash on the screen saying some like "MkDir error in creating /root/"
I've never seen this before, and never had any issues with DOSEMU
before. Why would it be trying to create a directory in /root/?
So far, the only changes I've made in the dosemu.conf file, are:
$_cpu_emu = "fullsim"
and
$_com1 = "virtual"
I am having one problem with DOSEMU though. When I try to run a door, I'm seeing a brief flash on the screen saying some like "MkDir error in creating /root/"
Never seen that one before. Could you turn on logging by adding the following to your dosemu.conf file:
Are you launching mystic as root to use lower ports or launching as a
user with setpcap?
I know mystic will run as a different user if you launch as root, but perhaps it 's getting the home directory wrong because it started as
root (and it's trying to create a .dosemu directory)
I'm thinking there's a problem with Mystic... Any of the events that I have running through Mystic are all giving me error 126. I have a script that runs when there's outbound mail called mailout.sh, located in ~/mystic/mailout.sh. The permissions are set as executable.
I know mystic will run as a different user if you launch as root, but perhaps it 's getting the home directory wrong because it started as
root (and it's trying to create a .dosemu directory)
I've been launching it with sudo to use port 23...
I think you were on to something there. I changed the port on the
internal network to 2300, and didn't use sudo to start mis. The events seems to be running right now...
I'm going to go with apam here, how are you starting mis?
Have you tried to run it without sudo and set your various ports >1024
and then create a rule to map connections to the higher ports as root?
That's what I'm doing now, but inside the modem. Port 23 is being
forward to that computer on port 2300.
If the node has a non-standard port, I'm having issues connecting. The logs look like it's trying to connect to port 0, instead of the port indicated. Here is the listing in binkd.cfg:
Did you compile binkd yourself?
I think I found the binaries somewhere... I honestly don't remember, as I've had binkd set up on the system for a few years...
The version is binkd/1.1a-95/Linux.
Yes, you definitely have to compile it again, Buster does a few things different when it comes to accessing the TCP/IP stack.
Alright. I have it compiled fresh from github/pgul/binkd. It looks like I'm still having the issue... :(
Let me setup a buster vm here and see if I can replicate the problem.
I did notice something different with this version of binkd. I'm running it with the -C option, so it reloads when the config file is changed. I had been getting this in the logs with the old version:
Hmmmm, something sounds weird. Can you drop the binary you compiled into my inbox?
It should be in your inbox...
There must be something goofy going on with your system.
I used the binary you sent me and connected to you with my fsxnet credentials as I know you don't operate binkp on the standard port and
it went through just fine as you can see:
17 Jul 18:30:09 [617] BEGIN, binkd/1.1a-99/Linux -P 21:4/100 binkd.cfg
You aren't running iptables or any other type of ip filtering? Your dns setting are all okay as I know you also said you had an issue resolving
a node.
I did notice something else just now... When I first compiled the new version of binkd, I was getting 'binkd/1.1a-99/Linux'. I've restarted
it, and now I'm seeing 'binkd/1.1a-95/Linux'...
When all else fails, start from scratch.
Thanks again for the help. See I'm still working on becoming that linux geek... :)
Thanks again for the help. See I'm still working on becoming that lin geek... :)
We are gonna get you there kicking and screaming if we have to.
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 60 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 20:25:52 |
| Calls: | 516 |
| Files: | 7,009 |
| Messages: | 287,050 |