Hello Wilfred,

MvdV>> Anyway, it is no good for those who need disfferent ports for
MvdV>> IPv4 and IPv6.

You can, but you will have to start multiple instances of binkd, with different configurations.

Is that theory or has anyone actually tried that?


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.eu (2:280/5555)

Hi Michiel,

On 2018-01-08 17:22:44, you wrote to me:

MvdV>>> Anyway, it is no good for those who need disfferent ports for
MvdV>>> IPv4 and IPv6.

You can, but you will have to start multiple instances of binkd, with
different configurations.

MvdV> Is that theory or has anyone actually tried that?

For me it is theory. But aren't there a number of nodes who do this?

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Monday January 08 2018 18:55, Wilfred van Velzen wrote to Michiel van der Vlist:

MvdV>>>> Anyway, it is no good for those who need disfferent ports for
MvdV>>>> IPv4 and IPv6.

You can, but you will have to start multiple instances of binkd, with
different configurations.

MvdV>> Is that theory or has anyone actually tried that?

For me it is theory. But aren't there a number of nodes who do this?

Yes, there are. :)

You can even run the same main config and just 'include' the task specific parts. Only 'iport' for example.

'Tommi

--- GoldED+/EMX 1.1.5-b20170303
* Origin: ---------------------------------->> (2:221/360)

On 2018 Jan 08 17:22:44, you wrote to Wilfred van Velzen:

MvdV>>> Anyway, it is no good for those who need disfferent ports for IPv4
MvdV>>> and IPv6.

You can, but you will have to start multiple instances of binkd, with
different configurations.

Is that theory or has anyone actually tried that?

i've told before that we've done it here while migrating one setup from one machine to another... we set up another mailer specifically to catch the new inbound mail... it was processed later after the migration was complete and the
new mail moved over to the new machine... you blew it off as a wild story that no one would ever do...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Life may not be exactly pleasant, but it is at least not dull.
---
* Origin: (1:3634/12.73)

Hello Tommi,

On Monday January 08 2018 20:03, you wrote to Wilfred van Velzen:

You can, but you will have to start multiple instances of
binkd, with different configurations.

MvdV>>> Is that theory or has anyone actually tried that?

For me it is theory. But aren't there a number of nodes who do
this?

Yes, there are. :)

You run multiple instances of binkd on the same machine to have different listen ports for IPv4 and IPv6?

You can even run the same main config and just 'include' the task
specific parts. Only 'iport' for example.

I vagueley remember crashing binkd when attempting to run two instances of binkd with a shared configuration. I do not recall the details, it was years ago...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hello mark,

On Monday January 08 2018 13:18, you wrote to me:

You can, but you will have to start multiple instances of binkd,
with different configurations.

Is that theory or has anyone actually tried that?

i've told before that we've done it here while migrating one setup
from one machine to another...

We are not talking migrating to other hardware, we were talking listening on different ports for IPv4 and IPv6. (Which is exotic in itself..)

we set up another mailer specifically to catch the new inbound mail...
it was processed later after the migration was complete and the new
mail moved over to the new machine... you blew it off as a wild story
that no one would ever do...

I rejected it as a likely explanation for the problem at hand. And indeed I do not know anyone - having native IPv6 - who, as a first encounter with IPv6 that
would setup a complete seperate system for IPv6, instead of just enabeling IPv6
on the existing system.
An exotic situation only to be explored after all other possibilities had been explored and eliminated as the cause of the problem.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hallo Michiel!

08.01.2018 17:22, Michiel van der Vlist schrieb an Wilfred van Velzen:

MvdV>>> Anyway, it is no good for those who need disfferent ports for
MvdV>>> IPv4 and IPv6.

You can, but you will have to start multiple instances of binkd,
with different configurations.

It works.
You can start multiple binkd Daemons with completly different configurations. Tested on os/2 and also on bsd.
Of course you have to use different ports on the same network-adapter.

If you use different network-adapters, it's also possible to use the same port. Depending on differnt network-adapters, you have different local ip-addresses. ;-)

Is that theory or has anyone actually tried that?

I've tried that and it's working here.

Cheers, Michiel

Bye/2 Torsten

... MAILBOX: up 14d 0h 24m load: 29 proc, 116 threads (tbupv1.0)
--- GoldED+ 1.1.5
* Origin: DatenBahn BBS Hamburg (2:240/5832)

On 2018 Jan 09 16:15:32, you wrote to me:

You can, but you will have to start multiple instances of binkd,
with different configurations.

Is that theory or has anyone actually tried that?

i've told before that we've done it here while migrating one setup
from one machine to another...

We are not talking migrating to other hardware, we were talking
listening on different ports for IPv4 and IPv6. (Which is exotic in itself..)

we couldn't have done the migration without doing the multiple ports and multiple configs on the same machine thing... your blinders lead you to miss other things in the same visual range... these two aspects being two of them...
we've done it more than once on OS/2 and on linux... no IPv6 muck needed or used... sorry... multiple ports and multiple configs on the same machine just work when configured properly...

we set up another mailer specifically to catch the new inbound
mail... it was processed later after the migration was complete and
the new mail moved over to the new machine... you blew it off as a
wild story that no one would ever do...

I rejected it as a likely explanation for the problem at hand. And
indeed I do not know anyone - having native IPv6 - who, as a first encounter with IPv6 that would setup a complete seperate system for
IPv6, instead of just enabeling IPv6 on the existing system. An exotic situation only to be explored after all other possibilities had been explored and eliminated as the cause of the problem.

and again, you've gone off in left field with what i posted :sigh:

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... A duck is a bird that walks like it has ridden horseback all day.
---
* Origin: (1:3634/12.73)

Hello Torsten,

On Tuesday January 09 2018 18:54, you wrote to me:

Of course you have to use different ports on the same network-adapter.

Ah, that's IPv4 think. ;-)

In the beginning every machine on the internet had its own global address. To conserve address space, institutions started to share public addresses among devices using NAPT. That practise is now standard in home networks. With the coming of IPv6, there is no longer a scarcity in addresses and every interface has, or at least can have, a public globally routable address again. Even multiple adresses if needed.

NA(P)T is IPv4 think. With the coming of IPv6 we need to be "deprogrammed". We must get rid of the IPv4 think and start thinking like the Internet pioeers did.

I now have two incarnations of binkd running on the same machine, on the same interface, each listening to ot own IPv6 address.

When you have IPv6, you can call 2:280/5556 at f5556.vlist.eu.

If you use different network-adapters, it's also possible to use the
same port. Depending on differnt network-adapters, you have different local ip-addresses. ;-)

Not much good with only one WAN IPv4 address...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Michiel van der Vlist wrote to Torsten Bamberg <=-

I now have two incarnations of binkd running on the same machine, on
the same interface, each listening to ot own IPv6 address.

I have one copy of binkd and Mystic listening on port 24554 on the same machine on both IPv4 and IPv6. I have both multiple public IPv4 and IPv6 addresses available.


... BULLFIGHTER: 1 little man against a 1/2 ton of pissed off pot roast.
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

09 Jan 18 16:34:24, you wrote to me:

You can, but you will have to start multiple instances of
binkd, with different configurations.

MvdV>>>> Is that theory or has anyone actually tried that?

For me it is theory. But aren't there a number of nodes who do
this?

Yes, there are. :)

You run multiple instances of binkd on the same machine to have different listen ports for IPv4 and IPv6?

Sure. I run a server and a client in separate session with slightly different configs. Separate logs, for example.

You can run any port / ipv4 / ipv6 addr combination. Or the same config in multiple computers started from a lan drive.

You can even run the same main config and just 'include' the task
specific parts. Only 'iport' for example.

I vagueley remember crashing binkd when attempting to run two instances of binkd with a shared configuration. I do not recall the details, it was years ago...

I remebmer this. It was only your system which crashed. ;-)

'Tommi

---
* Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)

10 Jan 18 14:22:58, you wrote to Torsten Bamberg:

Of course you have to use different ports on the same network-adapter.

Ah, that's IPv4 think. ;-)

Not really. You can define multiple ipv4 addresses for one network adapter. Just like ipv6.

If you use different network-adapters, it's also possible to use the
same port. Depending on differnt network-adapters, you have different
local ip-addresses. ;-)

Not much good with only one WAN IPv4 address...

Bad for you. I have six of them... :D

'Tommi

---
* Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)

Hello Tommi,

On Thursday January 11 2018 10:46, you wrote to me:

Of course you have to use different ports on the same
network-adapter.

Ah, that's IPv4 think. ;-)

Not really. You can define multiple ipv4 addresses for one network adapter. Just like ipv6.

I know that it is possible, but unfortunately the "normal" situation these days
is that IPv4 adresses are shared among all devices on the LAN by means of NAT. So one has to resort to using different port numbers to keep things apart.

With IPv6 the "kludge" of different port numbers is no longer needed, The unique IPv6 address will do. Hence me calling the use of different port numbers
"IPv4 think".

If you use different network-adapters, it's also possible to use
the same port. Depending on differnt network-adapters, you have
different local ip-addresses. ;-)

Not much good with only one WAN IPv4 address...

Bad for you. I have six of them... :D

You'r the lucky exception. Most of us have only one. And some of us may have none in the near future.

I am looking forward to the day that I can switch off IPv4 and get rid of all the kludges and work arounds that came with it.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hello mark,

On Tuesday January 09 2018 15:10, you wrote to me:

we couldn't have done the migration without doing the multiple ports
and multiple configs on the same machine thing... your blinders lead

"we"? As in "we the King"? *I* (all by myself) have done migrations many time without having to resort to such work arounds. Just move the stuff to the new place, add the new stuff, delete what is no longer needed and throw the switch.

no IPv6 muck needed or used...

"IPv6 muck"? If that is how you look at the main subject of discussion in the IPV6 area, what were you doing there in the first place?

sorry... multiple ports and multiple configs on the same machine just
work when configured properly...

I never said it could not work. I said it was an exotic scenario for the situation at hand (adding IPv6 to an existing binkp system) and I politely explained why I thought so. I also told you that your postulated exotic configuration did not match the observed behaviour of the system in question.

I see that was a waste of time. I also note that your intervention was of no help in solving the problem. On the contrary. You obviously had no idea what you were talking about and just produced noise. I didn't want to be that blunt at the time, but now that you won't drop the matter, I can not stop myself and prefer clearity over diplomacy.

I am wasting my time. So next time you postulate another outlandish scenario, I
will not waste any more time and energy to explain to you why it does not match
the situation at hand. I will just reject it and ignore any further comments from you.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hello Michiel!

14 Jan 18 14:22, Michiel van der Vlist wrote to mark lewis:

we couldn't have done the migration without doing the multiple ports
and multiple configs on the same machine thing... your blinders lead

MvdV> "we"? As in "we the King"?

No, as in "we couldn't have done". Why not calm down and regard this as a "pluralis modestiae" instead of a "pluralis majestatis"?


Regards,
Gerrit

... 8:57PM up 7 days, 23:50, 9 users, load averages: 0.05, 0.09, 0.08

--- Msged/BSD 6.1.2
* Origin: Is serving every man (2:240/12)