Wow! That made a difference. One
echo "0" > /proc/sys/net/ipv4/conf/eth1/rp_filter
and everything started working.
Thanks a lot Torsten and Alex - I wouldn't have solved it without your
suggestions.
Paul Viney
On Wednesday 14 February 2007 21:17, Torsten Luettgert wrote:
&
If I type
route add default gw 192.168.1.1
ip route flush cache
then my forwarding suddenly starts working again, although the rest of my
routing obviously doesn't do what I want any more.
Weird.
Paul Viney
___
LARTC mailing list
me the impression that routing has
failed.
I also tried ip r get from 192.168.12.5, which did
indeed give me the same "RTNETLINK answers: Invalid argument" error. I guess
that means that my understanding of the purpose of 'ip r get' is indeed
faulty.
Thanks fo
route get to 192.168.12.5 iif eth1 gives
RTNETLINK answers: Invalid argument
Am I not understanding how "ip route get" works? The man pages are fairly
succinct in their explanation.
Thanks for your help,
Paul Viney
On Tuesday 13 February 2007 21:40, Alex Samad wrote:
> On Tue, Fe
ush cache
I'm using linux 2.6.19.2 + grsecurity patches, every option I could find
compiled in, on an up to date gentoo system.
Can anyone see what I'm missing?
Thanks,
Paul Viney
ip route show
192.168.2.0/24 dev eth5 proto kernel scope link src 192.168.2.2
192.168.1.0/24 dev eth1
