[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Re: network issues



Norbert,
	top post first: "What the ..."

On Tue, 2 Dec 2003, norbert wrote:
> My external interface is eth1 & internal eth0, hmm I guess that I'll owe
> you a drink or two at LinuxWorld ..... ;-)     ... next ...
> norbert
>
> julius turtle com wrote:
> >On Tue, 2 Dec 2003, norbert wrote:
> >>K12LTSP Server V3.1.2 with all current updates
> >>Two 10/100 NICs
> >>SMC2-1211TX  connected to a cable-modem for internet (DHCP) - eth1
> >>RTL-8139 local lan (Static) - eth0
> >>no firewall
> >>route with gateway via eth0
> >>
> >>Problem:
> >>When I let kudzu & neat configure the cards neither work.
> >>
> >>Actions
> >>Restart the server without kudzu
> >>Use neat to define the two NIC cards
> >>Activate only the SMC2 for internet
> >>Save & exit
> >>Internet works !
> >>manually configure the RTL8139 - ifconfig eth0 192.168.0.130 up
> >>both work
> >>
> >>Restart the network - service network restart
> >>Neither work - no ping, no internet !!!!!
> >>
> >>Yes I know you said my first mistake was playing with the network, so I
> >>re-installed everything from scratch but I did run apt-get update &
> >>apt-get upgrade :-(
> >>
> >>Prior to having the updates/upgrade the system worked but since then
> >>NOTHING WORKS !!!!!!
> >>
> >>
> >
> >Norbert,
> >    first things first: make your eth1 the dhcp interface to the
> >world, and have eth0 as the internal network gateway. this is actually
> >important, because the dhp setup will try to put all the dns and default
> >gateway info for the server. you don't have to mess with cards or even
> >files - if neccessary just change the assignment in /etc/modules.conf.
> >after you do that, reboot and see if all is forgiven ;-)

now bottom post. why is the eth0 set at 192.168.0.130? are you subnetting
the natted network? more important: why is thge gateway set to eth0? this
alone will cause the network traffic to the outside to stop.
	try the default, you don't have to use neat, you can edit files by
hand: /etc/sysconfig/networks/devices/ifcfg-eth?and
/etc/sysconfig/network/scripts/ifcfg-eth?, btw, those files should be
linked, but if they are not, don't worry, just make sure that they have
same contents.
ifcfg-eth0 should contain something like:
DEVICE='eth0'
BOOTPROTO='none'
BROADCAST='192.168.0.255'
IPADDR='192.168.0.254'
NETMASK='255.255.255.0'
NETWORK='192.168.0.0'
ONBOOT='yes'
TYPE='Ethernet'
USERCTL='no'

ifcfg-eth1 should look like this:
DEVICE='eth1'
BOOTPROTO='dhcp'
ONBOOT='yes'
TYPE='Ethernet'
USERCTL='no'

after editing the files, do:
ifdown eth0; ifdown eth1; ifup eth0; ifup eth1
run: netstat -r, see that the default is pointing to eth1! in my case:
default         webramph.turtle 0.0.0.0         UG        0 0     0 eth1

try to ping outside world from the server. all might be forgiven ;-)

as one of the inventors of 802.11 told me: "Networks are tricky."
julius

p.s. did somebody mention drinkies? designated driver, anybody?




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]