Re: Bogus bind() warnings

Tom Lane writes:

> Is it possible that that kernel considers binding to an IPv6 port to
> conflict with binding to the "same" port number as an IPv4 port?

I don't understand this business, but if it helps, below is my ifconfig
output.

eth0 Link encap:Ethernet HWaddr 00:40:F6:74:BE:71
inet6 addr: fe80::240:f6ff:fe74:be71/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:440903 errors:0 dropped:0 overruns:0 frame:0
TX packets:301944 errors:5 dropped:0 overruns:0 carrier:3
collisions:0 txqueuelen:100
RX bytes:189774879 (180.9 Mb) TX bytes:64786361 (61.7 Mb)
Interrupt:11 Base address:0xd800

eth1 Link encap:Ethernet HWaddr 00:50:22:80:A9:6E
inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0
inet6 addr: fe80::250:22ff:fe80:a96e/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:99975 errors:0 dropped:0 overruns:0 frame:0
TX packets:126153 errors:0 dropped:0 overruns:0 carrier:0
collisions:8425 txqueuelen:100
RX bytes:15633278 (14.9 Mb) TX bytes:52753463 (50.3 Mb)
Interrupt:9 Base address:0x9000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:107127 errors:0 dropped:0 overruns:0 frame:0
TX packets:107127 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20827790 (19.8 Mb) TX bytes:20827790 (19.8 Mb)

ppp0 Link encap:Point-to-Point Protocol
inet addr:82.82.161.250 P-t-P:145.253.4.3 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:37103 errors:0 dropped:0 overruns:0 frame:0
TX packets:23882 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:4652420 (4.4 Mb) TX bytes:5807647 (5.5 Mb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

--
Peter Eisentraut peter_e(at)gmx(dot)net