erin c's questions

I have two machines that are connected to the same switch. Machines have multiple ethernet interfaces connected to the different networks. Computer A can ping an antenna which is connected to the same switch, but can not ping Computer B using correct interface.(via ping -I eth2 in my case), but Computer B can ping the antenna and can ping Computer A using correct interface ( via ping -I eth9 in my case).

I checked interface details they both have same subnet masks, I tried tracert -i , results were consistent with the problem I mentioned above but it didn't reveal much. tracert on computer A took 30 hops and in the end it couldn't reach computer B. route command showed me routing tables are similar, only difference that I see is computer B have two interfaces defined in subnet but only one is physically connected at the time, can that be causing this weird problem? Any suggestions would be appreciated.

computer A

eth0      Link encap:Ethernet  HWaddr 68:05:ca:02:e3:5c  
          inet addr:16.1.8.61  Bcast:16.1.63.255  Mask:255.255.192.0
          inet6 addr: fe80::6a05:caff:fe02:e35c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:144031 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11423 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:11302308 (10.7 MiB)  TX bytes:853551 (833.5 KiB)
          Memory:fe8e0000-fe900000 

eth2      Link encap:Ethernet  HWaddr 00:d0:c9:ce:6d:7c  
          inet addr:192.168.1.15  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:c9ff:fece:6d7c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:168 errors:0 dropped:0 overruns:0 frame:0
          TX packets:402 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:17398 (16.9 KiB)  TX bytes:41787 (40.8 KiB)
          Memory:fe9e0000-fea00000 

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:120 errors:0 dropped:0 overruns:0 frame:0
          TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:8480 (8.2 KiB)  TX bytes:8480 (8.2 KiB)

computer B

    eth7      Link encap:Ethernet  HWaddr 00:d0:c9:ce:6c:b2  
          inet addr:16.1.8.64  Bcast:16.1.63.255  Mask:255.255.192.0
          inet6 addr: fe80::2d0:c9ff:fece:6cb2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:134026 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3212 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:10611871 (10.1 MiB)  TX bytes:272509 (266.1 KiB)
          Memory:fe9e0000-fea00000 

eth8      Link encap:Ethernet  HWaddr 68:05:ca:02:e1:c2  
          inet addr:192.168.1.60  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:8228  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:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Memory:fe8e0000-fe900000 

eth9      Link encap:Ethernet  HWaddr 68:05:ca:02:e1:c3  
          inet addr:192.168.1.57  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::6a05:caff:fe02:e1c3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:383 errors:0 dropped:0 overruns:0 frame:0
          TX packets:157 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:40794 (39.8 KiB)  TX bytes:15778 (15.4 KiB)
          Memory:fe880000-fe8a0000 

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:250 errors:0 dropped:0 overruns:0 frame:0
          TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:22872 (22.3 KiB)  TX bytes:22872 (22.3 KiB)

Routing Table A

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth2 localnet * 255.255.192.0 U 0 0 0 eth0 default pfizmir.xxxx 0.0.0.0 UG 0 0 0 eth0

I have couple of debian boxes at the office where we have a dns server, so ftp'ing to these boxes from a windows machine using a .net application is fairly faster and we had no issues. As closer we get to deployment of our project, we get to set up a test environment where we connect these windows boxes and debian boxes via a switch and there's no dns server, all IP addresses are manually set and they are static. And we're experiencing a very peculiar problem, all ftp operations are timing out. Machines can ping each other, we have connectivity, but it's just that ftp is super slow. Just to test the situation I went into debian command line tried to ftp the machine that I am on using it's IP address(let's say machine's ip address is 16.1.X.X)

ftp 16.1.X.X

Machine instantly responds saying connected to 16.1.x.x but it takes up to 40 seconds prompting for ftp username and password.

Since I am on the machine I also tried:

ftp 127.0.0.1

it instantly asked for username and password. So it looks like it takes too long to identify 16.1.X.X since there's no dns server.

I tried running ftp -dv 16.1.X.X

Only extra information I am receiving is ftp: setsockopt: bad file descriptor.

I didn't have this problem in my office, so I am suspecting that it has something to do with DNS, any ideas will be greatly appreciated.

I am trying to use dd command to accomplish complete restore of a linux image on a new computer. I have two partitions sda1(main) and sda2(extended), I took a backup of mbr image using:

dd if=/dev/sda of=/mnt/sdb1/mbr_image bs=512 count=1

and dbr image as follows:

dd if=/dev/sda2 of=/mnt/sdb1/ebr_image bs=512 count=1

I also took a backup of main partition(the one that I want to restore) using:

dd if=/dev/sda1 of=/mnt/sdb1/sda1_image

I open the new system with a slax cd and first restore mbr and ebr images that I backed up before(I didn't use 446 bytes, because I want to restore the partition table as well)

dd if=/mnt/sdb1/mbr_image of=/dev/sda
dd if=/mnt/sdb1/ebr_image of=/dev/sda2

after that I restore main partition:

dd if=/mnt/sdb1/sda1_image of=/dev/sda1

once it finishes I resize the main partition using following set of commands:

umount /dev/sda1
e2fsck -f /dev/sda1
resize2fs /dev/sda1 -p

after this point I restart the computer hoping that I restored everything correctly. Unfortunately when I do this on a new computer whose hard drive has never been used before, Computer gets stuck in grub bootloader saying GRUB...

I am suspecting that there's something machine specific in mbr image because if I run the same restore process on the machine that I took back up, everything works fine and machine boots normally.

Can you please shed some light on what I've been doing wrong for the last 2 days...