At 07:33 AM 1/23/2004 +0100, pa3gcu wrote:
On Friday 23 January 2004 05:04, Beolach wrote:
> chuck wrote:
> > [snip]
> >
> > OBTW, when I
> >
> > ping -I eth0 192.168.1.1
> > ping: bad interface address 'eth0'
> >
> > is what I get. I do have an eth0 device. :-|
>
> The -I option doesn't tak
Hi, Beolach:
I tried the same thing that Devesh quoted.
I was not stating that the command line was
'configured correctly'. ;-)
Chuck
Beolach wrote:
>
> chuck wrote:
> > [snip]
> >
> > OBTW, when I
> >
> > ping -I eth0 192.168.1.1
> > ping: bad interface address 'eth0'
> >
> > is what I get.
On Friday 23 January 2004 05:04, Beolach wrote:
> chuck wrote:
> > [snip]
> >
> > OBTW, when I
> >
> > ping -I eth0 192.168.1.1
> > ping: bad interface address 'eth0'
> >
> > is what I get. I do have an eth0 device. :-|
>
> The -I option doesn't take an interface name (ie eth0), but rather t
chuck wrote:
[snip]
OBTW, when I
ping -I eth0 192.168.1.1
ping: bad interface address 'eth0'
is what I get. I do have an eth0 device. :-|
The -I option doesn't take an interface name (ie eth0), but rather the
IP address (ie 192.168.0.1) assigned to the interface.
Conway S. Smith
-
To
Hi, Devesh:
I think 'destination host unreachable' is a routing problem.
I think that then no packets are transmitted.
If true, ping would not run and there is no ping failure.
I think we are done with your original problem of 'ping' failure.
I am guessing, because you never reported the outpu
]
Subject: Re: 2 NIC cards not talking
Hi, Beolach:
Thanks.
I asked, but Chadha never reported his (exact) 'ping' usage, nor the (exact)
error message. :-| Chuck
Beolach wrote:
>
> ping has a -I option that allows you to specify the source interface.
> I haven't used t
Hi, Beolach:
Thanks.
I asked, but Chadha never reported his (exact) 'ping' usage,
nor the (exact) error message.
:-|
Chuck
Beolach wrote:
>
> ping has a -I option that allows you to specify the source interface. I
> haven't used this option myself, but I would guess Chadha used some
> thing like
]
Subject: Re: 2 NIC cards not talking
Oops. I just tried it, and it doesn't take an interface name (eth0),
but rather, the IP address for the interface. So instead of
ping -I eth0 192.168.1.1
it would be
ping -I xxx.xxx.xxx.xxx 192.168.1.1
Where xxx.xxx.xxx.xxx is the IP address of eth0.
Be
From what you wrote, I'd guess that you have not set up iptables to NAT
the LAN hosts. I'm afraid that what you posted did not answer this
definitively, but that was my fault; I asked for incomplete information
about iptables. NAT'ing is done not in the default (filter) table that
"iptables -nv
ping has a -I option that allows you to specify the source interface. I
haven't used this option myself, but I would guess Chadha used some
thing like this: 'ping -I eth0 192.168.1.1'.
Conway S. Smith
chuck wrote:
Dear Chadha:
In (4.) & (5.)...
I know how to ping from a host with an 'eth0' o
Oops. I just tried it, and it doesn't take an interface name (eth0),
but rather, the IP address for the interface. So instead of
ping -I eth0 192.168.1.1
it would be
ping -I xxx.xxx.xxx.xxx 192.168.1.1
Where xxx.xxx.xxx.xxx is the IP address of eth0.
Beolach wrote:
ping has a -I option that
Dear Chadha:
In (4.) & (5.)...
I know how to ping from a host with an 'eth0' or 'eth1' device.
I do not know how to ping from 'eth0' or from 'eth1'.
Sorry, I cannot help.
Chuck
"Chadha, Devesh" wrote:
> 4.Pinging 192.168.1.1 from eth0 gave destnation host unreachable and pinging
> xxx.xxx.x
It looks to me like you're iptables haven't been setup to NAT. I have
attached the output of 'iptables -nvL' on my NATing gateway. Just for
the heck of it I obscured my public address too. I used a slightly
modified version of the rc.firewall-stronger startup script from the
IP-Masquerade HO
esday, January 21, 2004 8:35 PM
To: [EMAIL PROTECTED]
Subject: RE: 2 NIC cards not talking
At 07:32 PM 1/21/2004 -0500, Chadha, Devesh wrote:
>Well my reason for not giving is that it is a public IP and does not have
>any firewalls in place. This exposes my server much more to unauthori
need to see the
output of
iptables -nvL
-Original Message-
From: Ray Olszewski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 7:02 PM
To: [EMAIL PROTECTED]
Subject: RE: 2 NIC cards not talking
At 04:52 PM 1/21/2004 -0500, Chadha, Devesh wrote:
>[...]
>Ray:
>I have sta
Hi, Chadha:
Originally, you said:
> I have a linux box with 2 NIC cards, both are properly configured.
> Both are on the same subnet, but still don't ping to one another!!
You do not show how you attempt the 'ping',
nor the error message.
Please show exact ping command attempt.
I was hoping f
that eth0, eth1 and lo are correctly configured.
ip_forward gives a "1"
What do the gurus say???
-Original Message-
From: Ray Olszewski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 7:02 PM
To: [EMAIL PROTECTED]
Subject: RE: 2 NIC cards not talking
At 04:52 PM 1/2
At 04:52 PM 1/21/2004 -0500, Chadha, Devesh wrote:
[...]
Ray:
I have static IP and therefore I cannot give the actual IP address.
I don't understand why, unless for some reason you think that your IP
address is a secret. Once you start using the address for any purpose, it
will be known to everyo
Hello, Chadha:
You do not show how you attempt the 'ping',
nor the error message.
Please show exact ping command attempt.
Please show output of 'netstat -r -n'.
Both cards (should not, cannot) be on the same subnet
for the 'firewall/router' to function. The 'firewall/router'
should show a rou
onvenience.
Regards,
Devesh
-Original Message-
From: chuck gelm net [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 4:45 PM
To: Chadha, Devesh
Cc: '[EMAIL PROTECTED]'
Subject: Re: 2 NIC cards not talking
Hello, Chadha:
You do not show how you attempt the &
is
baloney nonetheless, and you and your employer need to understand that it
is made meaningless by the act of you sending the message to a mailing list.
-Original Message-
From: Juan Facundo Suárez [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 10:13 AM
To: linux-newbie list
S
your solution after I reach home and get back to you tomorrow.
Regards,
Devesh
-Original Message-
From: pa3gcu [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 11:38 AM
To: Chadha, Devesh; linux-newbie list
Subject: Re: 2 NIC cards not talking
On Wednesday 21 January 2004
7;Juan Facundo Suárez'" <[EMAIL PROTECTED]>; "linux-newbie
list" <[EMAIL PROTECTED]>
Sent: Wednesday, January 21, 2004 12:23 PM
Subject: RE: 2 NIC cards not talking
| Juan,
|
| Eth0 has the external assigned IP by my ISP. Eth1 has a 192.168.x.x ip
| address. Eth1 ac
On Wednesday 21 January 2004 16:23, Chadha, Devesh wrote:
> Juan,
>
> Eth0 has the external assigned IP by my ISP. Eth1 has a 192.168.x.x ip
> address. Eth1 acts as the DHCP server for my LAN. My LAN is working fine. I
> can connect machines to the LAN and even connect one machine to another.
>
> B
internet nor connect to any internal machine from outside!!
Do I need to bridge the 2 NICs ???
Regards,
Devesh
-Original Message-
From: Juan Facundo Suárez [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 10:13 AM
To: linux-newbie list
Subject: Re: 2 NIC cards not talking
er: [EMAIL PROTECTED]
[EMAIL PROTECTED]
- Original Message -
From: "Chadha, Devesh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 21, 2004 11:25 AM
Subject: 2 NIC cards not talking
| Hi,
|
| I have a linux box with 2 NIC cards, both are properly
Hi,
I have a linux box with 2 NIC cards, both are properly configured. Both are
on the same subnet, but still don't ping to one another!!
I need to setup the box as the firewall/router that has eth0 set as external
and eth1 as internal serving as DHCP server to other computers on the
network. Bot
27 matches
Mail list logo
