Re: Eth1 problems again



Hi David Walcroft!

Scanning the thread it sounds like you have a DHCP server set up to
run from Eth1 which is connected by a crossover cable to Eth0, which
sets up to be 192.168.0.1 -- then when Eth1 tries to be 192.168.0.1 it
cannot since that is already taken.

If the above is correct you need to edit your DHCP server config files
to create the network you describe (Eth0 ...2 -- Eth1...1).

As a quick check you might try setting both ports to the separate
fixed addresses and see if ping then works.

The only other thing that occurs to me is that many of the error
messages sound like those I would hear from SELinuix - are you running
a security environment such as SELinux and is it in enforcing mode??!

Good Hunting!

Tod

On 10/3/07, david walcroft <d_j_w46@xxxxxxxxxxxxxx> wrote:
Timothy Murphy wrote:
david walcroft wrote:


Can someone tell how to get over this error please

[david@reddwarf ~]$ sudo service network restart
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: net.ipv4.ip_forward = 0
[ OK ]
SIOCGIFFLAGS: No such device
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0... done.
[ OK ]
Bringing up interface eth1: sysfs class device: Permission denied
Error, some other host already uses address 192.168.0.1.


How do eth0 and eth1 get their IP addresses?
From dhcp?

Eth0 is dhcp,Ethe1 is static 192.168.0.1
What does "ifconfig eth1" say?

[david@reddwarf ~]$ ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:E0:4C:14:1B:09
inet6 addr: fe80::2e0:4cff:fe14:1b09/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:0 txqueuelen:1000
RX bytes:747 (747.0 b) TX bytes:578 (578.0 b)
Interrupt:22 Base address:0x8c00

[david@reddwarf ~]$
What does "route" say?

[david@reddwarf ~]$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
121.208.32.0 * 255.255.248.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 121.208.32.1 0.0.0.0 UG 0 0 0 eth0
[david@reddwarf ~]$
What is in /etc/sysconfig/network-scripts/ifcfg-eth1?

# Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=none
HWADDR=00:e0:4c:14:1b:09
NETMASK=255.255.255.0
IPADDR=192.168.0.1
GATEWAY=192.168.0.0
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes

[david@reddwarf ~]$ sudo ping -c 5 192.168.0.2
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted

What do I do to get ping to work and is it part of this problem overall.
192.168.0.2 is on the other end of my crossover cable

Thanks david







--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list


--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



Relevant Pages

  • Re: simple ping; pinging 101
    ... How are you selecting to ping via eth0 or eth1? ... arrakis can ping caladan from eth0. ...
    (Fedora)
  • Re: Revisted Eth1 problem
    ... tends to also turn the box into a DHCP server. ... Sep 17 11:52:40 reddwarf dhclient: DHCPDISCOVER on eth1 to ... PING 192.168.0.1 56bytes of data. ... ping: sendmsg: Operation not permitted ...
    (Fedora)
  • Re: Revisted Eth1 problem
    ... tends to also turn the box into a DHCP server. ... Sep 17 11:52:40 reddwarf dhclient: DHCPDISCOVER on eth1 to ... PING 192.168.0.1 56bytes of data. ... ping: sendmsg: Operation not permitted ...
    (Fedora)
  • Re: simple ping; pinging 101
    ... arrakis can ping caladan from eth0. ... > arrakis cannot ping caladan from eth1. ...
    (Fedora)
  • Fedora 8 VPN Client for Microsoft PPTP VPN server: routing problem
    ... Seems that the VPN PPTP connection to MS PPTP server is OK as from the ... I tried ping 172.25.9.64 but it hanged up, ... ping: sendmsg: Operation not permitted ...
    (Fedora)