Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 07 Feb 2002 07:23:46 -0600
From:      Jordan Breeding <jordan.breeding@attbi.com>
To:        freebsd-current@freebsd.org
Subject:   Problems setting up TCP/IP in 5.0-CURRENT...
Message-ID:  <20020212021243.B89489F3C4@okeeffe.bestweb.net>

Next in thread | Raw E-Mail | Index | Archive | Help
Hello,

   I have been using -current for a few weeks now after converting from 
linux and then finding that a lot of things I wanted to do only work in 
-current and not -stable.  However the only thing which I can not get to 
work exactly as it did in Linux on -current are my TCP/IP settings.  I 
have two ethernet cards, one which I use for outbound (default net) 
traffic and its responses, and one card which I use for inbound port 
forwards from my hardware router as well as inbound/outbound for my 
192.168.1.0 net.  I have been able to get this to work perfectly, but 
only in 4.5-RELEASE (well actually in -stable, ie. 4.4-RELEASE, 
4.5-RC{1,2,3}, and 4.5-RELEASE).  Here is a small session which shows a 
successful setup under -stable:

#ifconfig -a
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
         options=3<rxcsum,txcsum>
         ether 00:01:02:3b:2b:c2
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
xl1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
         options=3<rxcsum,txcsum>
         ether 00:01:02:3b:2b:77
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
         inet6 ::1 prefixlen 128
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
#ifconfig xl0 192.168.1.2 netmask 255.255.255.0
#ifconfig xl1 192.168.1.3 netmask 255.255.255.0
#ifconfig -a
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=3<rxcsum,txcsum>
         inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
         inet6 fe80::201:2ff:fe3b:2bc2%xl0 prefixlen 64 scopeid 0x1
         ether 00:01:02:3b:2b:c2
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
xl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=3<rxcsum,txcsum>
         inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
         inet6 fe80::201:2ff:fe3b:2b77%xl1 prefixlen 64 scopeid 0x2
         ether 00:01:02:3b:2b:77
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
         inet6 ::1 prefixlen 128
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
#route delete -net 192.168.1.0
#route add -net default 192.168.1.1
#route add -net 192.168.1.0 -interface 192.168.1.3
#netstat -r
Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            192.168.1.1        UGSc        0       21    xl0
192.168.1          link#2             UCSc        4        0    xl1

Internet6:
Destination        Gateway            Flags      Netif Expire
localhost          localhost          UH          lo0
fe80::%xl0         link#1             UC          xl0
fe80::201:2ff:fe3b 0:1:2:3b:2b:c2     UHL         lo0
fe80::%xl1         link#2             UC          xl1
fe80::201:2ff:fe3b 0:1:2:3b:2b:77     UHL         lo0
fe80::%lo0         fe80::1%lo0        Uc          lo0
fe80::1%lo0        link#3             UHL         lo0
ff01::             localhost          U           lo0
ff02::%xl0         link#1             UC          xl0
ff02::%xl1         link#2             UC          xl1
ff02::%lo0         localhost          UC          lo0

This shows no problems at all and works whether I use the routing daemon 
or use static routes at boot up, however -current will not allow me to 
do the same thing that I have done above, instead I get the following:

bash-2.05a# ifconfig -a
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=3<rxcsum,txcsum>
         inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
         inet6 fe80::201:2ff:fe3b:2bc2%xl0 prefixlen 64 scopeid 0x1
         ether 00:01:02:3b:2b:c2
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
xl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=3<rxcsum,txcsum>
         inet 192.168.1.3 netmask 0xffffffff broadcast 192.168.1.3
         inet6 fe80::201:2ff:fe3b:2b77%xl1 prefixlen 64 scopeid 0x2
         ether 00:01:02:3b:2b:77
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
         inet6 ::1 prefixlen 128
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
         inet 127.0.0.1 netmask 0xff000000
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
bash-2.05a# ifconfig xl1 192.168.1.3 netmask 255.255.255.0
ifconfig: ioctl (SIOCAIFADDR): File exists

The only thing which I can think of is that either a) it is a userland 
change in -current, or b) I was only ever running the GENERIC kernel for 
4.5-RELEASE and never recompiled my kernel until I was compiling with 
-current source so maybe it is some option in the GENERIC config file 
for the -current source.  If it is b) could someone please tell me which 
option is causing this so that I may turn it back off.  I would really 
like to try and get this working exactly as I have in Linux, Solaris, 
FreeBSD 4.5-RELEASE.  Thanks for any help.

Jordan Breeding


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20020212021243.B89489F3C4>