Hello,
I recently upgraded from 5.4-RELEASE to 6.2-STABLE. Now I'm having problems
with the TCP stack. I suspect its because of code differences. I may have
some older 5.4 code that was used during the build world process. For
example, here's a partial ifconfig -a output
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=8<VLAN_MTU>
inet 71.4.48.6 netmask 0xfffffe00 broadcast 71.4.49.255
inet 71.4.48.4 netmask 0xffffffff broadcast 71.4.48.4
inet 71.4.48.7 netmask 0xffffffff broadcast 71.4.48.7
inet 71.4.48.9 netmask 0xffffffff broadcast 71.4.48.9
What's interesting is I can ping 71.4.48.6 from the console.
But I get the following whenever I ping any other aliased IP from the local
console. I can ping these from other machines.
[root 6]> ping 71.4.48.4
PING 71.4.48.4 (71.4.48.4): 56 data bytes
ping: sendto: Invalid argument
ping: sendto: Invalid argument
Looking up a domain using dig I get similar errors. It actually returns the
info I want but I still get the errors.
[root 7]> dig www.google.com
/usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1151:
internal_send: 71.4.48.2#53: Invalid argument
/usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1151:
internal_send: 71.4.48.3#53: Invalid argument
71.4.48.2 and 71.4.48.3 are my DNS.
So what I thought I'd do is move to 6.2-RELEASE. What I wanted to do is
install the source code from
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/src/* and do a
build world and build kernel. I assume that's really all I need to build a
new system. Are there any caveats to do an upgrade this way?
Thank you,
Mark Stout
VPM Global Internet Services, Inc.
530-626-4218 x205 Office
530-626-7182 Fax
530-554-9295 VoIP
916-240-2850 Cell
www.vpm.com
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
