Yeah you might want to attach the kernel config just to make sure nothing was dropped that needs to be there , when you got this dc0 ip of 192.168.1.33 was that set staticly?? On Wed, 2008-02-06 at 22:48 -0600, Eugen wrote: > That's what I get when I put ipv6_enable="YES" in /etc/rc.conf : > > $ ifconfig -a > dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=8<VLAN_MTU> > ether 00:14:cf:52:b4:17 > inet6 fe80::214:cfff:fe52:b417%dc0 prefixlen 64 scopeid 0x1 > inet 192.168.1.33 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX <full-duplex>) > status: active > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff000000 > > And yes, it is a customized kernel. Would it be useful to attach my > config file ? > > Eugen > > On Feb 6, 2008 8:46 PM, OutBackDingo <[EMAIL PROTECTED]> wrote: > > But i still dont see any ipv6 data in the ifconfig for dc0, we had an > > instance where ipv6 being turned off networking stopped functioning > > > > in your ifconfig dc0 should show inet6 data like lo0 does. make sure its > > commented out of rc.conf and reboot. also is this a generic kernel or > > did you customize it ?
_______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"