[plug] adsl trouble

[Richard]

On Sat, 2002-06-15 at 21:26, Craig Ringer wrote:
> > I have
> > two network cards (eth0, eth1) in my box (setup as DHCP clients)
> Both enabled and plugged in at the same time? this might confuse your 
> router (it thinks they're 2 different machines unless it supports some 
> kind of trunking or your switch (if not embedded in the router) does).

Sorry it's taken me a day to respond to the help offered on this one
(I've had a little email trouble...unrelated :) I have got it set up at
the moment not to bring up eth0 (I want to use eth1 for the Internet) on
boot up, just eth1. Eth0 has a static ip and eth1 is set to use DHCP.
How can I disable eth0 completely for the purposes of testing? I did
want to run another workstation off this linux box through eth0 at some
stage. Would it be better to swap the card slots around so the Internet
comes in through eth0, or is this not an issue?
 
> > and
> > have tried using both, with the same result...the connection seems to
> > come up fine when I boot, but after a couple of minutes it seems to die
> > for no apparent reason.
> Perhaps DHCP allocations change if its being confused by 2 NICs?
> Can you still ping other machines on your LAN? Try using ifconfig -a to 
> get the status on the interfaces too see if perhaps they're going down 
> on dhcpcd/pump's request due to maybe a DHCP NACK from the router?

This is the results of ifconfig -a

[root at Main700 scripts]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:BA:BB:F6:7A
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:7 dropped:0 overruns:0 carrier:14
          collisions:119 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:420 (420.0 b)
          Interrupt:9 Base address:0xcf80

eth1      Link encap:Ethernet  HWaddr 00:50:FC:5D:B5:92
          inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:323 errors:0 dropped:0 overruns:0 frame:0
          TX packets:357 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:44073 (43.0 Kb)  TX bytes:27060 (26.4 Kb)
          Interrupt:11 Base address:0xc00

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:302 errors:0 dropped:0 overruns:0 frame:0
          TX packets:302 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:25771 (25.1 Kb)  TX bytes:25771 (25.1 Kb)

[root at Main700 scripts]#


> > I can easily get it back again using /sbin/ifup
> > eth0 or 1, but after a few minutes or more the same thing happens again.
> Have you tried "tail -f /var/log/syslog" or "tail -f /var/log/messages" 
> and watching what the system is saying esp around the dropout time?

This is a snippet from last nights syslog, and it goes on like this for
quite a while. Could someone possibly tell me what martian source means?


Jun 15 14:12:52 Main700 dhcpcd[6354]: dhcpConfig: ioctl SIOCADDRT: File
exists
Jun 15 14:26:36 Main700 kernel: martian source 192.168.0.4 from
192.168.0.1, on dev eth1
Jun 15 14:26:36 Main700 kernel: ll header:
ff:ff:ff:ff:ff:ff:00:50:ba:92:dd:63:08:06
Jun 15 14:26:46 Main700 kernel: martian source 192.168.0.4 from
192.168.0.1, on dev eth1
Jun 15 14:26:46 Main700 kernel: ll header:
ff:ff:ff:ff:ff:ff:00:50:ba:92:dd:63:08:06
Jun 15 14:26:56 Main700 kernel: martian source 192.168.0.4 from
192.168.0.1, on dev eth1
Jun 15 14:26:56 Main700 kernel: ll header:
ff:ff:ff:ff:ff:ff:00:50:ba:92:dd:63:08:06
Jun 15 14:27:06 Main700 kernel: martian source 192.168.0.4 from
192.168.0.1, on dev eth1
Jun 15 14:27:06 Main700 kernel: ll header:
ff:ff:ff:ff:ff:ff:00:50:ba:92:dd:63:08:06
Jun 15 14:31:36 Main700 kernel: martian source 192.168.0.4 from
192.168.0.1, on dev eth1
Jun 15 14:31:36 Main700 kernel: ll header:
ff:ff:ff:ff:ff:ff:00:50:ba:92:dd:63:08:06
Jun 15 14:31:46 Main700 kernel: martian source 192.168.0.4 from
192.168.0.1, on dev eth1
Jun 15 14:31:46 Main700 kernel: ll header:
ff:ff:ff:ff:ff:ff:00:50:ba:92:dd:63:08:06
Jun 15 14:31:56 Main700 kernel: martian source 192.168.0.4 from
192.168.0.1, on dev eth1

> Not much info to go on unfortunately. Do the ifaces actually go down,
> or just stop sending packets? Can you still ping other machines on the
> LAN after connectivity to the internet is lost? Have you looked 
through the system logs for indications on what might be wrong?

Eth1 does not actually seem to go down, it just stops sending packets.

The syslog file continues like this for over an hour till I shut down.
It obviously looks like something is wrong here, but being a bit of a
newbie I have no idea what it all means. If anyone could offer some
advice I would be grateful.