Re: Traceroute issues
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] Any futher suggestions? :) 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 of my freebsd box, but every other computer connected to the router can, and can traceroute with flying colors. What might possibly be wrong with my machine that I can't traceroute anywhere? Could if be that the other hosts are using ICMP instead of UDP for traceroute? From your FreeBSD host, try... # traceroute -I hostname To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Traceroute issues
ifconfig -a dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST 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=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 faith0: flags=8002BROADCAST,MULTICAST mtu 1500 netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1UGSc6 654dc0 127.0.0.1 127.0.0.1 UH 275172lo0 192.168.0 link#1 UC 20dc0 192.168.0.100:c0:f0:5d:95:94 UHLW8 317dc0 1127 192.168.0.200:01:03:de:8c:40 UHLW1 430dc0954 192.168.0.25 127.0.0.1 UGHS00lo0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%dc0/64 link#1UC dc0 fe80::a00:8ff:fe00:800%dc008:00:08:00:08:00 UHL lo0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 fe80::1%lo0 link#3UHL lo0 ff01::/32 ::1 U lo0 ff02::%dc0/32 link#1UC dc0 ff02::%lo0/32 ::1 UC lo0 There ya go. At 09:13 PM 3/11/03 -0800, Michael K. Smith wrote: 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 with my machine that I can't traceroute anywhere? Hello: Could you send the output from a 'ifconfig -a' and a 'netstat -rn'? Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Traceroute issues
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] [-w wait] [-m max_ttl] [-M min_ttl] [-P proto] [-p port#] [-q nqueries] [-t tos] [-s src_addr] [-g gateway] host [data_size] Any futher suggestions? :) 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 of my freebsd box, but every other computer connected to the router can, and can traceroute with flying colors. What might possibly be wrong with my machine that I can't traceroute anywhere? Could if be that the other hosts are using ICMP instead of UDP for traceroute? From your FreeBSD host, try... # traceroute -I hostname To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Edmond Baroud UNIX Systems Admin mailto:[EMAIL PROTECTED] Fingerprint 140F 5FD5 3FDD 45D9 226D 9602 8C3D EAFB 4E19 BEF9 UNIX is very user friendly, it's just picky about who its friends are. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Traceroute issues
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 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 with my machine that I can't traceroute anywhere? Could if be that the other hosts are using ICMP instead of UDP for traceroute? From your FreeBSD host, try... # traceroute -I hostname 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] Any futher suggestions? :) This may not be the issue in the first place, but if you want to try an ICMP traceroute do: `traceroute -P icmp host`. I'm not sure what the -I option is and it's not documented in my version of the manpage (4.8-RC). Nathan -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc pgp0.pgp Description: PGP signature
Re: Traceroute issues
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. What might possibly be wrong with my machine that I can't traceroute anywhere? Could if be that the other hosts are using ICMP instead of UDP for traceroute? # traceroute -I hostname 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] Any futher suggestions? :) 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. What OS are the other hosts that are able to traceroute? Finally, download and install latest traceroute (ports?) --dax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Traceroute issues
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 ipfstat open: Device not configured ipf -Fa open device: Device not configured ioctl(SIOCIPFFL): Bad file descriptor netstat -rn See other reply for that. what about ping ? Ping works beautifully. Any other info you need? :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Traceroute issues
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 version of windows seems to be unaffected. I don't have any other linux or mac systems to test this with at this time or I'd see if those were affected too. Finally, download and install latest traceroute (ports?) Trying that right now as I speak. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Traceroute issues
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 of my freebsd box, but every other computer connected to the router can, and can traceroute with flying colors. What might possibly be wrong with my machine that I can't traceroute anywhere? Could if be that the other hosts are using ICMP instead of UDP for traceroute? This may not be the issue in the first place, but if you want to try an ICMP traceroute do: `traceroute -P icmp host`. I had/have the same issue with my D-link router. Originally I was using bridging on my Freebsd box so thought it I had set that up wrong, or it simply broke traceroute. However, it also occured without the bridging. Using -P icmp solves the issue completely for me. DG To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Traceroute issues
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 with my machine that I can't traceroute anywhere? I have no IPFW setup on the box at all, nor is it running. This is all that I have running on the box: root 45538 0.0 0.2 424 220 p0 R+ 11:52PM 0:00.00 ps -aux root 1 0.0 0.2 556 212 ?? SLs 1Feb03 0:00.73 /sbin/init -- root 2 0.0 0.0 00 ?? DL1Feb03 0:20.63 (pagedaemon) root 3 0.0 0.0 00 ?? DL1Feb03 0:00.00 (vmdaemon) root 4 0.0 0.0 00 ?? DL1Feb03 0:58.62 (bufdaemon) root 5 0.0 0.0 00 ?? DL1Feb03 41:44.80 (syncer) root 6 0.0 0.0 00 ?? DL1Feb03 1:09.51 (vnlru) root 81 0.0 0.6 952 516 ?? Ss1Feb03 0:34.44 /usr/sbin/syslogd -s root 88 0.0 0.6 1080 536 ?? Is1Feb03 0:00.43 /usr/sbin/inetd -wW root 90 0.0 0.6 1004 504 ?? Ss1Feb03 0:57.63 /usr/sbin/cron root 92 0.0 1.1 2348 1048 ?? Is1Feb03 0:00.59 /usr/sbin/sshd root131 0.0 0.5 956 488 v0 Is+ 1Feb03 0:00.03 /usr/libexec/getty Pc ttyv0 root132 0.0 0.5 956 488 v1 Is+ 1Feb03 0:00.03 /usr/libexec/getty Pc ttyv1 root133 0.0 0.5 956 488 v2 Is+ 1Feb03 0:00.03 /usr/libexec/getty Pc ttyv2 root134 0.0 0.5 956 488 v3 Is+ 1Feb03 0:00.03 /usr/libexec/getty Pc ttyv3 root135 0.0 0.5 956 488 v4 Is+ 1Feb03 0:00.03 /usr/libexec/getty Pc ttyv4 root136 0.0 0.5 956 488 v5 Is+ 1Feb03 0:00.03 /usr/libexec/getty Pc ttyv5 root137 0.0 0.5 956 488 v6 Is+ 1Feb03 0:00.03 /usr/libexec/getty Pc ttyv6 root138 0.0 0.5 956 488 v7 Is+ 1Feb03 0:00.03 /usr/libexec/getty Pc ttyv7 root 28842 0.0 0.6 940 584 ?? Is Wed06PM 0:00.04 /sbin/dhclient dc0 root 30562 0.0 1.2 1740 1128 ?? Ss Wed07PM 1:18.84 sendmail: accepting connections (sendmail) root 0 0.0 0.0 00 ?? DLs 1Feb03 0:00.00 (swapper) Anyone know why this is happening? I've tried with a Kingston router and a Linksys DSL router. This connection is on DSL by the way. :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Traceroute issues
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. What might possibly be wrong with my machine that I can't traceroute anywhere? Could if be that the other hosts are using ICMP instead of UDP for traceroute? From your FreeBSD host, try... # traceroute -I hostname To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Traceroute issues
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 with my machine that I can't traceroute anywhere? Hello: Could you send the output from a 'ifconfig -a' and a 'netstat -rn'? Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
