On Thu, 2003-01-16 at 07:00, Brian Astill wrote:
> Stacey Roberts and Bill Moran wrote stuff:
> Wot I dun:
> root@BAPhD ~ #ifconfig rl1 inet 192.168.1.100 netmask 255.255.255.0
> ifconfig: ioctl (SIOCAIFADDR): File exists
This is a problem. "ifconfig is complaining about duplicate entries for
IP information. Despite the error though, the command would appear to go
> root@BAPhD ~ #ifconfig -a
> rl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet6 fe80::205:1cff:fe01:9622%rl1 prefixlen 64 scopeid 0x2
> ether 00:05:1c:01:96:22
> media: Ethernet autoselect (100baseTX <full-duplex>)
> status: active
> At that point the two amber lights for that system light up on the hub -
No., this is not right here. There is no IP address returned for rl1
> Altered rc.conf as follows
> # -- sysinstall generated deltas -- # Sun Dec 1 22:00:04 2002
> ifconfig_rl0="inet 192.168.1.100 netmask 255.255.255.0"
> # added this line after manual invoking of rl1 using ifconfig
> ifconfig_rl1="inet 192.168.1.100 netmask 255.255.255.0"
Here you go.., You have given the same IP Addr / netmasks information to
both rl0 & rl1 - this is not right.
> I have given both NICs the same address because they are both on the
> same machine - is this right or wrong?
In your earlier message, you mentioned that rl0 is connected to a cable
modem and rl1 is connected to a lan. rl0 should have a different IP
address.., indeed a different network altogether as against rl1.
To make life easier, you should configure rl1 with another completely
different RFC1918 IP address. So if you're using 192.168.x.x for rl0,
use an IP addr from the 172.16.x.x or 10.x.x.x ranges for rl1.
Your set up appears to be that of a gateway. If so, google for "dual
homed hosts" and have a read of what is required to set it all up.
Hope this helps.
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
B.Sc (HONS) Computer Science
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message