You are not logged in.
Hi when I modify hosts.allow on my laptop
sudo nano /etc/hosts.allow
from
#
# /etc/hosts.allow
#
# End of file
to
#
# /etc/hosts.allow
#
sshd:192.168.1.180
# End of file
** 192.168.1.180 = another desktop.
After rebooting, It just kills my network connection on my laptop. So no more internet, shares, ping or anything, ... But Im connected to my wireless router and my static ip, gateway, dns are ok. If I change it to this exact syntax
#
# /etc/hosts.allow
#
# End of file
And I reboot, the network connection works again.
The only way I've found to be able to make it work with one rule in hosts.allow is:
sudo cp /etc/hosts.allow /etc/hosts.allow.bak
sudo nano /etc/hosts.allow.bak
Change it from
# /etc/hosts.allow
#
# End of file
to
#
# /etc/hosts.allow
#
sshd:192.168.1.180
# End of file
sudo cp /etc/hosts.allow.bak /etc/hosts.allow
sudo nano /etc/hosts.allow
Change it from
# /etc/hosts.allow
#
sshd:192.168.1.180
# End of file
to
sshd:192.168.1.180
This is like the only thing I can do with it. I can't modify hosts.allow or my network connection will stop working.
I've installed firestarter and add a rule. After rebooting with firestarter running, my network connection stoped working as well, If I don't run firestarter service on boot, my network connection will work.
Weird issue, I really don't understand, maybe tcpd?
Thanks.
Last edited by lordchaos (2008-10-27 01:25:01)
Offline
I'm fairly certain hosts.allow requires spaces between elements, for example:
sshd : 192.168.1.180
Offline
I've tested it with and without space. On this fresh archlinux installation, it only worked without space, using this weird way to do it that you can read above.
I'm not new to linux and I always got it to work with hosts.allow or firestarter. Now none of them is working...
Offline
what the shit?
modifying hosts.allow is for tcp_wrappers, which allows/denies hosts _connecting-to-you_. It should have no impact on 'your internet connection'.
More likely your firestarter rules are screwing things up (or something else seriously wrong with your config/setup), and it is just a matter of coincidence not causation.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Probably, but something is wrong, it was doing it before installing firestarter. Strange...
Offline