f



Ping Problems On Two-Machine Linux Network

Hi.

I wonder whether anyone out there can help me.  I'm new to networking,
and have
set up my first simple network by connecting two P100 linux boxes with
an RJ-45
crossover cable.  The first of these machines, 'methuselah', is
installed with a
D-Link DE-220PCT jumperless NE2000-type card, and is running Slackware
9.  The
second, 'blockhead', is installed with an unidentified ISA
RTL8019-based
jumpered card, and is running Redhat 6.1.  Both machines' LEDs come on
when I plug in the crossover cable, and flickering on one end causes
flickering at the
other, but I can't ping properly between them.  There seems to be a
problem with
blockhead - the RTL8019-based card seems unable to receive (and also
seems to
transmit in periodic bursts).

I've disabled PnP in the BIOS on both machines, and have set the
appropriate
IRQ channels to Legacy ISA.  I've also set the IO & IRQ jumpers on the
RTL8019
card to the correct settings, using a document (8019AS.pdf) I found on
the
RealTek website, but I didn't know what settings to use for the BROM
jumpers,
so I've left them unjumpered.

Anyway, I include below the data from both machines (first before
pinging, and
then during pinging, both from blockhead to methuselah, and from
methuselah to
blockhead).  If there's any further information I could provide that
would be
useful, please ask!

I'd be very grateful for any help, as I've run out of ideas!
Thanks,

Paul.

******************************************************************************

Data for methuselah (192.168.0.1) 
*********************************

Relevant section (last few lines) of dmesg: 
*******************************************
  ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
  Last modified Nov 1, 2000 by Paul Gortmaker
  NE*000 ethercard probe at 0x340: 00 40 05 2c 7d 3d
  eth0: NE2000 found at 0x340, using IRQ 10.
  
Output of ifconfig:
*******************
  eth0      Link encap:Ethernet  HWaddr 00:40:05:2C:7D:3D  
            inet addr:192.168.0.1  Bcast:192.168.0.255 
Mask:255.255.255.0
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:100 
            RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
            Interrupt:10 Base address:0x340 
  
  lo        Link encap:Local Loopback  
            inet addr:127.0.0.1  Mask:255.0.0.0
            UP LOOPBACK RUNNING  MTU:16436  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0 
            RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
  
Output of netstat -r: 
*********************
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags   MSS Window 
irtt Iface
  localnet        *               255.255.255.0   U         0 0       
  0 eth0
  loopback        *               255.0.0.0       U         0 0       
  0 lo
  
Output of netstat -i: 
*********************
  Kernel Interface table
  Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR   TX-OK TX-ERR TX-DRP
TX-OVR Flg
  eth0   1500   0       0      0      0      0       0      0      0  
   0 BMRU
  lo    16436   0       0      0      0      0       0      0      0  
   0 LRU
  
Output of tcpdump -i eth0 (whilst being pinged by blockhead): 
*************************************************************
  tcpdump: listening on eth0
  18:20:50.374116 arp who-has methuselah.junkyard tell
blockhead.junkyard
  18:20:50.374230 arp reply methuselah.junkyard is-at 0:40:5:2c:7d:3d
  18:21:00.372555 arp who-has methuselah.junkyard tell
blockhead.junkyard
  18:21:00.372658 arp reply methuselah.junkyard is-at 0:40:5:2c:7d:3d
  18:21:10.370985 arp who-has methuselah.junkyard tell
blockhead.junkyard
  18:21:10.371113 arp reply methuselah.junkyard is-at 0:40:5:2c:7d:3d
  18:21:20.369423 arp who-has methuselah.junkyard tell
blockhead.junkyard
  18:21:20.369532 arp reply methuselah.junkyard is-at 0:40:5:2c:7d:3d
  
  10 packets received by filter
  0 packets dropped by kernel
  
Output of ping 192.168.0.2: 
***************************
  PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
  From 192.168.0.1 icmp_seq=1 Destination Host Unreachable
  (repeated another 23 times before being stopped with <Ctrl>-C)
  
  --- 192.168.0.2 ping statistics ---
  26 packets transmitted, 0 received, +24 errors, 100% packet loss, 
  time 25136ms, pipe 3

******************************************************************************

Data for blockhead (192.168.0.2)
********************************
  
Relevant section (last few lines) of dmesg:
*******************************************
  ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov)
  NE*000 ethercard probe at 0x340: 00 00 21 b1 82 08
  eth0: NE2000 found at 0x340, using IRQ 10.
  
Output of ifconfig:
*******************
  eth0      Link encap:Ethernet  HWaddr 00:00:21:B1:82:08  
            inet addr:192.168.0.2  Bcast:192.168.0.255 
Mask:255.255.255.0
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:100 
            Interrupt:10 Base address:0x340 
  
  lo        Link encap:Local Loopback  
            inet addr:127.0.0.1  Mask:255.0.0.0
            UP LOOPBACK RUNNING  MTU:3924  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0 
  
Output of netstat -r:
*********************
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags   MSS Window 
irtt Iface
  192.168.0.2     *               255.255.255.255 UH        0 0       
  0 eth0
  192.168.0.0     *               255.255.255.0   U         0 0       
  0 eth0
  127.0.0.0       *               255.0.0.0       U         0 0       
  0 lo
  
Output of netstat -i:
*********************
  Kernel Interface table
  Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP
TX-OVR Flg
  eth0   1500   0       0      0      0      0        0      0      0 
    0 BRU
  lo     3924   0       0      0      0      0        0      0      0 
    0 LRU
  
