Good day! Maybe this one is an actual bug or I'm seriously losing my mind.
My BBS is configured with two interfaces. The first is my management interface, the second is the BBS. Let us consider the management eth0 and the BBS eth1.
The entire BBS is configured for eth1 via sbbs.ini. All "defaults" are removed and the IP address of eth1 is configured to ensure zero ambiguity. When I attempt to go into IRC Chat to join our amazing SysOps, I notice that I am egressing the BBS via eth0 instead of eth1 (verified via netstat).
For example:
[sbbs@ip-172-31-5-242 ~]$ netstat -an | grep 6667
tcp 0 0 172.31.1.184:6667 0.0.0.0:* LISTEN tcp 0 0 172.31.5.242:34698 73.35.161.200:6667
ESTABLISHED
172.31.1.184 is the IP of eth1. 172.31.5.242 is the IP of eth0.
Based upon this netstat, communication is definitely not going where it's supposed to be going.
I'll take any suggestions you may have to get this fixed.
You can experiment by adding a call to sock.bind() in exec/irc.js to bind to your preferred address, just after the sock=new Socket(); line. See how that works for ya.
Good day! Maybe this one is an actual bug or I'm seriously losing my mind.
My BBS is configured with two interfaces. The first is my management interface, the second is the BBS. Let us consider the management eth0 and the BBS eth1.
The entire BBS is configured for eth1 via sbbs.ini. All "defaults" are removed and the IP address of eth1 is configured to ensure zero ambiguity. When I attempt to go into IRC Chat to join our amazing SysOps, I notice that I am egressing the BBS via eth0 instead of eth1 (verified via netstat).
For example:
[sbbs@ip-172-31-5-242 ~]$ netstat -an | grep 6667
tcp 0 0 172.31.1.184:6667 0.0.0.0:* LISTEN tcp 0 0 172.31.5.242:34698 73.35.161.200:6667 ESTABLISHED
172.31.1.184 is the IP of eth1. 172.31.5.242 is the IP of eth0.
Based upon this netstat, communication is definitely not going where it's supposed to be going.
I'll take any suggestions you may have to get this fixed.
Re: IRC Chat Function
By: Digital Man to Dream Master on Wed Jan 06 2021 01:30 pm
You can experiment by adding a call to sock.bind() in exec/irc.js to bind to
your preferred address, just after the sock=new Socket(); line. See how that
works for ya.
digital man, the experiment worked. Code change:
sock=new Socket();
sock.bind(0,server.interface_ip_address);
Re: IRC Chat Function
By: Digital Man to Dream Master on Wed Jan 06 2021 01:30 pm
You can experiment by adding a call to sock.bind() in exec/irc.js to bind to your preferred address, just after the sock=new Socket(); line. See how that works for ya.
digital man, the experiment worked. Code change:
sock=new Socket();
sock.bind(0,server.interface_ip_address);
netstat output:
[sbbs@ip-172-31-5-242 ~]$ netstat -an | grep 6667
tcp 0 0 172.31.1.184:6667 0.0.0.0:* LISTEN tcp 0 0 172.31.1.184:34523 192.241.178.238:6667
ESTABLISHED
Everything is now egressing from eth1 (BBS Interface).
Thank you!
digital man, the experiment worked. Code change:
sock=new Socket();
sock.bind(0,server.interface_ip_address);
A good temporary fix but we should really fix it properly by implementing the M: and P: ip properties in ircd.conf. I sent Deuce a message on irc so we'll see.
Re: Re: IRC Chat Function
By: Nelgin to Dream Master on Wed Jan 06 2021 06:02 pm
digital man, the experiment worked. Code change:
sock=new Socket();
sock.bind(0,server.interface_ip_address);
A good temporary fix but we should really fix it properly by implementing the M: and P: ip properties in ircd.conf. I sent Deuce a message on irc so we'll see.
Dream Master was talking about the irc client (irc.js).
the 2nd parameter of the M: line in ircd.conf would usually be used to specify the IP address to bind to, however in the synchronet ircd it is commented as "not used" so it appears you cannot choose.
| Sysop: | Chris Crash |
|---|---|
| Location: | Huntington Beach, CA. |
| Users: | 595 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 07:19:08 |
| Calls: | 10,784 |
| Files: | 5 |
| Messages: | 468,802 |