7.0 - ifconfig create is not working as expected?



Hi,

I was using following command in FreeBSD 6.2:

# ifconfig lo1 create inet 172.16.16.2 netmask 255.255.255.0

In FreeBSD 7.0 I got an error:

# ifconfig lo1 create inet 172.16.16.2 netmask 255.255.255.0
ifconfig: inet: bad value

But it is working splitted in to two commands:
# ifconfig lo1 create
# ifconfig lo1 inet 172.16.16.2 netmask 255.255.255.0

Is this expected behavior or should I file a PR?

Miroslav Lachman
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: 7.0 - ifconfig create is not working as expected?
    ... I was using following command in FreeBSD 6.2: ... ifconfig: inet: bad value ... Is this expected behavior or should I file a PR? ...
    (freebsd-net)
  • Re: 2nd try : tap SIOCIFCREATE failure
    ... FreeBSD FreeBSD 6.2-RELEASE ... FreeBSD# ifconfig tap0 create ... ifconfig: SIOCIFCREATE: Invalid argument ... I never had to manually issue the create command, ...
    (freebsd-questions)
  • Re: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts
    ... see dmesg, ifconfig and netstat below... ... Copyright 1992-2003 The FreeBSD Project. ... 2 ports with 2 removable, ... The output of dmesg and ifconfig would be helpful in diagnosing this. ...
    (freebsd-questions)
  • Re: Netstat command output
    ... FreeBSD box acts as a router between two subnets where an ftp client is on ... MB file and at the same time initiate a netstat -w1 -Ibge0 command on the ... Note that some modern NICs with hardware checksum offloading can give false ...
    (freebsd-questions)
  • Re: The Myth of the secure Mac
    ... >> Good to see that you can interpret the command I wrote. ... >> which means it is a fork of FreeBSD. ... >> the implication that Os X somehow transcends the need for a mere CLI. ...
    (comp.sys.mac.advocacy)