On Mon, 25 May 2009 08:37:33 +1200
Chris Bannister wrote:
> On Fri, May 22, 2009 at 09:25:29AM -0700, Frank Miles wrote:
> > I recently added a second networking card to a hardware-test PC. This
> > elderly machine
> > had been working reasonably well. The second networking card is for eth1,
Thanks, Adrian. I was sure that it wasn't just the firewall at this
point - that it was necessary to kill eth1 to get eth0 fully functional.
I was wrong.
This is now just a firewall problem. And this is a "handcrafted" beast,
with lotsa rules. I wouldn't dream (well, not yet anyway) of asking
2009/5/28 Frank Miles :
> Regrettably, the problem persists - though possibly with a different
> threshold of sorts, as pinging now seems to work. However-
> apt-get update
> still hangs. I have to kill BOTH the firewall and eth1 in order to
> make this work (not seeming to wait indefinite
Following up, particularly on Adrian Levi's suggestion to eliminate
the gateway spec in /etc/network/interfaces:
Thanks, Adrian! Your idea makes sense. Trying it: it changes the
routing table exactly as you described, causing my routing table to
match yours (excepting, of course, the specific I
2009/5/27 Frank Miles :
> Sure, can provide more info...
>
> /etc/network/interfaces :
>
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> auto eth0
> #iface eth0 inet dhcp
> iface eth0 inet static
> address xxx.yyy.zzz.32
> network xxx.yyy.zzz.0
>
On Tue, 26 May 2009 18:20:07 +0200, Frank Miles wrote:
> Sure, can provide more info...
>
> /etc/network/interfaces :
>
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> auto eth0
> #iface eth0 inet dhcp
> iface eth0 inet static
> address xxx.yyy.zzz
Sure, can provide more info...
/etc/network/interfaces :
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
#iface eth0 inet dhcp
iface eth0 inet static
address xxx.yyy.zzz.32
network xxx.yyy.zzz.0
netmask 255.255.255.0
broadcas
Do you have network-manager installed? It's not very good with setups
with mixed static/dynamic ips. If you've got network-manager, remove
it and set things up manually.
Regards,
Daniel
--
And that's my crabbing done for the day. Got it out of the way early,
now I have the rest of the after
On Fri, May 22, 2009 at 09:25:29AM -0700, Frank Miles wrote:
I recently added a second networking card to a hardware-test PC. This elderly
machine had been working reasonably well. The second networking card is for
eth1, etc., and /sbin/ifconfig shows things as properly connected, with eth0
b
Andrei Popescu wrote:
On Fri,22.May.09, 09:25:29, Frank Miles wrote:
[snip troubles with two network cards]
Please provide your /etc/network/interfaces
And also add the output of 'route'. It seems to me that somehow all
traffic is routed via eth1, instead of only 192.x.x.x.
Sjoerd
signatu
On Fri, May 22, 2009 at 09:25:29AM -0700, Frank Miles wrote:
> I recently added a second networking card to a hardware-test PC. This
> elderly machine
> had been working reasonably well. The second networking card is for eth1,
> etc., and
> /sbin/ifconfig shows things as properly connected, wit
On Fri,22.May.09, 09:25:29, Frank Miles wrote:
[snip troubles with two network cards]
Please provide your /etc/network/interfaces
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
signature.asc
Description: Digital signature
I recently added a second networking card to a hardware-test PC. This elderly
machine
had been working reasonably well. The second networking card is for eth1,
etc., and
/sbin/ifconfig shows things as properly connected, with eth0 being the outside
interface
and eth1 being an internal 192.168
13 matches
Mail list logo
