Change configuration for static IP

[ONEEYEMAN]

Hi, ALL,
I don't know whether this belongs to here or in Networking, but I'd like to start somewhere...

I had a nicely configured working Gentoo install on the DHCP. Now, I wanted to install Samba on that machine.
So, I did install and configured Samba.

Since I wanted to connect to this machine from Windows XP I did change my router configuration to assign a static IP address to this machine.

Now in order to work with static IP I changed the configuration according to the Handbook adding the address to the /etc/conf.d/net file.

In the Samba configuration I bound Samba to use wlan0 inteface.

Now the problem.

I rebooted the machine and after that strange things started to happen.

After re-boot I issued "startx" and then nothing happened. X didn't want to start. No error messages, no nothing. It was just sitting in the CLI waiting for something.

I hit Ctrl+C got back to the shell prompt. Trying to investigate I checked and to my surprise there was no net.wlan0 file for the wireless interface.

So I made one, added it to the "default" runlevel and rebooted.

Now, the boot went thru, but in the end there was no shell prompt. The boot stopped at the line:

"This is <host_name>"

without going to the shell prompt.

So, now I need someone's help.

What I did wrong and how do I fix it?

I can probably unmerge Samba for now to make the static IP going first, and then continue with Samba installation.

Thank you.

[Hu]

Given the very limited information, my guess would be that DHCP configures something else that is important to you. With DHCP disabled, that something is not configured and so problems arise. Why did you switch off DHCP if it was working? DHCP with reservations is almost always superior to static configurations maintained separately for every system.

[ONEEYEMAN]

Hi,
So now I have 2 questions.

1. I reconfigured my router to use static IP for my Gentoo machine and for Windows XP machine. Now are you saying that I could just use DHCP even in this case?
2. How do I restore my system to the working condition on the wireless network?

The funny thing is that it is working on eth0 (wired connection).

Also if you need anything else, just ask. I didn't know what to post.

Thank you.

[khayyam]

[ONEEYEMAN]

Hi,
I temporary removed Samba, changed /etc/conf.d/net to use DHCP and corrected /etc/hosts.
Now I rebooted and everything works.

I am going to finish my project and then will try Samba.

Thank you.

P.S.: If you are familiar with Samba and how to make it work over the wireless network I'm all ears.

[Hu]

Some people misuse "static IP" to include both the idea that there is no central management and the idea that addresses are centrally managed, but reserved so that the same result occurs every time. I assumed from context that the OP configured for the former, but the latter is a better arrangement, since it permits the DHCP server to set routes, advertise NTP, etc.

[krinn]

You shouldn't assign your hostname to the localhost but to an network one.

So do :
127.0.0.1 localhost
192.168.0.2 oneeye

localhost is special and bypass rules made on other interface. You should never assign any host to loopback except to explicitly create bogus traffic (like redirecting some url to localhost in order to ignore the url as done with rough publicity filtering).
Multicasting and brodcasting from localhost should be drop, so oneeye will be mute and services using it will not work.
So ping oneeye should resolve to 192.168.0.2 or 3... hostname -i should return your eth or lan interface ip but not 127.0.0.1

There might be other reasons i'm not aware of.

[khayyam]

[krinn]

[khayyam]

[Jaglover]

This is OK