Date: Wed, 5 Apr 2000 16:05:10 -0400 From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: Anders Andersson <anders@sanyusan.se> Cc: questions@FreeBSD.ORG Subject: Re: NAT/Gateway routing problems? Message-ID: <20000405160509.A930@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <20000405083933.A40778@enterprise.sanyusan.se>; from anders@sanyusan.se on Wed, Apr 05, 2000 at 08:39:33AM %2B0200 References: <20000404134336.A35647@enterprise.sanyusan.se> <20000404233725.B40889@cc942873-a.ewndsr1.nj.home.com> <20000405083933.A40778@enterprise.sanyusan.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 05, 2000 at 08:39:33AM +0200, Anders Andersson wrote: > on Tis, Apr 04, 2000 at 11:37:25pm -0400, Crist J. Clark wrote: > > What is the output of, > > > > % netstat -rn > > anders@gw$ netstat -rn > Routing tables > > Internet: > Destination Gateway Flags Netif Expire > default 212.209.55.81 UGSc ep0 > 127.0.0.1 127.0.0.1 UH lo0 > 192.168.4 link#2 UC ep1 => > 192.168.4.18 0:80:5f:d:5a:ba UHLW ep1 1030 > 192.168.4.19 0:8:c7:1b:ff:83 UHLW ep1 1167 > 192.168.4.20 0:60:97:b4:dd:51 UHLW ep1 1127 > 192.168.4.23 0:60:97:b8:b5:31 UHLW ep1 857 > 192.168.4.255 ff:ff:ff:ff:ff:ff UHLWb ep1 > 212.209.55.80/28 link#1 UC ep0 => > 212.209.55.81 link#1 UHLW ep0 => > 212.209.55.83 0:60:97:b4:dd:20 UHLW ep0 771 > 212.209.55.95 ff:ff:ff:ff:ff:ff UHLWb ep0 Everything looks good. No routing problems. > > % netstat -in > > anders@gw$ netstat -in > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll > ep0 1500 <Link#1> 00:20:af:b7:80:72 322968 31 276938 0 0 > ep0 1500 212.209.55.80 212.209.55.82 322968 31 276938 0 0 > ep1 1500 <Link#2> 00:20:af:b7:66:b0 286324 0 308479 0 0 > ep1 1500 192.168.4 192.168.4.17 286324 0 308479 0 0 > lo0 16384 <Link#3> 24 0 24 0 0 > lo0 16384 127 127.0.0.1 24 0 24 0 0 OK, not a lot of collisions... well, none actually (as we might expect on a switch) and low Ierrs and Oerrs. Everything looking good. > > % ifconfig -a > > anders@gw$ ifconfig -a > ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 212.209.55.82 netmask 0xfffffff0 broadcast 212.209.55.95 > ether 00:20:af:b7:80:72 > media: 10baseT/UTP > supported media: 10base2/BNC 10baseT/UTP 10base5/AUI > ep1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 192.168.4.17 netmask 0xffffff00 broadcast 192.168.4.255 > ether 00:20:af:b7:66:b0 > media: 10baseT/UTP > supported media: 10base2/BNC 10baseT/UTP 10base5/AUI > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > inet 127.0.0.1 netmask 0xff000000 I was curious if there might be simplex-duplex issues. Does not look like these cards do full-duplex anyway? > > % uptime > > anders@gw$ uptime > 8:37AM up 4 days, 18:49, 1 user, load averages: 0.05, 0.02, 0.01 Wanted to see the load average. It is low. > > % ps aux > > anders@gw$ ps aux > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > root 1 0.0 1.0 512 136 ?? ILs Fri03PM 0:00.05 /sbin/init -- > root 2 0.0 0.1 0 0 ?? DL Fri03PM 0:03.10 (pagedaemon) > root 3 0.0 0.1 0 0 ?? DL Fri03PM 0:00.00 (vmdaemon) > root 4 0.0 0.1 0 0 ?? DL Fri03PM 0:04.95 (bufdaemon) > root 5 0.0 0.1 0 0 ?? DL Fri03PM 1:30.60 (syncer) > root 29 0.0 0.1 208 0 ?? Is Fri03PM 0:00.00 adjkerntz -i > root 86 0.0 1.5 448 196 ?? Ss Fri01PM 7:31.75 /sbin/natd -f /et > root 103 0.0 2.4 876 320 ?? Ss Fri01PM 0:06.20 syslogd -s -vv > daemon 109 0.0 1.9 844 260 ?? Is Fri01PM 0:08.86 rwhod > root 127 0.0 2.0 920 272 ?? Ss Fri01PM 0:08.90 cron > root 130 0.0 3.5 1740 480 ?? Is Fri01PM 1:39.76 /usr/sbin/sshd > root 7281 0.0 3.7 892 512 v0 Is+ 12:20PM 0:00.05 /usr/libexec/gett > root 8273 0.0 7.6 1764 1048 ?? S 8:33AM 0:00.79 sshd: anders@ttyp > anders 8274 0.0 3.3 656 456 p0 Ss 8:33AM 0:00.21 -sh (sh) > root 0 0.0 0.1 0 0 ?? DLs Fri03PM 0:00.70 (swapper) > anders 8288 0.0 1.6 404 212 p0 R+ 8:38AM 0:00.01 ps aux Wanted to see what might be eating memory and CPU. natd's usage is a bit high, but nothing to be alarmed about. I would have a look at the machines on either end or verify that you get these slow transfers indepenent of the machine at either end (you may have already done so). If it is this NAT box, I really am not sure where to look next for trouble. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000405160509.A930>