how do i add the ips ? freebsd was a longtime ago there is no /etc/network/interfaces ifconfig_em0_alias0="inet 174.136.101.147 netmask 255.255.255.248" is that how i add the ips ? i'm unfamiliar with freebsd maybe try it? http://pastebin.com/3emmwQcZ is that how dont rember ? that looks like first response on google oh hangon set additionals ips to netmask 255.255.255.255 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-virtual-hosts.html hmms ok not the first one in subnet thoguh fconfig_fxp0_alias4="inet 202.0.75.17 netmask 255.255.255.240" ifconfig_fxp0_alias5="inet 202.0.75.18 netmask 255.255.255.255" ifconfig_fxp0_alias6="inet 202.0.75.19 netmask 255.255.255.255" ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255" like see how they added a seperate subnet so first one has netmask of 240 then next ones 255 so if the extra ips are on diff subnet to your main ip this have the same subnet ok 255.255.255.255 <-- is one ip ? yaeh so the non alias oen has 248 and the next ones have 255 ahha ifconfig_em0="inet 174.136.101.146 netmask 255.255.255.248" ifconfig_em0_alias0="inet 174.136.101.147 netmask 255.255.255.248" ifconfig_em0_alias1="inet 174.136.101.148 netmask 255.255.255.248" ifconfig_em0_alias2="inet 174.136.101.149 netmask 255.255.255.248" ifconfig_em0_alias3="inet 174.136.101.150 netmask 255.255.255.248" so in that example change all the alias ones to have 255.255.255.255 ifconfig_em0="inet 174.136.101.146 netmask 255.255.255.248" ifconfig_em0_alias0="inet 174.136.101.147 netmask 255.255.255.255" ifconfig_em0_alias1="inet 174.136.101.148 netmask 255.255.255.255" ifconfig_em0_alias2="inet 174.136.101.149 netmask 255.255.255.255" ifconfig_em0_alias3="inet 174.136.101.150 netmask 255.255.255.255" like that then yip cross your fingers :) ok i try then :D cool hmms i dont think it works http://pastebin.com/3RXhREV2 that is wierd :/ what's it do? PING 174.136.101.150 (174.136.101.150) 56(84) bytes of data. 64 bytes from 174.136.101.150: icmp_req=2 ttl=57 time=127 ms --- 174.136.101.150 ping statistics --- 2 packets transmitted, 1 received, 50% packet loss, time 1008ms rtt min/avg/max/mdev = 127.759/127.759/127.759/0.000 ms wtf it missed the first packet? but anyway it can ping ok hmms its like i need to ping the ip one time then it works heh :D merky - first packet might be missed because arp didn't reply fast enough. that's arp, not ARP :) if you ping an IP for which you don't have the MAC, you have to arp first. hmm then the same thing would happen with syn packets and you'd get delayed connections.. and that does happen oh wait it doesn't even *send* the syn until it has a MAC it can't wait wait well router doesn't forward it along it uses the local mac of the router the packet has the destination IP, but the local MAC i'm getting more confused not less so in general, there's no delay and it always has the MAC of the router, since otherwise it wouldn't have a default route no it doesn't. in general, you won't have the MAC of the destination IP, unless it's on the same segment a default route is an ip not a mac mac's get cached yes - and you have the mac of the ip except maybe if the cache flushes but it asks for them again and again generally not macs are long-cached I've had problems with that before there was a cable isp here who used to have a really big arp domain and routers used to fail from all the arps. so if you used a shit router then the router would become unresponsive. well, in that case, the caches would get flushe dmore it took them ages to fix it so that there was multiple arp domains but really this whole arp thing seems really lame to me but anyway, the reason that syn works is that most of the time, you're talking to a remote IP and to talk to them, you first have to know your local router's mac and that's typically cached if something about that needs retry, it happens transparently on the other hand, ping insists on reporting that first timeout since that timeout really happened yeah well hopefully he got his ip's working by the way, setting up a range of IPs is easy if you use the advanced setup I have: ipv4_addrs_em0=208.79.95.2-14/28 oh i didn't know that, i'm not acutally a customer yet. and that sets up all 12 aliases and i don't use freebsd. in other words, just show the range, and the netmask i know how it works in openbsd and that takes care of everything that's actually kind of cool well ijust told him to check the freebsd handbook cos whitefang was saying everything is documented in there so it basically directly interprets the type of numbers you'd be given yeah - this isn't documented well yet and I discovered it in some blog then verified that it worked that way oh yip it's like perl docs or apache docs early tutorials had to use primitive stuff i hate perl docs but then the tool got more advanced and everyone still uses the old ways I hate tutorials from the mid-90's still being treated as modern well i kind of knew about the netmask stuff but for some reason it skipped my mind heh openbsd hasn't changed a lot you have hostname.em0 then inet blah blah then inet alias blah blah gotta start getting ready for work heh i should get to bed it's 3 am here hm ports for php5 seems to be broken can't fetch the file anywhere i asked about that earlier on silc lemme see if they figured it out nothing. but, packages appear to be back on ftp3 hm what mirror are you trying? *.php.net it seems oh. now i gotcha i automatically s/ports/packages/ slightly frustrating, just got my vps and wanted to start using it lol oh well i'll spend time migrating my home dir instead use packages does the php5 package come with fpm ? no idea