Quote From : kyme32 October 26, 2013, 2:33 am
i've changed the primary ip to my lan ip(machine ip it's lan ip)and now everything works as it should BUT, it's not visible to others, works only for me(tested via proxy online) or maybe somebody from here can confirm that
http://kyme32.ro
should say "kyme32.ro page" later i'm gonna ask one of my friends to give me his mac address to put my wmware bridged with my internet due the mac auth i can't do that right now, my internet provider use macs to validate login, now my wmware it's bridged with my actual router and manually set to 192.168.0.2 as a internal ip, this ip i used for primary ip, the same ip from ifconfig eth0
i have a old switch and when i get that mac i would use it to connect both(pc and wmware)to internet provider network and have 2 different external ip's and reinstall the whole thing
honestly, try to play by punctuation rules and use passages - cause I don't understand a thing u try to say.
Quote From : kyme32 October 26, 2013, 2:33 am
one small fast question, what should i use under installing centos as hostname?
if i use kyme32.ro(my primary domain) it will be fine?or it may cause problems(better usei localhost)? or "localhost.kyme32.ro"?
Localhost ist a very bad idea, since this is pre-defined. kyme32.ro is no hostname, it is a domain-name. host.kyme32.ro would be a hostname.
U need to read some stuff about DNS and FQDN!
Quote From : kyme32 October 26, 2013, 2:33 am
honestly i don't understand how this should work if i use my local ip for primary ip, on my point of view that ip access every user on my domain, it's like if they have an apache on 192.168.0.2 on there lan they will see they server on my domain(kinda if you get what i mean, maybe not, i don't know, it's something beyond my knowledge) it may be only due propagation my new ip but
Of course, no one can access your webserver if you don't route and foward ports.
You need to tell your firewall to send every package coming in on external:80 send to internal:80 - Port 443 similar. Do you have an Knowledge in networking, routing and Port-fowarding?
If not, then I'd suggest you cut the idea about a routing firewall and put your webserver straight into the internet and try to secure it on itsself.
Or you start learning a lot of stuff very very fast.
Powered By AEF 1.0.8 © 2007-2008 Electron Inc.
October 26, 2013, 9:35 am | Post: 12
