JB wrote:
First of all, thanks very much for your advice.
I found in the end - probably due to something you said -
that the problem was entirely due to the fact that
I had omitted the line
#INTERFACE SOURCE ADDRESS PROTO PORT(S)
eth0 eth1
in /etc/shorewall/masq .
Since I put it in, and re-started shorewall, everything is working fine.
Timothy Murphy <gayleard <at> eircom.net> writes:
> ...
> [tim <at> helen ~]$ route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
...
This is your backup server (Fedora 13).
First question I have: where did these come from ?
> 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0
> eth1
Nb My iptables data presumably all comes from shorewall.
I see this address is mentioned in shorewall
(in /usr/share/doc/shorewall*/Samples/two-interfaces/ , which I followed).
Isn't it used in some way if one's internet connection is down?
>From /etc/resolv.conf I see you obtain your data by NetworkManager
for
>both
interfaces eth0 and eth1 (there are no other interfaces, except lo).
Do you know anything about them or their purpose ?
I would like to see lease data obtained by NM for both interfaces.
Give me outputs:
$ ps aux |grep -i net
$ ps aux |grep -i dhc
Actually, I had to stop NM with this OS,
and use the network service instead.
I'm not sure why.
But the network service seems to work fine,
and this is only a backup OS, so NM's failure doesn't really matter.
--
Timothy Murphy
e-mail: gayleard /at/
eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland