Thanks to everyone for your help/suggestions. I think that I'm headed in the
right direction.
I still can't seem to force a ping through a particular interface, even when I
have both interfaces as default routes (I've tried both with and without mpath).
If it matters, in both cases I used a
On 02-10-2014 10:11, Jeff wrote:
I still can't seem to force a ping through a particular interface, even when
I
have both interfaces as default routes (I've tried both with and without
mpath).
If it matters, in both cases I used a lower priority (higher #) for our low
speed
metered connection.
Hello Jeff,
Wednesday, October 1, 2014, 12:14:53 PM, you wrote:
J It sounds like ping -I is what I was looking for, but when I use it, it
seems
J to be sending out the packet with the right source address, but sending it to
J the wrong interface.are there any tricks here?
J Here's some
grazzol...@gmail.com (Giancarlo Razzolini), 2014.10.02 (Thu) 15:39 (CEST):
On 02-10-2014 10:11, Jeff wrote:
I still can't seem to force a ping through a particular interface, even when
I
have both interfaces as default routes (I've tried both with and without
mpath).
If it matters, in
On 2014-10-02, Jeff j...@usedmoviefinder.com wrote:
Thanks to everyone for your help/suggestions. I think that I'm headed in the
right direction.
I still can't seem to force a ping through a particular interface, even when I
have both interfaces as default routes (I've tried both with and
On 2014/10/02 17:21, aluc...@phangos.fr wrote:
Or you can use a static route to force reaching the ip from an interface.
Would be more secure than bringing down a working interface just to check if
another one is working ...
I didn't suggest that ;)
This would only be needed to spot the main
Hi Everyone,
With the addition of a carefully constructed route-to rule I now have all of the
individual pieces working. Now, with some careful plumbing and testing I should
be all set. The final solution will be a combination of ifstated, multipath
routing
(prioritized) and ping -I; thanks to
On 02-10-2014 16:12, Jeff wrote:
With the addition of a carefully constructed route-to rule I now have all of
the
individual pieces working. Now, with some careful plumbing and testing I
should
be all set. The final solution will be a combination of ifstated, multipath
routing
(prioritized)
Or you can use a static route to force reaching the ip from an
interface.
Would be more secure than bringing down a working interface just to
check if another one is working ...
Cheers,
Louis
On 2014-10-02 17:09, Stuart Henderson wrote:
On 2014-10-02, Jeff j...@usedmoviefinder.com wrote:
I have a very unreliable ISP (approximately 97% uptime). Many of the times
that they go
down, I'm connected and can ping within their limited network, but can't get to
the
outside world. In these cases, I have an alternate slow speed connection
that I use.
Right now, I manually change the
ifstated could do it ...
On Wed, Oct 01, 2014 at 11:10:12AM -0400, Jeff wrote:
I have a very unreliable ISP (approximately 97% uptime). Many of the times
that they go
down, I'm connected and can ping within their limited network, but can't get
to the
outside world. In these cases, I have an alternate slow speed
On 2014-10-01 16:10, Jeff wrote:
I have a very unreliable ISP (approximately 97% uptime). Many of the
times that they go
down, I'm connected and can ping within their limited network, but
can't get to the
outside world. In these cases, I have an alternate slow speed
connection that I use.
10 - 4 fpx1
--
View this message in context:
http://openbsd.7691.n7.nabble.com/Change-routing-tables-when-ISP-goes-down-tp256610p256624.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.
On Wed, Oct 1, 2014 at 8:10 AM, Jeff j...@usedmoviefinder.com wrote:
I have a very unreliable ISP (approximately 97% uptime). Many of the times
that they go
down, I'm connected and can ping within their limited network, but can't get
to the
outside world. In these cases, I have an
It sounds like ping -I is what I was looking for, but when I use it, it seems
to be sending out the packet with the right source address, but sending it to
the wrong interface.are there any tricks here?
Here's some data (edited) to show what I'm seeing:
fxp0: inet 10.16.100.1 netmask
On Wed, Oct 1, 2014 at 2:10 PM, Gerald Chudyk gchu...@gmail.com wrote:
I have been casually working on this for some time now.
Hey, nice work!
--
Don't eat anything you've ever seen advertised on TV
- Michael Pollan, author of In Defense of Food
On 01-10-2014 14:14, Jeff wrote:
It sounds like ping -I is what I was looking for, but when I use it, it
seems
to be sending out the packet with the right source address, but sending it
to
the wrong interface.are there any tricks here?
You must enforce through pf route-to the packets to go
18 matches
Mail list logo
