On Thu, 2007-02-15 at 00:30 +0100, Paul Viney wrote:
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.
But the question I have had about this
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:
This is one of my
On Tue, 2007-02-13 at 22:54 +0100, Paul Viney wrote:
I still seem to have much the same problem. I no longer get ICMP unreachable
errors, but the packet just seems to disappear - I can't see it being
forwarded on any interface, nor can I find any kind of reply - icmp or
otherwise.
This is
On Wed, Feb 14, 2007 at 08:30:48AM +0100, Paul Viney wrote:
I still seem to have much the same problem. I no longer get ICMP
unreachable errors, but the packet just seems to disappear - I can't see
it being forwarded on any interface, nor can I find any kind of reply -
icmp or
On Tue, Feb 13, 2007 at 02:50:13PM +0100, Paul Viney wrote:
Hi all,
I'm trying to set up a computer with 2 routes to the internet, much as
described at http://lartc.org/howto/lartc.rpdb.multiple-links.html .One of my
interfaces (eth5, 192.168.2.2) is only used for traffic originating
Thanks for the advice, Alex. I've been able to add both default routes - I
hadn't considered using the metric to avoid using the VPN link.
I guess I wasn't very clear with my use of 64.233.183.103, which was meant to
be a random internet address coming in over the VPN link, not the default
On Tue, Feb 13, 2007 at 10:54:51PM +0100, Paul Viney wrote:
Thanks for the advice, Alex. I've been able to add both default routes - I
hadn't considered using the metric to avoid using the VPN link.
I guess I wasn't very clear with my use of 64.233.183.103, which was meant to
be a random
I still seem to have much the same problem. I no longer get ICMP
unreachable errors, but the packet just seems to disappear - I can't see
it being forwarded on any interface, nor can I find any kind of reply -
icmp or otherwise.
sounds like a firewall issue!
It does sound like a
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
