[ipv6hackers] Scanning for IPv6 addresses embedding TCP/UDP service ports
fabian at wenks.ch
Thu Mar 28 21:02:31 CET 2013
I just quote your e-mail back to the mailing list, as it seems
that it did not got through the mailing list. It is even not in
On 27.03.2013 09:05, Owen DeLong wrote:
> On Mar 27, 2013, at 12:25 AM, Fernando Gont <fernando at gont.com.ar> wrote:
>> On 03/26/2013 09:59 AM, Fabian Wenk wrote:
>>> It would probably be the best, to just firewall the TCP/139 on IPv6.
>>> Even the smb.conf(5) manpage is quite low on information regarding IPv6,
>>> I see only this two parts, all other examples an options just mention
>>> IPv4 addresses:
>>> the IP address of the client machine.
>>> Before 3.6.0 it could contain IPv4 mapped IPv6 addresses,
>>> now it only contains IPv4 or IPv6 addresses.
>> I cannot parse this excerpt. This means that before 3.6.0 it could only
>> contain v6 addresses?
> No, it means that before 3.6.0, it could contain addresses
> like ::ffff:188.8.131.52.
> After 3.6.0, it can contain only addresses of the form 184.108.40.206 or
> actual IPv6 addresses. It cannot contain a representation of
> an IPv4 address in the form ::ffff:220.127.116.11.
PS: No need to use "reply all", reply only to the list is
perfect, as I do filter e-mails based on the "List-Id" header line.
More information about the Ipv6hackers