| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | BinkD |
Hi! Russell, On Tue, 07 Oct 03, you wrote to me: PQ>> I don't run any sort of *nix. RT> You don't run any sort of *nix, now com'on ... I don't need to. If I want to add a BinkP port I just add it into the Radius string grid of ports, and run a matching port-forward from my firewall server (another string grid interface). Piece of the proverbial, mate. RT> Only thing that needs to be changed are the paths, and BinkD did RT> stomp on my MBSE binkp settings in inetd.conf. :-(( Ermm, umm... yeah, I would have done that. Looks like you'll have to brush up on yer command-line mumbo-jumbo linux voodoo shit, then. =:) RT> Well, I believe it is not wise to have 2 similar programs listening RT> on the same ports, especially when where the files end up is not the RT> same, so I will have to run using different ports from my slant on RT> things. I wonder if Michiel allowed for multiple port access for the same protocol? (I never got that far with MBSE.) Ask him. Might be worthy of a slot on his wish list. Cheers, Paul. --- Radius/W32 4.009-02.01.03/RC10* Origin: Oh! I get it! HAhahahaha...haha... (ZMH only) (3:640/384) SEEN-BY: 633/267 270 @PATH: 640/384 954 774/605 123/500 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.