On Mon, Sep 24, 2001 at 09:15:38AM +1200, Juha Saarinen wrote:
:: I don't think any RFC actually calls for this, but 1122 is probably
:: the relevant reference. From 3.2.1.3:
:: (g) { 127, any }
::
:: Internal host loopback address. Addresses of this form
:: MUST NOT appear
On Sun, Sep 23, 2001 at 01:24:49AM -0400, Kutulu wrote:
Linux does have some company, though not very prestigious... from Win2k
Professional:
Pinging 127.1.2.3 with 32 bytes of data:
Reply from 127.1.2.3: bytes=32 time10ms TTL=128
Reply from 127.1.2.3: bytes=32 time10ms TTL=128
Reply
Juha Saarinen [EMAIL PROTECTED] writes:
I thought about some of the things mentioned in that thread, and having
the ability to use some of the 127/8 addresses could actually be useful.
Is it possible to create aliases for the loopback interface?
I'm not sure this is relevant, but I wondered
On Sun, Sep 23, 2001 at 06:01:48PM -0700, Gary W. Swearingen wrote:
Juha Saarinen [EMAIL PROTECTED] writes:
I thought about some of the things mentioned in that thread, and having
the ability to use some of the 127/8 addresses could actually be useful.
Is it possible to create aliases
:: FYI, RFC 990 is obsolete, the current version is RFC 1700:
:: 1700 Assigned Numbers. J. Reynolds, J. Postel. October 1994. (Format:
:: TXT=458860 bytes) (Obsoletes RFC1340) (Also STD0002)
:: (Status: US:)
:: (Status: STANDARD)
g) {127, any}
Internal host loopback
All my 4.3 and 4.4 boxen have problems with the only lookback address
being valid is 127.0.0.1 instead of the entire /8.
My ifconfig looks like:
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
Lamont Granquist [EMAIL PROTECTED] probably said:
All my 4.3 and 4.4 boxen have problems with the only lookback address
being valid is 127.0.0.1 instead of the entire /8.
My ifconfig looks like:
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 ::1 prefixlen 128
