Oh, you specifically need them to have different interfaces? That's a bit more complicated. I guess you could rig something with netgraph (ngctl and such), but I'm not familiar with it... -- Daniel Nebdal On Sat, Mar 9, 2013 at 2:57 PM, Yasir hussan <kolyasir_at_gmail.com> wrote: > i want to have differnet ips`s and each should have different interface, it > could be a virtual interface. like u can made it like > > ifconfig arge0.1 create > > but each ip should able to access from differnet machine > > On Sat, Mar 9, 2013 at 7:29 AM, Daniel Nebdal <dnebdal_at_gmail.com> wrote: >> >> Going by Zaphod's recommendation of using a /32 for each IP, how about >> this? >> >> ifconfig arge0 inet 192.168.1.100/32 >> ifconfig arge0 alias 192.169.1.100/32 >> >> I wouldn't recommend 192.169, though - only 192.168.x.x is reserved >> for private networks, and 192.169 is a valid IP-routable prefix, >> assigned to some US company. >> To be exact: The ranges from RFC1918 are 10.0.0.0/8, 172.16.0.0 /20 >> and 192.168.0.0/24. >> >> On Sat, Mar 9, 2013 at 9:57 AM, Yasir hussan <kolyasir_at_gmail.com> wrote: >> > Kindly will u give me example with cammand line, which can test on my >> > freebsd machine, i want two ips 192.168.1.100 and 192.169.1.100 to be >> > work >> > on single network interface, my default interface for network is arge0 >> > >> > On Sat, Mar 9, 2013 at 3:08 AM, Zaphod Beeblebrox <zbeeble_at_gmail.com> >> > wrote: >> > >> >> On Sat, Mar 9, 2013 at 3:04 AM, Yasir hussan <kolyasir_at_gmail.com> >> >> wrote: >> >> >> >>> i just want to run multiple IPs for single network card in freebsd >> >>> >> >>> >> >> OK. A better question. About the only caution I can give here >> >> (assuming >> >> you don't mean something more interesting like vlans and whatnot) is >> >> that >> >> if both IP addresses are on the SAME network, use a /32 as the netmask >> >> (it >> >> works better). If they are on different networks, specify the netmask >> >> as >> >> normal. >> >> >> >> You may, at this point, need a method to choose which IP address to >> >> use >> >> for any particular connection. There's a pile of documentation waiting >> >> for >> >> you. >> >> >> >> >> > _______________________________________________ >> > freebsd-current_at_freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to >> > "freebsd-current-unsubscribe_at_freebsd.org" > >Received on Sat Mar 09 2013 - 17:12:54 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:35 UTC