cork1958 Posted July 6, 2015 Share Posted July 6, 2015 Should be an easy question but I can't find anything or think of a good search phrase to find what I need. Here's the issue. I recently installed Debian Jessie and when inputting my static IP address in wicd, which is 192.168.0.109, it always connects on 192.168.0.148. When I manually disconnect the device and reconnect, it will then connect to 192.168.0.109. How do I make it connect to 192.168.0.109 at start up? My kids gaming system is set for 192.168.0.148. Thank you Link to comment Share on other sites More sharing options...
Aergan Posted July 6, 2015 Share Posted July 6, 2015 Are you running DHCP? Have you statically assigned DHCP range addresses to devices but not reserved them to stop them from being allocated? Link to comment Share on other sites More sharing options...
Haggis Veteran Posted July 6, 2015 Veteran Share Posted July 6, 2015 see this page https://www.howtoforge.com/debian-static-ip-address Link to comment Share on other sites More sharing options...
cork1958 Posted July 6, 2015 Author Share Posted July 6, 2015 Thanks, Haggis I've seen several of those how to type things like that but, to be honest, I despise the command line! Anyway, I went a head and tried to figure those steps out, figuring I could do no worse then wreck everything! After doing the steps required, I rebooted (I know, I wasn't required to totally reboot) to test out what IP wicd said I connected with and it said the one I want. When first attempting to browse a web page though, it went no where. Opened wicd again and disconnected everything, then reconnected. Internet worked! Opened ifconfig and it said I was connected at what I wanted to also with all the correct settings. Going to try another reboot and see what happens again. Edit: Nope, what ever I did using command line made it so I now have to open wicd and diconnect all then reconnect, to get anywhere! Doing a couple DNS test sites, it does verify I have entered the correct DNS settings I wanted to use. Connection is just fine after disconnecting and reconnecting, as mentioned above. Link to comment Share on other sites More sharing options...
c.grz Posted July 6, 2015 Share Posted July 6, 2015 I've seen several of those how to type things like that but, to be honest, I despise the command line! You despise the command line but you still went with Linux? I figured it was a requirement to love the cli if you were going to use any flavor of Linux!! Link to comment Share on other sites More sharing options...
cork1958 Posted July 6, 2015 Author Share Posted July 6, 2015 You despise the command line but you still went with Linux? I figured it was a requirement to love the cli if you were going to use any flavor of Linux!! Usually no requirement at all, now a days, as most Linux distro's are pretty gui friendly, except for a few select things. Been using Debian for a few years now without to many hiccups where I HAD to use command line. That, IMO, is the one thing that holds Linux back from gaining any significant ground as far as more users. Link to comment Share on other sites More sharing options...
Mindovermaster Moderator Posted July 6, 2015 Moderator Share Posted July 6, 2015 Command/Terminal is Linux's backbone. If you only use GUI's, I'm afraid you are right at the edge of that pool... Link to comment Share on other sites More sharing options...
simplezz Posted July 6, 2015 Share Posted July 6, 2015 It sounds like something else is automatically acquiring a DHCP address on bootup. Perhaps a service or something. Just to be on the safe side, clear out /etc/network.d/interfaces/ and make sure you're not running dhcpcd or another network tool like netcfg. You've added wicd to your service list right? Something else to consider is that you configured your router to reserve <= .109 for non DHCP addresses. Link to comment Share on other sites More sharing options...
Recommended Posts