[Bug 236014] w -nn doesn't resolve hostname to ipv6 numeric if host has v4 and v6 entry.

2019-03-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236014 --- Comment #3 from nis...@snickers.org --- No - It had a single A and a single associated to it. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@fr

[Bug 236014] w -nn doesn't resolve hostname to ipv6 numeric if host has v4 and v6 entry.

2019-03-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236014 Hiroki Sato changed: What|Removed |Added CC||h...@freebsd.org --- Comment #2 from

[Bug 236014] w -nn doesn't resolve hostname to ipv6 numeric if host has v4 and v6 entry.

2019-03-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236014 Pedro F. Giffuni changed: What|Removed |Added CC||p...@freebsd.org Assi

Re: TCP-forwarding with netcat - weird failures ...

2019-03-04 Thread Patrick M. Hausen
Hi Eugene, > Am 04.03.2019 um 12:21 schrieb Eugene Grosbein : > > 04.03.2019 17:43, Patrick M. Hausen wrote: > >> Needless to say: doesn’t work. And no, it’s not the obvious ARP caches. >> Connections can be established but then abort spontaneously without >> an observable pattern or reason. >

Re: TCP-forwarding with netcat - weird failures ...

2019-03-04 Thread Eugene Grosbein
04.03.2019 17:43, Patrick M. Hausen wrote: > Needless to say: doesn’t work. And no, it’s not the obvious ARP caches. > Connections can be established but then abort spontaneously without > an observable pattern or reason. Each "abort" of TCP connection has its own distinct reason: TCP FIN or TCP

TCP-forwarding with netcat - weird failures ...

2019-03-04 Thread Patrick M. Hausen
Hi all, in a particular customer network we have a world wide VPN with partially overlapping addresses, renumbering impossible due to political reasons, and all the fun you can have in the „enterprise“ environment. No IPv6 either, newfangled nonsense … :-/ So to access a certain set of services w