Output of ping 192.168.0.1:
***************************
  PING 192.168.0.1 (192.168.0.1) from 192.168.0.2 : 56(84) bytes of
data.
  From blockhead.junkyard (192.168.0.2): Destination Host Unreachable
  (repeated another 35 times before being stopped with <Ctrl>-C)
  
  --- 192.168.0.1 ping statistics ---
  38 packets transmitted, 0 packets received, +36 errors, 100% packet
loss
  Kernel filter, protocol ALL, datagram packet socket
  
Output of tcpdump -i eth0 (whilst being pinged by methuselah):
**************************************************************
  tcpdump: listening on eth0
  
  0 packets received by filter
0
Paul576 (9)
1/24/2004 10:52:57 PM
comp.os.linux.networking 15677 articles. 0 followers. Post Follow

4 Replies
738 Views

Similar Articles

[PageSpeed] 15

Change your Crossover cable or check your card setting for right media 
connector(only if you have a RJ45 and BNC connector present on your 
NIC). ifconfig output seems OK.It is a hardware issue.

Neeraj Gupta
neerajkgupta@hotmail.com

Paul wrote:
> Hi.
> 
> I wonder whether anyone out there can help me.  I'm new to networking,
> and have
> set up my first simple network by connecting two P100 linux boxes with
> an RJ-45
> crossover cable.  The first of these machines, 'methuselah', is
> installed with a
> D-Link DE-220PCT jumperless NE2000-type card, and is running Slackware
> 9.  The
> second, 'blockhead', is installed with an unidentified ISA
> RTL8019-based
> jumpered card, and is running Redhat 6.1.  Both machines' LEDs come on
> when I plug in the crossover cable, and flickering on one end causes
> flickering at the
> other, but I can't ping properly between them.  There seems to be a
> problem with
> blockhead - the RTL8019-based card seems unable to receive (and also
> seems to
> transmit in periodic bursts).
> 
> I've disabled PnP in the BIOS on both machines, and have set the
> appropriate
> IRQ channels to Legacy ISA.  I've also set the IO & IRQ jumpers on the
> RTL8019
> card to the correct settings, using a document (8019AS.pdf) I found on
> the
> RealTek website, but I didn't know what settings to use for the BROM
> jumpers,
> so I've left them unjumpered.
> 
> Anyway, I include below the data from both machines (first before
> pinging, and
> then during pinging, both from blockhead to methuselah, and from
> methuselah to
> blockhead).  If there's any further information I could provide that
> would be
> useful, please ask!
> 
> I'd be very grateful for any help, as I've run out of ideas!
> Thanks,
> 
> Paul.
> 
> ******************************************************************************
> 
> Data for methuselah (192.168.0.1) 
> *********************************
> 
> Relevant section (last few lines) of dmesg: 
> *******************************************
>   ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
>   Last modified Nov 1, 2000 by Paul Gortmaker
>   NE*000 ethercard probe at 0x340: 00 40 05 2c 7d 3d
>   eth0: NE2000 found at 0x340, using IRQ 10.
>   
> Output of ifconfig:
> *******************
>   eth0      Link encap:Ethernet  HWaddr 00:40:05:2C:7D:3D  
>             inet addr:192.168.0.1  Bcast:192.168.0.255 
> Mask:255.255.255.0
>             UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>             RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>             TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>             collisions:0 txqueuelen:100 
>             RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>             Interrupt:10 Base address:0x340 
>   
>   lo        Link encap:Local Loopback  
>             inet addr:127.0.0.1  Mask:255.0.0.0
>             UP LOOPBACK RUNNING  MTU:16436  Metric:1
>             RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>             TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>             collisions:0 txqueuelen:0 
>             RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>   
> Output of netstat -r: 
> *********************
>   Kernel IP routing table
>   Destination     Gateway         Genmask         Flags   MSS Window 
> irtt Iface
>   localnet        *               255.255.255.0   U         0 0       
>   0 eth0
>   loopback        *               255.0.0.0       U         0 0       
>   0 lo
>   
> Output of netstat -i: 
> *********************
>   Kernel Interface table
>   Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR   TX-OK TX-ERR TX-DRP
> TX-OVR Flg
>   eth0   1500   0       0      0      0      0       0      0      0  
>    0 BMRU
>   lo    16436   0       0      0      0      0       0      0      0  
>    0 LRU
>   
> Output of tcpdump -i eth0 (whilst being pinged by blockhead): 
> *************************************************************
>   tcpdump: listening on eth0
>   18:20:50.374116 arp who-has methuselah.junkyard tell
> blockhead.junkyard
>   18:20:50.374230 arp reply methuselah.junkyard is-at 0:40:5:2c:7d:3d
>   18:21:00.372555 arp who-has methuselah.junkyard tell
> blockhead.junkyard
>   18:21:00.372658 arp reply methuselah.junkyard is-at 0:40:5:2c:7d:3d
>   18:21:10.370985 arp who-has methuselah.junkyard tell
> blockhead.junkyard
>   18:21:10.371113 arp reply methuselah.junkyard is-at 0:40:5:2c:7d:3d
>   18:21:20.369423 arp who-has methuselah.junkyard tell
> blockhead.junkyard
>   18:21:20.369532 arp reply methuselah.junkyard is-at 0:40:5:2c:7d:3d
>   
>   10 packets received by filter
>   0 packets dropped by kernel
>   
> Output of ping 192.168.0.2: 
> ***************************
>   PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
>   From 192.168.0.1 icmp_seq=1 Destination Host Unreachable
>   (repeated another 23 times before being stopped with <Ctrl>-C)
>   
>   --- 192.168.0.2 ping statistics ---
>   26 packets transmitted, 0 received, +24 errors, 100% packet loss, 
>   time 25136ms, pipe 3
> 
> ******************************************************************************
> 
> Data for blockhead (192.168.0.2)
> ********************************
>   
> Relevant section (last few lines) of dmesg:
> *******************************************
>   ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov)
>   NE*000 ethercard probe at 0x340: 00 00 21 b1 82 08
>   eth0: NE2000 found at 0x340, using IRQ 10.
>   
> Output of ifconfig:
> *******************
>   eth0      Link encap:Ethernet  HWaddr 00:00:21:B1:82:08  
>             inet addr:192.168.0.2  Bcast:192.168.0.255 
> Mask:255.255.255.0
>             UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>             RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>             TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>             collisions:0 txqueuelen:100 
>             Interrupt:10 Base address:0x340 
>   
>   lo        Link encap:Local Loopback  
>             inet addr:127.0.0.1  Mask:255.0.0.0
>             UP LOOPBACK RUNNING  MTU:3924  Metric:1
>             RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>             TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>             collisions:0 txqueuelen:0 
>   
> Output of netstat -r:
> *********************
>   Kernel IP routing table
>   Destination     Gateway         Genmask         Flags   MSS Window 
> irtt Iface
>   192.168.0.2     *               255.255.255.255 UH        0 0       
>   0 eth0
>   192.168.0.0     *               255.255.255.0   U         0 0       
>   0 eth0
>   127.0.0.0       *               255.0.0.0       U         0 0       
>   0 lo
>   
> Output of netstat -i:
> *********************
>   Kernel Interface table
>   Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP
> TX-OVR Flg
>   eth0   1500   0       0      0      0      0        0      0      0 
>     0 BRU
>   lo     3924   0       0      0      0      0        0      0      0 
>     0 LRU
>   
> Output of ping 192.168.0.1:
> ***************************
>   PING 192.168.0.1 (192.168.0.1) from 192.168.0.2 : 56(84) bytes of
> data.
>   From blockhead.junkyard (192.168.0.2): Destination Host Unreachable
>   (repeated another 35 times before being stopped with <Ctrl>-C)
>   
>   --- 192.168.0.1 ping statistics ---
>   38 packets transmitted, 0 packets received, +36 errors, 100% packet
> loss
>   Kernel filter, protocol ALL, datagram packet socket
>   
> Output of tcpdump -i eth0 (whilst being pinged by methuselah):
> **************************************************************
>   tcpdump: listening on eth0
>   
>   0 packets received by filter

0
vishakha (1)
1/25/2004 1:55:34 AM
Paul,

I you have another crossover cable try that first.

Check both boxes to see if there's something in the firewall configuration
that may be blocking ICMP echo/reply messages. It would be unusual to block
those in a default firewall configuration.

Looking at the tcpdump it looks like the arp is working because it appears
blockhead is sending out arp requests. Methuselah can see the arp request so
transmission from blockhead to Methuselah seems to be working. Blockhead may
be blocked from receiving ICMP replies.

Bill in Sacramento, California
Land of the fruits and nuts...


0
bmungaven (2)
1/25/2004 8:11:15 AM
> Change your Crossover cable or check your card setting
> for right media connector (only if you have a RJ45 and
> BNC connector present on your NIC). ifconfig output seems OK.
> It is a hardware issue.
>
> Neeraj Gupta
> neerajkgupta@hotmail.com

Thanks - I bought the crossover cable online, and I'm fairly confident that
it's all right (of course, I may be wrong).  I suspect that the problem is with
the RTL8019 card.  However, I don't know how to set it to use the RJ-45
connector rather than the coaxial one: I sort-of imagined that the card would
figure that out for itself, seeing that there's no BNC cable connected to it.
Anyway, thanks again for the suggestions.

Paul.

> Paul,
>
> I you have another crossover cable try that first.
>
> Check both boxes to see if there's something in the firewall configuration
> that may be blocking ICMP echo/reply messages. It would be unusual to block
> those in a default firewall configuration.
>
> Looking at the tcpdump it looks like the arp is working because it appears
> blockhead is sending out arp requests. Methuselah can see the arp request so
> transmission from blockhead to Methuselah seems to be working. Blockhead may
> be blocked from receiving ICMP replies.
>
> Bill in Sacramento, California
> Land of the fruits and nuts...

Thanks, Bill.  I'm not sure that there are any firewalling measures at all in
place on blockhead, so - as you say - it's probably not that.  I agree with
what you say about blockhead being somehow blocked from receiving.  I've a
feeling that it's a hardware problem with the card, but I'll tinker with it a
bit more, and let you know if I get anywhere...
Thanks again,

Paul.
0
Paul576 (9)
1/26/2004 2:55:34 PM
Ha! 
Someone up there likes me - as a last-ditch attempt, I changed the
jumper settings on the card (they were configured correctly to work
with IRQ 10 and IO 0x340) to IRQ 11 and IO 0x280.  And it worked! 
Joy!  Don't know why it made a difference - there were no hardware
conflicts reported, either in Linux or in W!?&@#s.  Weird.  Still, my
first network is up and running, so I'm happy.
Thanks again for the suggestions.  

Paul.
0
Paul576 (9)
1/27/2004 1:14:06 PM
Reply:

Similar Artilces:

Proper routes for linux machine with two network ports to same network
Hi, I run a Fedora Core 4 system with two network devices eth0 (assigned 10.10.10.30) and eth1 (assigned 10.10.10.31). The local network is 10.10.10.0, the gateway is 10.10.10.1 # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.10.10.1 * 255.255.255.255 UH 0 0 0 eth1 10.10.10.0 * 255.255.255.0 U 0 0 0 eth0 10.10.10.0 * 255.255.255.0 U 0 0 0 eth1 169.254.0.0 * 255.255.0.0 U 0 0 0 eth1 default 10.10.10.1 0.0.0.0 UG 0 0 0 eth1 default 10.10.10.1 0.0.0.0 UG 0 0 0 eth0 Although rules to 10.10.10.0 exists for both eth interfaces, It seems that traffic going to the local network at 10.10.10.* goes thru eth0 if no interface specified. If I pull out the network cable at eth0, ping 10.10.10.100 -> Destination Host Unreachable ping 10.10.10.100 -I eth0 -> Destination Host Unreachable ping 10.10.10.100 -I eth1 -> Works fine! Similar problems exist for the internet outgoing connections with the default and 10.10.10.1 gateway routes. How do I add the routes properly so that the machine will look at which interface is working or sort of, and choose the correct route? Thanks for any pointers. fuzzybr80@gmail.com wrote: > Hi, > > I run a Fedora Core 4 system with two network devices eth0 (assi...

How to set my Linux machine to have two network cards with two IPs
Dear all gurus out there, I am newbie to Linux and networking. I have a Red hat linux that used as a Database machine, oracle. I have 2 network cards that I wish to set to 192.168.0.10 and 192.168.0.11 respectively, the default gw is 192.168.0.1. The connection of the two IPs coming from 2 different switches (still from the same router). My purpose is that : if one of the switches is down, my connection still up with the other side. I know switch is hardly "down", but i wish to have full redundancy. What I did is, I jus set the 2 network cards with the two IPs and I switch off one of the switches, "poof" the whole network down..........so, how can it be done ? Or any other alternatives ? Thanks. On Sun, 27 May 2007 02:02:58 -0700, keanewoon wrote: [link failover] > Or any other alternatives ? Try the 'bonding' driver: http://linux-net.osdl.org/index.php/Bonding And use an interface alias if you still need the second IP adress, e.g.: ifconfig bond0:1 <ipadress> ... -- -Menno. In article <1180256578.345257.44170@d30g2000prg.googlegroups.com>, <keanewoon@gmail.com> wrote: >Dear all gurus out there, > >I am newbie to Linux and networking. > >I have a Red hat linux that used as a Database machine, oracle. > >I have 2 network cards that I wish to set to 192.168.0.10 and >192.168.0.11 respectively, the default gw is 192.168.0.1. The >connection of the two IPs coming from 2 different switc...

Problem with Ad-hoc wireless network Windows to Linux (no ping)
Hello All, Sorry for the verbosity of this post... I am trying to set up an ad-hoc wireless network between two computers; one runing Windows XP and the other Linux (2.6.x, Slackware). After I have set them up I cannot ping the Linux machine from the Windows machine. This is what I have done so far: * Made sure that the Wlan card is running on the Linux machine (it is; it's a RT61 based D-Link DWL-G510). It works fine when in "managed" mode (connecting to an access-point); I'm using the latest firmware/drivers I could find. * Made sure that the Wlan card is running on the Windows machine (it is; Intel something-something built into a Dell laptop). Then I try to set things up. ** On the Linux machine: $ modprobe rt61 (load module, card is recognized) $ iwconfig ra0 essid box (ra0 is my RT61, set SSID) $ iwconfig ra0 channel 11 (we are in Europe) $ iwconfig mode Ad-Hoc (this is what I want; no encryption) $ ifconfig eth0 down (just in case; remember ra0 is the WLan card) $ ifconfig ra0 10.0.0.1 netmask 255.255.255.0 up (interface comes up) $ ifconfig ra0 ra0 Link encap:Ethernet HWaddr 00:19:5B:70:2D:D2 inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::219:5bff:fe70:2dd2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:...

Any Documentaion about How Linux Networking IP stack looklike between Linux PC (single NIC card) and Router with multiple Network interfaces (LAN and WAN)?
Any Documenttaion about How Linux IP Networking stack looklike bwteen Linux PC (single NIC card) and Router with multiple Network interfaces running on Linux (LAN and WAN)?. appreciated for links or some documentation. Thanks. ...

Connecting two networks with two linux boxes.
I have 2 networks each with a linux box as the gateway to the internet. At the moment they are VPN'd together, but are close enough to get a cable run and I'd like to connct them like this to make it quicker so each linux box will have 3 nics in it. My question is possibly a dumb one! But what should the IP for the 3rd nic in each box be? The networks are: network - linux box internal address Box 1) 10.0.12.x/24 - 10.0.12.1 Box 2) 192.168.12.x/24 - 192.168.12.1 Should the 3rd NIC in the box 1 be on the 192.168.12.x range, and vice versa but wouldn't that confuse the other network as it would think that it is a local IP when it wouldn't be. Should they both be on a different range althogether? And then set the routing up on each. ie 3 NICS in each Box1 internal 10.0.12.1 public 123.456.78.2 "intranet" 10.0.13.1 Box2 internal 192.168.12.1 public 423.243.123.32 "intranet" 10.0.13.2 If it was 2 networks with one linux box it would be easy, just not sure how you'd connect the two boxes together.... Any advice appreciated! Cheers Mark Markvr wrote: > I have 2 networks each with a linux box as the gateway to the internet. > > At the moment they are VPN'd together, but are close enough to get a > cable run and I'd like to connct them like this to make it quicker > so each linux box will have 3 nics in it. > > My question is possibly a dumb one! But what should the IP for the 3rd > ...

Free Download Ebook for linux networking guide | http://freepdf-ebook.blogspot.com/2007/12/linux-network-admin-guide.html
i have linux networking guide, their format is pdf, you can download it for free http://freepdf-ebook.blogspot.com/2007/12/linux-network-admin-guide.html Tony Andreas wrote: > i have linux networking guide, their format is pdf, you can download > it for free > http://freepdf-ebook.blogspot.com/2007/12/linux-network-admin-guide.html i have problems resolving the domain name of this link: http://www.mybook.000webhost.info/Linux%20Network%20Admin%20Guide.pdf goarilla <"kevin DOT paulus AT skynet DOT be"> wrote: > Tony Andreas wrote: >> i have linux networking guide, their format is pdf, you can download >> it for free >> http://freepdf-ebook.blogspot.com/2007/12/linux-network-admin-guide.html > > i have problems resolving the domain name of this link: > http://www.mybook.000webhost.info/Linux%20Network%20Admin%20Guide.pdf What link is that? i.e. which one on the Home Page? There are over 30 of them. mybook.000webhost.info resolves to 64.235.54.104 The link you gave opens KPDF for me - I didn't look at its contents. Doug. Doug Laidlaw wrote: > goarilla <"kevin DOT paulus AT skynet DOT be"> wrote: > >> Tony Andreas wrote: >>> i have linux networking guide, their format is pdf, you can download >>> it for free >>> http://freepdf-ebook.blogspot.com/2007/12/linux-network-admin-guide.html >> i have problems resolving the domain name of this link: >>...

linux network problem
we have many RHEL 3 Update 9 servers who's bnx2 driver (v52d) STOPS sending packets and they pile up in the SEND QUEUE when viewing through 'netstat -a'. This problem happens randomly and we cannot consistently duplicate it. What could I do on the local box between the 2 'on board' NICS to force loads of data from one NIC to the other to try to duplicate this problem? ...

I want to study linux network but I have not a network
HI, I am using debian 3.0 as my linux PC and I want to study the linux network administartion. When I only have one pc, is it possible for me to study it on this only one PC? Is any emulation that can be done to construct a virtual network within my PC? Any help appreciated! Chen On Tue, 02 Nov 2004 19:06:40 +0800, Chen Bin wrote: > HI, > > I am using debian 3.0 as my linux PC and I want to study the linux > network administartion. When I only have one pc, is it possible for me > to study it on this only one PC? > > Is any emulation that can be done to construct a virtual network within > my PC? You can use Vmware (www.vmware.com), but it's quite expensive. The workstation edition costs $189. But you can get a 30 day fully functioning trial version. -- Rolf Arne Schulze Trans-atlantic weightloss challenge: http://tawlc.net/ Personal weblog: http://roffe.ronningveien.net/ In comp.os.linux.networking Chen Bin <binch@mobilesoft.com.cn>: > HI, > I am using debian 3.0 as my linux PC and I want to study the linux > network administartion. When I only have one pc, is it possible for me > to study it on this only one PC? > Is any emulation that can be done to construct a virtual network within > my PC? You can do almost anything just over loop-back, like "ssh localhost" no need for any emulation, you already have one. -- Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94) mail: echo zvpunry@urvz...

Strange problem: no problem with Linux, when I boot windows 2K network is down...
Guys: This is very strange problem, looklike this problem is not going to leave me for months. I have a computer with Windows2K and Linux. I have Netgear 4-port Switch/Router (connected to DSL modem). If I boot with Linux, everything is OK, I can be on-line, also two of my other computers works fine. If I boot my PC with Win2K, then immediately all computers are down. None of the computer connected to network. I thought some problem with LAN card, so I went for early bird sale on day after Thanksgiving and I got one LinkSys PCI LAN card and one Router and I plugged new LAN card into my machine, then I booted with Windows, same problem. No problem on Linux side, then I changed my Router with new Router, samething. CAN SOME EXPERT SUGGEST ME, WHAT IS HAPPENING with my Win2K machine. But if I bypass Router and connect directly from DSL modem to my Win2K PC, then it is working. Why win2K pc is not working with Router. I have two more XP machines connected top 4-port switch (one is with cable and other one is with 802.11), they are working fine. Can somebody suggest me, how can I fix this. I verified MAC address, all are Unique MAC's. Thanks in advance. Santa wrote: > Guys: > > This is very strange problem, looklike this problem is not going to > leave me for months. I have a computer with Windows2K and Linux. I > have Netgear 4-port Switch/Router (connected to DSL modem). If I boot > with Linux, everything is OK, I can be on-line, also two of my other...

Two network adapters on seperate networks problem
Greetings. Here's my situation: I have a PC running SuSe 9.3 that has two NIC's. One of these is configured with a static IP such as: device: eth0 IP: 10.9.81.204 Subnet Mask: 255.255.255.192 Default Gateway: 10.9.81.193 This is an "isolated" network. By this I mean that the routers on this network have extensive access control lists so that only certain machines on this network can see other machines. There is no access from this network to the public internet, (the proxy server for the internet is blocked on this network). My other NIC is configured to get an IP via DHCP (although I could get a static IP if that would help). It gets an IP like: device: eth1 IP: 10.9.16.140 Subnet Mask:255.255.255.0 Gateway: 10.9.16.1 This network does have a connection to the public internet through a proxy server at IP 10.22.2.100. I can ping and ssh to machines on both networks. Machines on both networks can see me, even my samba shares. But, I cannot get to the public internet from my machine, it seems that my connection to the proxy server is blocked. I suspect it is because my default gateway is going through eth0 onto the private network. If I remove the default gateway entry, then I can get to the public internet, but I loose the connection I have to machines on the "isolated" network network. Is there some sort of solution that will allow me to have my default network traffic go to the eth1 adapter configured via DHCP, and still allow traffic to go ...

problem with Linux box on network
I have a small home Ethernet network. One machine is running Slackware Linux 13.0, KDE 4.2.4 and KMail 1.11.4 and Firefox. The other runs Windows XP. My ISP is Time-Warner and I have a broadband connection to the Internet. Everything was working fine with the network, but suddenly email downloads from Time-Warner's Road Runner POP server started to get erratic. At first it seemed that rebooting helped, but now I can't download my email at all. I can usually ping the POP server, and I can always download my email from the Windows machine, so it appears there is nothing wrong on the server side. I can generally send email (although it appears to be a little slow, and sometimes a perfectly ordinary email gets stuck in the outbox). Coincidentally, Firefox on the Linux box is also behaving erratically. HTML processing get's stuck on "Waiting for xyz.com...". HTML requests do not time out at the server, but the page never comes. (Again, Firefox on the Windows machine works normally.) The fact that I have problems with *both* KMail (a KDE app) *and* Firefox makes me suspect there is a problem with the underlying TCP/IP plumbing on the Linux machine. Is there a buffer overflowing somewhere? A corrupted cache? Is there a log file I can look at? Thanks & Best Regards, Vwaju NYC On Wed, 27 Jul 2011 17:48:07 -0400, Vwaju <slack@rcn.com> wrote: > The fact that I have problems with *both* KMail (a KDE app) *and* > Firefox > makes...

problem networking Linux and XP
I have Centos and XP installed on separate machines and connected using a crossover cable. I configured the network cards of both machines with static IP addresses. I have disabled the firewalls on both machines. The problem is: I can ping the Centos machine from the XP machine. However, when I try to ping XP from Centos, the ping request arrives at the XP machine but no reply arrives back at the Centos machine. I would appreciate some help with this. On Thu, 26 Jun 2008 15:01:49 -0700, esrom wrote: >> I would appreciate some help with this. get rid of XP? On Thu, 26 Jun 2008 15:01:49 -0700, esrom rearranged some electrons to say: > I have Centos and XP installed on separate machines and connected using > a crossover cable. > I configured the network cards of both machines with static IP > addresses. > I have disabled the firewalls on both machines. > > The problem is: > I can ping the Centos machine from the XP machine. However, when I try > to ping XP from Centos, the ping request arrives at the XP machine but > no reply arrives back at the Centos machine. > > I would appreciate some help with this. Turn off the built-in XP firewalls. david wrote: > On Thu, 26 Jun 2008 15:01:49 -0700, esrom rearranged some electrons to > say: > >> I have Centos and XP installed on separate machines and connected using >> a crossover cable. >> I configured the network cards of both machines with static IP >&...

weird linux networking problem
Just wondering if anyone has experienced anything like this, and if so, if they have any idea what could be causing it. A number of our boxes are HP dx5150 running Red Hat 4.3 (kernel 2.6.9-42). The onboard NIC is Broadcom BCM5751 Gigabit. Every now and then, these boxes lose contact with the network: we find that the central network switch (Cisco) has shut down the port, having apparently detected that the MAC address of the connected box has changed. Once the security on the port is reset, everything continues as normal. (The incorrect MAC address detected by the switch is always 08:00:45:00:FF:F8.) Obviously, this is now a fairly old version of Red Hat, and we've found that an upgrade to kernel 2.6.9-55 seems to solve the problem (we have application-related constraints limiting the kernels to which we can upgrade.) However, it would be really good to understand this problem. Any ideas? On Wed, 5 May 2010, in the Usenet newsgroup comp.os.linux.networking, in article <f68557e2-f392-4638-821c-b547d39013cc@a34g2000yqn.googlegroups.com>, pduffy wrote: NOTE: Posting from groups.google.com (or some web-forums) dramatically reduces the chance of your post being seen. Find a real news server. >A number of our boxes are HP dx5150 running Red Hat 4.3 (kernel >2.6.9-42). The onboard NIC is Broadcom BCM5751 Gigabit. [compton ~]$ etherwhois BROADCOM 00-10-18 (hex) BROADCOM CORPORATION 001018 (base 16) BROADCOM CORPORATION ...

Linux
Hi all, I have quite unusual problem with my home network and i hope there is someone who knows the solution. there are 3 networked computers I run dual boot machine with winxp and slackware 9.1 linux, NIC is via-rhine running on default kernel driver, i think that version is 1.10, i have few services running like proftpd, httpd, samba, and they are accessible from the internet thanks to noip software. the problem is that im connected to the internet using internet connection sharing on winXP machine. when i use winxp on my comp everything works fine, but when i want to use linux (that would be probably most of the time) everything works fine for a while, sometimes its 3 hours sometimes 3 minutes, and then windows machine 'forgets' about my linux box. from that moment there is nothing i can do, i can't ping to that computer because it looks like its switched off. when i reboot it won't help, i can't see connection even in windows (network cable disconnected). the only thing that helps is disabling and enabling network connection on winXP machine sharing the internet. problem is that i have very limited access to that machine and it's real pain sometimes when i cant use internet for the rest of the day, just because i wanted to use linux for a while. i think i didnt have that problem before i upgraded slackware from 9.0 to 9.1, NICs in winxp are some kind of realtec cards, one of them built into the motherboard, but the problem is with both of them. i&#...

Odd linux networking problem
Hi, I'm currently dealing with a very strange networking problem. I suspect it's the OS (Debian testing) on the client that is causing the problem, but as a matter of fact, I'm not absolutely sure. We're running a home network of about 10 PCs, which used to be connected with an 802.11b-network with a D-Link WLAN AP and DSL router (DL-713P). Now we're migrating from to a 802.11g AP (Linksys WAP54G) for the Wireless, which will eventually be connected to a Linux server, but currently is connected to one of the three ethernet ports on the D-Link router. Now, we've started to one by one switch the clients from the old 11 Mb AP to the new Linksys, which is working fine for all Windows clients. It also used to work with the aforementioned Debian machine, but somehow, it's not working any more. The symptoms are: - it connects to the AP just fine - it can connect to any other client on the network and vice versa - it can *not* connect to the D-Link router, neither ping nor anything else gets a connection - running "arp" takes very long, but eventually finds out all MACs - I don't really know what to make of what ethereal shows me; the router reacts immediately to ARP requests, but nothing else seems to come out of it. I'm totally clueless...any suggestions! Thanks Bela -- Bela Bauer - bela_b@gmx.net www.aitrob.de - www.drsl.de ...

[News] [Linux] Linux the Platform of Choice for Network Processor
Dual-core network processors sample with Linux ,----[ Quote ] | The OpenWRT BSP includes the open U-Boot bootloader, a Linux | 2.6-series kernel, filesystem, drivers, web-based configuration system, | make files, and a VoIP-enabled PBX application. `---- http://www.linuxdevices.com/news/NS3501901164.html Roy Schestowitz <newsgroups@schestowitz.com> espoused: > Dual-core network processors sample with Linux > > ,----[ Quote ] >| The OpenWRT BSP includes the open U-Boot bootloader, a Linux >| 2.6-series kernel, filesystem, drivers, web-based configuration system, >...

linux neewbie : Configuring linux client in a windows network
Hi , I have a windows 2000 server running as the domain controller. I want to add a LINUX (RED HAT 9.0) computer as a client in this network. What software do i need to do this ? Thanks in advance. BNS MIke typed: > I have a windows 2000 server running as the domain controller. I want > to add a LINUX (RED HAT 9.0) computer as a client in this network. > What software do i need to do this ? > you'll have everything you need to accomplish this. samba is what will work: http://us1.samba.org/samba/samba.html 'man smbclient' 'man smbmount' or try this HOWTO: http://www.tldp.org/HOWTO/SMB-HOWTO.html -- - Linux: the choice of a GNU generation - free; as in free speech and free beer remove '.eh' to email ...

1pc, 2 network devices in same network -> ping problem
Hello, Consider the following situation: kernel 2.4 1 pc, 2 network devices Both devices have an IP of the same network e.g. net_device1 has IP 192.168.0.1 net_device2 has IP 192.168.0.2 This results in the following routing table (dependent of which device is firstly initialized with ifconfig ... up): .... .... 192.168.0.0 * 255.255.0.0 U 0 0 0 net_device2 192.168.0.0 * 255.255.0.0 U 0 0 0 net_device1 When pinging to net_device1, net_device2 responds to the arp-request and the ping instead of net_device1 (even when the cable of net_device1 is unplugged). Thus net_device2 kind of becomes the "gateway" of network 192.168.0.0. Net_device1 never responds. How can I change this behavior to obtain that: - net_device1 responds to an arp-request and a ping to 192.168.0.1 - net_device2 responds to an arp-request and a ping to 192.168.0.2 ? This is needed for monitoring purposes (to be able to switch between a main e.g. net_device1 and backup device e.g. net_device2). Thx Pieter Beyens ...

[News] [Linux] Company Offers Specialised Linux Networking Stack
Linux networking stack scales to 64 virtual MIPS64 cores ,----[ Quote ] | 6WindGate says its commercial Linux networking stack supports | a Continuous Computing (CCPU) ATCA board powered by 16 | MIPS64-compatible cores. `---- http://www.linuxdevices.com/news/NS2103965321.html Related: Development Kit Simplifies Design of Linux Based Device Networking Products ,----[ Quote ] | Oxford Semiconductor has introduced a software development kit for | its OXETHU954 network connectivity controller chip aiming to | dramatically simplify the design of Linux based device | networking products. `----...

How to check network status on the Linux machine
Hi: Recently, I wrote a program on a Linux machine which is able to detect whether the machine is connected to the network. I used the Linux netstat program with the �i option to do the trick. netstat has a running flag (shown as a R when exercute netstat �i command), which will be turned on if the network cable is plugged into the machine and vice versa. However, it turns out that on some motherboards (I am using on broad network cards) the netstat will fail to detect the connection status. That is, no matter the network cable is plugged in or not, the running flag (R) is always on. The ...

I have Linux! I have Linux!
Ok, after two days of trying to get Windos 1900 installed and working , I sat down an hour ago and installed Linux. In an hour. Smirk. Ok, I will be honest. I did have some problems, but I believe they were of my own ignorance. 0) I started with trying to install Suse. However, I couldn't get it to install. Why? Because I didn't read the menu. There is a startup menu and the first entry is boot to harddisk. I thought that was the thing to do so I did it about 4 times. Then I gave up. However, I went back to it and subsequently realized that I should have chosen the 2nd men...

My Linux is not your Linux
To the denizens of comp.os.linux.advocacy! So many people demonstrate in this newsgroup that they know only a Linux of Hatred and Greed, of paranoia, and of a selfish sense of entitlement. They seem always to be behaving like monkeys in reaction to human dissenters, throwing feces at one another and beating their chests pretending to know something. My Linux is not that Linux. My Linux is the Linux of Love, of sharing, friendship, community. It is a uniquely human Linux and not one for monkeys. When I speak with fellow Linux users in real life (i.e. not in the monkeyhouse of COLA) they remind me of myself: practical, freedom-loving, anti-corporate. Here in COLA however they remind me of monkeys or spoiled brats or worse, corporate sysadmins. My Linux is not your Linux. It is the human Linux that acknowledges that Linux involves human work to create, that although it is free you are not entitled to it, that although it is created in large part by volunteers, they deserve to be paid for their gifts with at least gratitude. And that monkeys and self-entitled brats and sysadmins never thank anyone. yarmfelder@yahoo.com writes: > To the denizens of comp.os.linux.advocacy! You crossposted to gnu.misc.discuss. > My Linux is not your Linux. It is the human Linux > that acknowledges that Linux involves human work > to create, that although it is free you are not > entitled to it, that although it is created in large part > by volunteers, they deserve to be pa...

Why linux is linux
We don't destroy, we create. We don't imitate, we build. We are not a network, we are a personal OS. -- http://www.texeme.com Hi John, Attempting to Speak for Linux, You wrote: << We don't destroy, we create. We don't imitate, we build. We are not a network, we are a personal OS. >> Linux is more like this: << Like everything else, we consume and are consumed. We exchange ideas with everyone, to the point where it's almost impossible to track. We are artisans, not mass producers. >> Jeff Relf wrote: > Linux is mo...

User Mode Linux = Network Problem
Hi, I have problems to set up the network with user-mode-linux, I can't set up the eth0 interface under UML. The Host system is a Debian 3.0, ip adress 192.168.1.3, kernel 2.4.10 with tun/tap, netlink device emulation... For UML, root filesystem is Debian 3.0, ip adress 192.168.1.101, kernel 2.4.16 To configure the network, I have done : On the host : [root @host]# tunctl -u root Set 'tap0' persistent and owned by uid 0 [root @host]# ifconfig tap0 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255 [root @host]# ifconfig eth0 Link encap:Ethernet HWaddr 00:60:97:8D:90:2F inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:3 Base address:0x300 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 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:560 (560.0 b) TX bytes:560 (560.0 b) tap0 Link encap:Ethernet HWaddr 00:FF:6F:7B:09:DD inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 UP B...

Web resources about - Ping Problems On Two-Machine Linux Network - comp.os.linux.networking

L.A. homeless man arrested with two machine guns
Sheriff's deputies arrested Richard Cunningham over the weekend, charging him with possession of five guns and ammunition, raising a debate about ...

Rocket propelled grenade launcher, World War Two machine gun and Kalashnikov seized by armed police after ...
Two men have been arrested after police seized a rocket launcher, World War Two machine gun and AK-47 rifle (pictured) following a ten-man brawl ...

Two Chinese toddlers dead in washing machine
Two Chinese toddlers dead in washing machine People's Daily Online Police are investigating the deaths of two toddlers whose bodies were found ...

Rise Of Glory Review: Biplanes And Machine Guns, Two Great Tastes That Go Great Together
I've been a fan of air combat games for years, but most titles of this sort are done in a very "arcade" way with simplified controls. This is ...

U.S. Takes Back World Supercomputer Crown, With Two Fastest Machines
... way to the top spot in six short months. Now, for the first time in three years, the U.S. holds the top two spots, with Titan and the IBM machine ...

Rube Goldberg Machine Tells Story Of A Ball Trying To Save His Two Ball Brothers
This is Biisuke's Big Adventure , a Rube Goldberg machine that follows a red ball named Biisuke on his quest to save Biita and Biigoro, his green ...

This Machine Can Sequence a Genome in Just Two Days
Researchers at a hospital in Kansas have been using this machine to crank out entire genome sequences of just-born babies in two days—which could ...

Team USA FIBA Weekend Recap: A Machine With Two Settings
Team USA either must be smiting ruination upon the world’s basketball pretenders, or it must be learning important object lessons about respecting ...

Time Machine From Inventor In Iran Predicts Your Future Life, Two Percent Maybe Not
A time machine from an Iranian inventor promises to predict your future life. As previously reported by The Inquisitr , there was a claim of ...

How Japan Can Churn Out Game Machines for the Next...Two Hundred Years
Our glittering game machines and our shiny gadgets aren't made possible by merely fancy tech and electricity. They are here because minerals ...

Resources last updated: 3/14/2016 2:43:47 PM