Date: 06 Dec 2002 10:55:40 -0500 From: Dhee Reddy <dhee@myrealbox.com> To: "Julian Stacey" <jhs@berklix.com> Cc: current@freebsd.org Subject: Re: 2nd ether device wont config Message-ID: <87n0njta4j.fsf@myrealbox.com> In-Reply-To: <200212060238.gB62c3058291@flip.jhs.private> References: <200212060238.gB62c3058291@flip.jhs.private>
next in thread | previous in thread | raw e-mail | index | archive | help
FWIW.
i have a similar setup except that the fxp is replaced by rl. All i did was
to change ifconfig_ed1 to ifconfig_ed0 in rc.conf.
for some strange reason, when i installed(sysinstall), the ed card was
detected as ed1 and not as ed0 but on subsequent boots (after i changed
rc.conf) its running smooth as before.
truely
dheeraj
"Julian Stacey" <jhs@berklix.com> writes:
> With DP-2 my 2nd ether won't config
> ( but I've got other FreeBSDs right in the past with 2 ether
> cards. the mail gate on another box, relaying this mail has
> DSL+ether & Internal net+ether)
> Any know why some devices get conf'd as inet6 + inet & some just as inet6 ?
> Could that be part of the problem ?
>
> If I boot with /etc/rc.conf
> ifconfig_fxp0="inet 192.168.53.47 netmask 255.255.255.0"
> # ifconfig_ed1="inet 192.168.53.39 netmask 255.255.255.0"
> # network_interfaces="auto" # default
> I see:
> ifconfig -a
> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 192.168.53.47 netmask 0xffffff00 broadcast 192.168.53.255
> inet6 fe80::2a0:c9ff:fe9c:e0a5%fxp0 prefixlen 64 scopeid 0x1
> ether 00:a0:c9:9c:e0:a5
> media: Ethernet autoselect (10baseT/UTP)
> status: active
> lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
> ed1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> ether 00:00:b4:36:a5:04
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
> inet 127.0.0.1 netmask 0xff000000
> ifconfig ed1 inet 192.168.53.39
> ifconfig: ioctl (SIOCAIFADDR): File exists
> ifconfig ed1 192.168.53.39
> ifconfig: ioctl (SIOCAIFADDR): File exists
> ifconfig lp0 10.0.0.1 10.0.0.2
> works ok
>
> If I boot with /etc/rc.conf
> ifconfig_fxp0="inet 192.168.53.47 netmask 255.255.255.0"
> ifconfig_ed1="inet 192.168.53.39 netmask 255.255.255.0"
> I see:
> ifconfig -a
> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 192.168.53.47 netmask 0xffffff00 broadcast 192.168.53.255
> inet6 fe80::2a0:c9ff:fe9c:e0a5%fxp0 prefixlen 64 scopeid 0x1
> ether 00:a0:c9:9c:e0:a5
> media: Ethernet autoselect (10baseT/UTP)
> status: active
> lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
> ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet6 fe80::200:b4ff:fe36:a504%ed1 prefixlen 64 scopeid 0x3
> ether 00:00:b4:36:a5:04
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
> inet 127.0.0.1 netmask 0xff000000
>
> If I boot with /etc/rc.conf
> ifconfig_ed1="inet 192.168.53.47 netmask 255.255.255.0"
> ifconfig_fxp0="inet 192.168.53.39 netmask 255.255.255.0"
> I see:
> ifconfig -a
> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 192.168.53.39 netmask 0xffffff00 broadcast 192.168.53.255
> inet6 fe80::2a0:c9ff:fe9c:e0a5%fxp0 prefixlen 64 scopeid 0x1
> ether 00:a0:c9:9c:e0:a5
> media: Ethernet autoselect (10baseT/UTP)
> status: active
> lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
> ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet6 fe80::200:b4ff:fe36:a504%ed1 prefixlen 64 scopeid 0x3
> ether 00:00:b4:36:a5:04
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
> inet 127.0.0.1 netmask 0xff000000
>
> It could be my BIOS isnt right (as the ed1 is an ISA card),
> dmesg:
> ed1: <PLUG & PLAY ETHERNET CARD> at port 0x240-0x25f iomem 0xc0000-0xc3fff irq 10 on isa0
> ed1: address 00:00:b4:36:a5:04, type NE2000 (16 bit)
> bios:
> irq 10 allocated to ISA bus,
> PNP OS was off. tried on, made no difference.
> But I think even if the BIOS is wrong somewhere,
> there's perhaps more to fix on FreeBSD side ?
>
> Any Ideas ?
>
> PS I'ts not actually using 192.168.53 but 192.168.??,
> but changed for email to protect `the innoocent` :-)
>
> Julian Stacey
> jhs @ berklix.com Computer Systems Engineer, Unix & Net Consultant, Munich.
> Ihr Rauchen => mein allergischer Kopfschmerz ! Schnupftabak probieren.
> Munich BSD Conference: http://berklix.org/conf/
> Spam phrases triggering deletion: http://berklix.com/jhs/mail/
>
> 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: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87n0njta4j.fsf>