Networking with Firewall Router

[rob hawkes]

I am trying to connect a PC running Fedora Core 4 to a netgear DG834 ADSL Firewall Router. I get an error message when trying to activate eth0 - Using the Network device control GUI it fails when trying to determine IP information for eth0. I have set eth0 to DHCP but I notice that when examine /sbin/ifconfig I get no inet addr: just an inet6 sddr:

Presumabably this is an ipv6 vs ipv4 problem? Any suggestions would be helpful. Thanks in advance.

/sbin/ifconfig

eth0 Link encap:Ethernet HWaddr 00:02:B3:B8:94:60
inet6 addr: fe80::202:b3ff:feb8:9460/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 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)

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:2776 errors:0 dropped:0 overruns:0 frame:0
TX packets:2776 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3430670 (3.2 MiB) TX bytes:3430670 (3.2 MiB)

[moulsonp]

Could you give us a little more information. What is the specific error message you get? What happens if you do 'ifconfig eth0 up' and then 'dhclient eth0' ?

[w5set]

Is the DHCP "server" turned on in the Netgear Router?

[rob hawkes]

Originally Posted by moulsonp

Could you give us a little more information. What is the specific error message you get? What happens if you do 'ifconfig eth0 up' and then 'dhclient eth0' ?

The DG834 is configured for DHCP. RedHat 9 worked ok using another PC and this PC works with Windows (another disc). So I think its the settings for Fedora core 4 and something to do with IPv6? The output of ifconfig eth0 up and dhclient eth0 are as below. the error message is 'Cannot activate network device eth0' when using the Network Device Contral GUI. Thanks.


[root@localhost ~]# ifconfig eth0 up
[root@localhost ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:02:B3:B8:94:60
inet6 addr: fe80::202:b3ff:feb8:9460/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 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)

[root@localhost ~]# dhclient eth0
Internet Systems Consortium DHCP Client V3.0.2
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth0/00:02:b3:b8:94:60
Sending on LPF/eth0/00:02:b3:b8:94:60
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[capnlinux]

It's not an IPV6 problem. That IPV6 address shows up in FC4 by default. It's not important. What is important is that your interface is not really up. Note the 0 packet counts. Do you get link lights at the physical interface level? Is your cable good? This looks to me like a layer 1 problem (Physical Interface)

[rob hawkes]

It appears that the physical link is OK as the lights work ( 100TX stays on and ACT/LNK blinks during attempts to activate eth0 ) and the same PC communicates just fine when using Windows 2000 using an alternate hard disc drive. The reason I thought it might be IPv6 was that in the mini-HOWTO ( IPv6 on Fedora Core mini-HOWTO ) the output of ifconfig eth0 includes a line like

inet addr:..... as well as
inet6 addr:....

Any more suggestions? - thanks for the comments so far....

[capnlinux]

Yeah, That inet6 addr:... thing sent me on a wild goose chase before also.

OK, Now we are getting methodical here. You've eliminated the physical layer by dual booting to Windows and proving the hardware there.

So let's eliminate the device drivers next. It really doesn't look like they are working. This is based on the ifconfig showing absolutely no packets received or transmitted. If you do the ifconfig after the dhclient eth0 exchange there should be some packet activity if you are indeed talking to your hub/switch. There should have been some traffic even just starting the interface (an arp insertion sequence, etc.) and broadcast packets are present on all but the most trivial ethernet LAN's.

Try changing the interface to static addressing temporarily and see if you can ping your gateway.

[prathimaramesh]

Dear All,

I want to use fire walled proxy server.How to Create a Proxy Server in fedora Core2 and how to configure the proxy IPs in Windows and Linux Machines. Please give me the reply.

[gavinw6662]

Originally Posted by capnlinux

Yeah, That inet6 addr:... thing sent me on a wild goose chase before also.

OK, Now we are getting methodical here. You've eliminated the physical layer by dual booting to Windows and proving the hardware there.

So let's eliminate the device drivers next. It really doesn't look like they are working. This is based on the ifconfig showing absolutely no packets received or transmitted. If you do the ifconfig after the dhclient eth0 exchange there should be some packet activity if you are indeed talking to your hub/switch. There should have been some traffic even just starting the interface (an arp insertion sequence, etc.) and broadcast packets are present on all but the most trivial ethernet LAN's.

Try changing the interface to static addressing temporarily and see if you can ping your gateway.

have you looked at your /etc/sysconfig/network-scripts/ifcfg-eth0 file??

can you post up what that says?? If your router is set to dhcp, and the computer is set to dhcp - then you should get a connection. Have you tried to restart the network services after making changes??

service network restart

also - i heard you think it is getting link, you can check that with a command:

mii-tool or
ethtool eth0

[rob hawkes]

Dear All,
Thanks for all the help and I apologise for the delay in replying but the solution to my problem was to install Debian! Worked out of the box! In any event - thank you for all the interest taken and perhaps I needed a system that was all ready up and working......
Regards,
Rob

[Zotter]

Ah Rob, you see - that's not a solution. You just avoided the problem.

The problem still exists and now we've no way to know what's up one way or the other.

Glad you got a system working - but, now we all wonder if there's a problem someplace and no sure way to fix it, let alone identify it.


Feel'n guilty yet? shouldn't be :up: - your box works

[C0USTEAU]

Hi guys, I'm having the same issue with a DG834GT NetGear firewall/modem/router and FC4.

The router works with a different xp box, ip address etc... are detected, but no luck with Fedora using DHCP or setting the details manually.

Here are some of the details:
[root@localhost ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:13:46:30:6f:16
ONBOOT=yes
TYPE=Ethernet
DHCP_HOSTNAME=fedora_box
USERCTL=yes
PEERDNS=yes
IPV6INIT=yes

[root@localhost ~]# ifconfig eth0 up
[root@localhost ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:13:46:30:6F:16
inet6 addr: fe80::213:46ff:fe30:6f16/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:86 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11

[root@localhost ~]# dhclient eth0
Internet Systems Consortium DHCP Client V3.0.2
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth0/00:13:46:30:6f:16
Sending on LPF/eth0/00:13:46:30:6f:16
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[root@localhost ~]# service network start
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0... failed. [FAILED]

Any help would be appreciated, slán.
Feargal

[C0USTEAU]

Also tried setting the IP details manually, see below:

[root@localhost ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:13:46:30:6f:16
ONBOOT=yes
TYPE=Ethernet
DHCP_HOSTNAME=fedora_box
USERCTL=yes
PEERDNS=yes
IPV6INIT=yes
IPADDR=192.168.0.3
NETMASK=255.255.255.0
GATEWAY=192.168.0.1

[root@localhost ~]# service network start
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]

[root@localhost ~]# service network start
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]

[root@localhost ~]# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.3 icmp_seq=1 Destination Host Unreachable
From 192.168.0.3 icmp_seq=2 Destination Host Unreachable
From 192.168.0.3 icmp_seq=3 Destination Host Unreachable

--- 192.168.0.1 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5000ms
, pipe 4

Please help me, geting desperate!!!!!

[gavinw6662]

delete the ipv6 line....

[C0USTEAU]

Originally Posted by gavinw6662

delete the ipv6 line....

Tried it, no luck, any other ideas??