Subject: Re: Mysteriously broken tcp: "Can't assign requested address"
To: James Thomas <jim@andalustech.com>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: tech-net
Date: 09/08/2001 18:26:13
On Sat, Sep 08, 2001 at 03:03:21AM +0000, James Thomas wrote:
> I'm attempting to set up a nat box with netbsd 1.5.1.  Before I replace
> the current netgear router, I want to sup the kernel source and install 
> various packages.  Only one nic (sip0) is currently in use, and it's getting 
> its ip via dhcp from the router. 
> 
> This box can ping outside the lan: 
> 
> koukotsu: {3} ping soulcalibur.com
> PING soulcalibur.com (216.22.201.45): 56 data bytes
> 64 bytes from 216.22.201.45: icmp_seq=0 ttl=114 time=42.025 ms
> 64 bytes from 216.22.201.45: icmp_seq=1 ttl=114 time=28.092 ms
> ^C
>  ----soulcalibur.com PING Statistics----
> 2 packets transmitted, 2 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 28.092/35.059/42.025/9.852 ms 
> 
> It can traceroute just as easily:
> koukotsu: {6} traceroute soulcalibur.com
> traceroute: Warning: Multiple interfaces found; using 192.168.0.2 @ sip0
> traceroute to soulcalibur.com (216.22.201.45), 30 hops max, 40 byte packets
> 1  routar (192.168.0.1)  2.006 ms  1.789 ms  1.652 ms
> 2  10.28.192.17 (10.28.192.17)  381.512 ms  244.396 ms  160.051 ms
> 3  ffaxvamf-7507-pos600.cox.rr.com (24.28.223.18)  104.935 ms  83.756 ms  
> 212.531 ms
>  -etc- 
> 
> 
> It can telnet and ssh inside the lan: 
> 
> koukotsu: {7} ssh 192.168.0.101
> drake@192.168.0.101's password:
> Last login: Fri Sep  7 20:32:22 2001 from 24-28-196-224.c
>  -etc- 
> 
> But it can't telnet, ssh, sup, or do anything with TCP outside the lan: 
> 
> koukotsu: {8} telnet non-euclidean.org
> Trying 198.144.201.82...
> telnet: Unable to connect to remote host: Can't assign requested address
> koukotsu: {9} sup /etc/sup.netbsd.org
> SUP 8.26 (4.3 BSD) for file /etc/sup.netbsd.org at Jan 10 16:32:36
> SUP: Can't connect to server for supfilesrv: Can't assign requested address
> SUP: Will retry in 112 seconds
> ^C
> koukotsu: {10} 
> 
> 
> ifconfig -a says this:
> sip0: 
> flags=fbff<UP,BROADCAST,DEBUG,LOOPBACK,POINTOPOINT,NOTRAILERS,RUNNING,NOARP, 
> PROMISC,ALLMULTI,SIMPLEX,LINK0,LINK1,LINK2,MULTICAST> mtu 1500

Known bug with the sip driver: there are way too many flags set here for a
ethernet interface.
This is fixed in the 1.5 branch; I think you can just update the
driver (if_sip*) to get things going.

--
Manuel Bouyer <bouyer@antioche.eu.org>
--