On or about Wed, Dec 27, 2006 at 22:08 , while attempting a
Zarathustra emulation Stephan Wehner thus spake:
> Ok, this is a little unfortunate: I can't run traceroute from
> the client PC (the service provider doesn't seem to like it).
> (Nor can I use ping)
So login to the FreeBSD machine and
Gavin Atkinson wrote:
Hi all,
Is anybody actively developing this driver?
I don't think so!
Thanks go out to Damien (merci bcp) who kicked it all of but had some
issues with the people if I read correctly.
Although it's never too late to ask whether he has made any other
improvements or is
So login to the FreeBSD machine and trace back to your client IP -
or as close as you can get. That may mean just to the edge of your
current provider but that may give you some idea.
Ok, here is the result.
$ traceroute 64.114.83.92
traceroute to 64.114.83.92 (64.114.83.92), 64 hops max, 40 b
Hello list & Yvan.
This is my second post regarding the one from:
http://osdir.com/ml/freebsd-net@freebsd.org/msg20572.html
Sorry for not replying, but my email provider simply sucks.
Here's more info.
- racoon.conf
path include "/usr/local/etc/racoon";
path pr
On Wed, Dec 27, 2006 at 10:08:25PM -0800, Stephan Wehner wrote:
> Ok, this is a little unfortunate: I can't run traceroute from the client PC
> (the service provider doesn't seem to like it). (Nor can I use ping)
/usr/ports/net/tcptraceroute
You should normally be able to use tcptraceroute to ge
On Wed, Dec 27, 2006 at 10:08:25PM -0800, Stephan Wehner wrote:
> The server FreeBSD kernel doesn't support tcpdump. I should recompile it
> then, but not now.
Ok, that explains the private 192.168 IP address I saw in your earlier
dumps, it was from the client (a detail mentioned but that I overl
Wise men talk because they have something to say, however
on Thu, Dec 28, 2006 at 08:31 , Stephan Wehner just had
to say something so we heard:
> >So login to the FreeBSD machine and trace back to your client IP -
> >or as close as you can get. That may mean just to the edge of your
> >current p
