Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 9 Aug 2001 19:16:49 -0400
From:      "alexus" <ml@db.nexgen.com>
To:        <freebsd-stable@freebsd.org>
Subject:   binding second ip and that second ip rolls over to first.. why? how to fix it?
Message-ID:  <001201c12129$5e0b2910$0d00a8c0@alexus>

next in thread | raw e-mail | index | archive | help
Hello

let me cut to the chase and get on the subject...

I'm running FreeBSD 4.3-STABLE (used to 4.3-RELEASE)

I already had ip 66.92.98.145

su-2.05# host 66.92.98.145
145.98.92.66.IN-ADDR.ARPA domain name pointer oXyeTb.com
su-2.05#

and I wanted to bind ip 66.92.98.151

su-2.05# host 66.92.98.151
151.98.92.66.IN-ADDR.ARPA domain name pointer MbI.PyCCKuE.com
su-2.05#

I bind another ip (2nd) to my existing interface as an alias using command

ifconfig fxp0 alias 66.92.98.151 netmask 255.255.255.255

su-2.05# uname -a
FreeBSD box.nexgen.com 4.3-STABLE FreeBSD 4.3-STABLE #9: Thu Aug  2 17:14:23
EDT 2001     alexus@box.nexgen.com:/usr/src/sys/compile/box  i386
su-2.05# ifconfig
fxp0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        inet 66.92.98.145 netmask 0xffffff00 broadcast 66.92.98.255
        inet 66.92.98.151 netmask 0xffffffff broadcast 66.92.98.151
        ether 00:60:94:a5:cb:44
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.0.9 netmask 0xffffff00 broadcast 192.168.0.255
        ether 00:a0:cc:21:04:42
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000
su-2.05#

as you can see I have 2 interfaces fxp0 used for external (internet) ips and
dc0 for internal (intranet) network

let me show you my routing table without dc0 interface

su-2.05# netstat -rn | grep -v dc0
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            66.92.98.1         UGSc       28   517876   fxp0
66.92.98/24        link#1             UC          6        0   fxp0 =>
66.92.98.1         0:10:67:0:8d:68    UHLW       27        4   fxp0    608
66.92.98.145       0:60:94:a5:cb:44   UHLW        3     5375    lo0
66.92.98.146       0:30:48:21:78:8f   UHLW        0       26   fxp0    918
66.92.98.148       0:30:48:21:78:a6   UHLW        0       30   fxp0    790
66.92.98.149       0:30:48:21:3c:c9   UHLW        0      288   fxp0    649
66.92.98.150       0:30:48:21:3c:c9   UHLW        0     1468   fxp0    191
66.92.98.151       0:60:94:a5:cb:44   UHLW        0      250    lo0 =>
66.92.98.151/32    link#1             UC          1        0   fxp0 =>
127.0.0.1          127.0.0.1          UH          2     9383    lo0
su-2.05#

and for those who intersted to see whole thing here it is..

su-2.05# netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            66.92.98.1         UGSc       28   517878   fxp0
66.92.98/24        link#1             UC          6        0   fxp0 =>
66.92.98.1         0:10:67:0:8d:68    UHLW       27        4   fxp0    606
66.92.98.145       0:60:94:a5:cb:44   UHLW        3     5384    lo0
66.92.98.146       0:30:48:21:78:8f   UHLW        0       26   fxp0    916
66.92.98.148       0:30:48:21:78:a6   UHLW        0       30   fxp0    788
66.92.98.149       0:30:48:21:3c:c9   UHLW        0      288   fxp0    647
66.92.98.150       0:30:48:21:3c:c9   UHLW        0     1468   fxp0    189
66.92.98.151       0:60:94:a5:cb:44   UHLW        0      250    lo0 =>
66.92.98.151/32    link#1             UC          1        0   fxp0 =>
127.0.0.1          127.0.0.1          UH          2     9383    lo0
192.168            link#2             UC          7        0    dc0 =>
192.168.0.6        0:d0:b7:9e:f:d3    UHLW        0     6477    dc0   1043
192.168.0.8        0:d0:b7:9e:12:8a   UHLW        0      357    dc0   1027
192.168.0.13       0:2:b3:40:99:2a    UHLW        3   391423    dc0   1121
192.168.0.22       0:d0:b7:9e:15:13   UHLW        1     3601    dc0   1173
192.168.0.23       0:d0:b7:9e:12:54   UHLW        1     4215    dc0   1041
192.168.0.26       0:2:b3:40:96:a7    UHLW        0     6338    dc0    446
192.168.0.31       0:2:b3:40:9a:df    UHLW        0   155811    dc0   1198
su-2.05#

... now the problem that i'm having for some reason whenever i'm trying to
IRC w/ my 2nd ip and for some reason it rolls over to first ip

i've tryed following clients

su-2.05# BitchX -v
BitchX - Based on EPIC Software Labs epic ircII (1998).
Version (BitchX-1.0c18) -- Date (20010108).
Process [9357]
BitchX version BitchX-1.0c18 (20010108)
su-2.05#

BitchX with -H

ircII with -h

su-2.05# irc --version
ircII version 4.4Z (20000831)
su-2.05#

and eggdrop 1.6.6

su-2.05# grep "set my" /home/alexus/eggdrop/bot.conf
set my-hostname "MbI.PyCCKuE.com"
set my-ip "66.92.98.151"
su-2.05#

I also copy my binary to another box to see maybe something wrong with
client(s) .. nope they all workin fine
I was able to irc using 2nd ip on another box using same software

...

to make sure that ip is working itself

i'm able to telnet/ssh/www/ftp to that 2nd ip so it works.. although i'm not
quite sure if its rolls over to first ip or not..
i'd assume it is.. but i dont know for sure


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001201c12129$5e0b2910$0d00a8c0>