Re: Traceroute issues

2003-03-12 Thread David
On Wed, 12 Mar 2003, Nathan Kinkade wrote: > > At 09:13 PM 3/11/03 -0800, Daxbert wrote: > > >Quoting Dragoncrest <[EMAIL PROTECTED]>: > > > > > >> Hi all. Got a really weird issue here. Got a router that > > >> uses simple nat that for some reason won't allow me to traceroute > > >> out o

Re: Traceroute issues

2003-03-12 Thread Dragoncrest
Is this a router or true stateful firewall? Take a look at the logs to see if you see unusual high port udp packets being dropped. Kingston Router. And regrettably I have no logs on it right now. So I have none to look at. What OS are the other hosts that are able to traceroute? So far any v

Re: Traceroute issues

2003-03-12 Thread Dragoncrest
At 11:04 AM 3/12/03 -0500, Edmond Baroud wrote: did u compile a custom kernel? Nope. Standard generic kernel. try: uname -a FreeBSD dragoncrest.jasnetworks.net 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Tue Jun 11 06:14:12 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 ipfs

Re: Traceroute issues

2003-03-12 Thread Daxbert
Quoting Dragoncrest <[EMAIL PROTECTED]>: > > > Hi all. Got a really weird issue here. Got a router that uses > > > simple nat > > > that for some reason won't allow me to traceroute out of my freebsd box, > > > but every other computer connected to the router can, and can traceroute > > > with

Re: Traceroute issues

2003-03-12 Thread Nathan Kinkade
On Wed, Mar 12, 2003 at 10:11:23AM -0500, Dragoncrest wrote: > At 09:13 PM 3/11/03 -0800, Daxbert wrote: > >Quoting Dragoncrest <[EMAIL PROTECTED]>: > > > >> Hi all. Got a really weird issue here. Got a router that uses > >simple nat > >> that for some reason won't allow me to traceroute o

Re: Traceroute issues

2003-03-12 Thread Edmond Baroud
did u compile a custom kernel? try: uname -a ipfstat ipf -Fa netstat -rn what about ping ? Ed Quoting Dragoncrest ([EMAIL PROTECTED]): > Already tried that. I think it may be the version of Traceroute > I'm using. When I enter that command, all I get is this. > > traceroute [-Sdnrv]

RE: Traceroute issues

2003-03-12 Thread Dragoncrest
ifconfig -a dc0: flags=8843 mtu 1500 inet6 fe80::a00:8ff:fe00:800%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.25 netmask 0xff00 broadcast 192.168.0.255 ether 08:00:08:00:08:00 media: Ethernet autoselect (100baseTX) status: active lp0: flags=8810 mtu 1500

Re: Traceroute issues

2003-03-12 Thread Dragoncrest
Already tried that. I think it may be the version of Traceroute I'm using. When I enter that command, all I get is this. traceroute [-Sdnrv] [-w wait] [-m max_ttl] [-M min_ttl] [-P proto] [-p port#] [-q nqueries] [-t tos] [-s src_addr] [-g gateway] host [data_size]

RE: Traceroute issues

2003-03-11 Thread Michael K. Smith
> > Hi all. Got a really weird issue here. Got a router > that uses simple nat > that for some reason won't allow me to traceroute out of my > freebsd box, > but every other computer connected to the router can, and can > traceroute > with flying colors. What might possibly be wrong

Re: Traceroute issues

2003-03-11 Thread Daxbert
Quoting Dragoncrest <[EMAIL PROTECTED]>: > Hi all. Got a really weird issue here. Got a router that uses simple nat > that for some reason won't allow me to traceroute out of my freebsd box, > but every other computer connected to the router can, and can traceroute > with flying colors.