WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Network Interface  (Read 3646 times)

Offline cURIOUSgEORGE

  • Full Member
  • ***
  • Posts: 140
Network Interface
« on: May 18, 2011, 01:14:23 PM »
 Would anybody be so kind to tell me a "step by step" guide on changing my ip address, "in dummy terms".
I've done it in windows before so I know that it can be done but I'm completely lost in TC.

Thanks, George

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Network Interface
« Reply #1 on: May 18, 2011, 01:33:35 PM »
Use the network button on the control panel.

Offline cURIOUSgEORGE

  • Full Member
  • ***
  • Posts: 140
Re: Network Interface
« Reply #2 on: May 18, 2011, 02:21:07 PM »
 Yes, I got to the Network Interface but I was looking for step by step instructions on how to fill it out.

IP Address __________ <--------------- I have a desktop, does that matter on the numbers I put and also how do I know if the number is already taking or not?

Network Mask _________ ?

Broadcast __________ ?

Gateway __________ ?

Nameservers __________ ?
                          __________ ?


How do I determine these numbers?

Thanks, George

Offline Lee

  • Hero Member
  • *****
  • Posts: 645
    • My Core wiki user page
Re: Network Interface
« Reply #3 on: May 18, 2011, 03:56:34 PM »
If you are not using a local router then you probably need to get the correct settings from your ISP.  They will probably have you use DHCP.

If you are in a workplace setting with IT people in charge of the network, they can help you.  They might have you use DHCP.

IP Address: If you are assigning a specific address (static IP address), then you should know what addresses are available.  If you are using DHCP then you don't need to fill in this field.

Assuming that you are not using DHCP, when you fill in the IP address the network tool will fill in some default, but not necessarily correct, guesses for some of the other fields.

On my home network, my router is at 192.168.0.1 (which is a common default address for a home router.  Sometimes you see 192.168.1.1 or 10.0.something.) so I use addresses in the range 192.168.0.xxx.  On my desktop system, I use 192.168.0.96 and the network setup tool fills in (I'm doing this from memory so it may not be completely accurate but should give you the idea):

network mask 255.255.255.0
broadcast        192.168.0.255
and
gateway          192.168.0.254

The gateway default is wrong in  my case and I suspect it is wrong for the majority of home users with local routers.  I always have to change it to 192.168.0.1 which is the address of my router.

My router also acts as a "caching DNS server" so I put in the address of the router here, as primary and my ISP's DNS server's IP address as the secondary.


32 bit core4.7.7, Xprogs, Xorg-7.6, wbar, jwm  |  - Testing -
PPR, data persistence through filetool.sh          |  32 bit core 8.0 alpha 1
USB Flash drive, one partition, ext2, grub4dos  | Otherwise similar

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Network Interface
« Reply #4 on: May 18, 2011, 10:29:15 PM »
gateway          192.168.0.254

The gateway default is wrong in  my case and I suspect it is wrong for the majority of home users with local routers.  I always have to change it to 192.168.0.1 which is the address of my router.

My router also acts as a "caching DNS server" so I put in the address of the router here, as primary and my ISP's DNS server's IP address as the secondary.

192.168.0.254 is common as gateway with certain brands of routers, as is 192.168.0.1 et al.

Alternatively one could use a public DNS service.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7183
    • My Community Forum
Re: Network Interface
« Reply #5 on: May 19, 2011, 02:08:05 AM »

192.168.0.254 is common as gateway with certain brands of routers, as is 192.168.0.1 et al.

Alternatively one could use a public DNS service.

Or any other, depending on LAN settings. My GW is 192.168.0.6 but it can be 10.x.x.x or whatever. 192.168.1.1 is also common with certain SOHO routers. Without exact knowledge no easy way to find out topology. Use DHCP.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Network Interface
« Reply #6 on: May 20, 2011, 06:04:26 PM »

Offline yetanotherusername

  • Newbie
  • *
  • Posts: 18
Re: Network Interface
« Reply #7 on: May 23, 2011, 07:51:43 AM »
What if I'm using microcore as a server, and all I have is a command line interface.
I purchased a dedicated server, and my host gives me:
Main IP
default gateway
subnet mask: 255.255.255.248
(+ 4 additional IPs)
So I ran:
        tc@box:~$ sudo ifconfig eth0 [Main IP] netmask 255.255.255.248 up
        tc@box:~$ sudo route add default gw [default gateway] netmask 255.255.255.248 eth0
Problem is, I still can't ping my default gateway (using iKVM to configure the server), but I can ping the default gateway from my desktop, but not the Main IP. So no connection to the internet from my server. Am I doing something wrong here, or is it something in the datacenter blocking me you think?

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Network Interface
« Reply #8 on: May 23, 2011, 11:02:34 AM »
Try:
sudo route add default gw [default gateway]