postfix z ra-updates
Tomek Orzechowski
orzech w pld.org.pl
Pon, 7 Kwi 2003, 00:11:11 CEST
[06 kwiecień, 2003] Jan Rekorajski napisał:
>[baggins w duch ssh]$ ip a
>1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet6 ::1/128 scope host
>2: sit0 w NONE: <NOARP> mtu 1480 qdisc noop
> link/sit 0.0.0.0 brd 0.0.0.0
>3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc sfq qlen 100
> link/ether 00:10:5a:c7:45:9a brd ff:ff:ff:ff:ff:ff
> inet 193.0.96.2/24 brd 193.0.96.255 scope global eth0
> inet 193.0.96.1/24 brd 193.0.96.255 scope global secondary eth0
> inet 193.0.96.14/24 brd 193.0.96.255 scope global secondary eth0
> inet6 fe80::210:5aff:fec7:459a/64 scope link
>4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> link/ether 00:10:5a:c7:45:9e brd ff:ff:ff:ff:ff:ff
> inet 10.1.3.2/24 brd 10.1.3.255 scope global eth1
> inet 10.1.3.1/32 scope global eth1
> inet 10.1.3.12/32 scope global eth1
> inet 10.1.3.4/32 scope global eth1
> inet6 3ffe:8010:70:3::1/128 scope global
> inet6 3ffe:8010:70:3::2/64 scope global
> inet6 fe80::210:5aff:fec7:459e/64 scope link
# ip a
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
2: imq0: <NOARP> mtu 1500 qdisc noop qlen 30
link/void
3: imq1: <NOARP> mtu 1500 qdisc noop qlen 30
link/void
4: sit0 w NONE: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
5: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc htb qlen 100
link/ether 00:a0:24:3a:c5:1a brd ff:ff:ff:ff:ff:ff
inet 217.153.110.66/30 brd 217.153.110.67 scope global eth0
inet6 fe80::2a0:24ff:fe3a:c51a/10 scope link
6: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc htb qlen 100
link/ether 00:30:84:88:b5:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global eth1
inet6 3ffe:8210:f09:2::1/64 scope global
inet6 fe80::230:84ff:fe88:b500/10 scope link
7: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc sfq qlen 100
link/ether 00:20:ed:52:70:78 brd ff:ff:ff:ff:ff:ff
inet 217.153.110.133/29 brd 217.153.110.135 scope global eth2
inet 217.153.110.129/29 brd 217.153.110.135 scope global secondary eth2
inet 217.153.110.130/29 brd 217.153.110.135 scope global secondary eth2
inet6 fe80::220:edff:fe52:7078/10 scope link
8: opacz w eth0: <POINTOPOINT,NOARP,UP> mtu 1480 qdisc noqueue
link/sit 217.153.110.133 peer 62.233.140.218
inet6 fe80::d999:6e85/128 scope link
inet6 3ffe:8210:f09:2::1/127 scope global
Czyli podobnie i problemu nie ma. Czyli błąd wywoływany jest przez specyficzną konfigurację...
>
>> .. i jakby można było zerknąć na wynik "postconf -n".
>
>Wolalbym calego tu nie wsadzac, powiedz co konkretnie?
# postconf -n
alias_database = hash:/etc/mail/aliases
alias_maps = hash:/etc/mail/aliases
biff = no
command_directory = /usr/sbin
config_directory = /etc/mail
daemon_directory = /usr/lib/postfix
debug_peer_level = 2
default_privs = nobody
mail_owner = postfix
mail_spool_directory = /var/mail
myhostname = blue.lj.pl
myorigin = $myhostname
queue_directory = /var/spool/postfix
setgid_group = maildrop
W twoim przypadku szczególnie istotne może być mynetworks, bo właśnie
obsługę mynetworks qboosh ostatnio poprawiał w paczu IPv6.
--
_ _._. _ .|_
(_)| /_(/.(.| )
Tomek Orzechowski
Solitude, mon Dieu, solitude...
Więcej informacji o liście dyskusyjnej pld-devel-pl