Thanks for the response.
Yes - I plugged an Ethernet directly into the computer from a router. I recycled the computer more than once. In my terminal, I used /sbin/ifconfig:
jim@jim-laptop:~$ sudo /sbin/ifconfig
[sudo] password for jim:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:480 (480.0 B) TX bytes:480 (480.0 B)
jim@jim-laptop:~$ netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
I don't know if this may help.
--- In LINUX_Newbies@yahoogroups.com, "Paul" <pfrederick1@...> wrote:
>
>
>
> --- In LINUX_Newbies@yahoogroups.com, "Jim" <jverhovec@> wrote:
> >
> > When I use a direct connection, I am still not connected.
> >
> > I plug into my laptop from a Wireless router with 4 ports. Then what?
> >
> > Nothing happens. Any suggestions?
> >
> > Jim V in Ohio
>
>
> When you say, "When I use a direct connection" I assume you mean plug an Ethernet cable into your laptop. What should happen depends on a few things. One thing is when you plug your laptop in. It should be plugged in while you are booting the machine up. That is when Linux attempts to establish an automatic network connection.
>
> There are of course other ways of doing that but they are all more complicated. Anyhow that automatic network configuration will only happen if your router uses DHCP, and your system is configured to use DHCP as well. It should be, but who knows.
>
> In any event try booting the machine up with the Ethernet cable attached to it and get back to the group with what that does, or doesn't do for you.
>
> BTW one way to make a DHCP connection without rebooting is to use a command called pump
>
> $ aptitude show pump
>
> Description: BOOTP and DHCP client for automatic IP configuration
> This is the BOOTP/DHCP client written by RedHat.
>
> DHCP (Dynamic Host Configuration Protocol) and BOOTP (Boot Protocol) are
> protocols which allow individual devices on an IP network to get their own
> network configuration information (IP address, subnetmask, broadcast address,
> etc.) from network servers. The overall purpose of DHCP and BOOTP is to make it
> easier to administer a large network.
>
>
> It has been a while but I believe the command is pump -d, but you need pump installed for that to work and pump is not usually installed by default.
>
> A couple other commands that are handy to debug network issues are:
>
> /sbin/ifconfig
>
> and
>
> netstat -nr
>
> also
>
> dmesg | grep -i eth
>
> this is a fun one that may not work
>
> less `locate eth0.leases`
>
> Those are back quotation marks. They have a special meaning to the shell so get them right. If it does work space bar pages and q quits out.
>
> Any of that may yield clues as to what is going on. Networking is great when it works, but a pain to get to work sometimes. If you have a static IP that can be configured as well.
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (16) |
No comments:
Post a Comment