A kdo ve kako v Linuxu skonfigurirat zunanjo mrežo

Torej, moj kabelski provider trdi, da se moje eth0 kartice ne vidi na moji strani modema. Vsi ostali problemi so izključeni, zadevo je treba samo skonfigurirat da se kartica vidi iz modema. Nastavil sem torej eth0=on, IP sem dal zunanjega fiksnega, ki mi ga je določil provider, gateway sem dal standarden 255.255.255.0,
PPP0 deamona sem zaprl.
DHCP je odprt.
Firewalla ni...
Sistem je Red Hat 9 (Clarkconnect) in Linux ni baš moja močna točka.

Bi moral še kaj nastavit, ker po teh nastavitvah naj bi ne delalo? Obstaja kakšna avto varianta kot v Winsih?

Ne vem, ce tisti IP, ki ti ga je dal provider velja za tvojo eth0 kartico. Kot vem, se pri teh zadevah uporablja ppoE, ki pot od kartice do do modema uporablja za ppp tunel.
Tisti IP je merodajen kot IP novega logicnega vmesnika ppp0, ki nastane po vzpostavitvi tunela. O.K., ni nujno da je vedno tako, je pa tako pri meni na ADSLu...

Jaz imam IP na kartici, ki je pristekana na ADSL 192.168.4.1 z NETMASKom 255.255.255.0 , modem si pa sam izbere IP v okvirih tega omrezja, torej 192.168.4.x .
Nato adsl-start skript vzpostavi pppoE link skozi kartico preko modema do DSLAMa in dobim novo "kartico" ppp0, ki ima IP naslov, ki mi ga je dal moj ISP...

Kabelski providerji po mojih izkusnjah navadno dodeljujejo kvazi "dinamicni" IP - torej dodeljen ti je prek DHCPja, ampak dobis vedno isti IP, ker je lockan na MAC adreso tvoje kartice.

V konzoli kot root samo napisi dhclient eth0 in mogu bi dobit vse nastavitve iz DHCP serverja tvojega providerja.

Ce to ne dela (oz. ce imas v naprej dolocen fikesn IP), lahko poskusis naslednje

1. najprej vrzes dol mrezo ifconfig eth0 down (za vsak slucaj, ce nato napises ifconfig, ti mora izpisat samo nastavitve za lo 127.0.0.1)
2. nato dolocis svoji kartici staticen ip ifconfig eth0 xxx.xxx.xxx.xxx
3. nato dolocis gateway route add default gw xxx.xxx.xxx.xxx
4. v filetu /etc/resolv.conf morajo biti napisani DNS serverji (lahko jih je poljubno mnogo, mora pa biti vsaj en) npr.
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx


Se ena zadeva... ce imas dve mrezni kartici v masini, potem moras najti katera je eth0 in katera eth1 Provider mora namrec imeti MAC adreso prave kartice.

Ups, sory... typo Mas prav -- tam bi moralo pisati DNS server... sem popravil :)

trenutno nedelujoče stanje:

LINK ENCAP: ETHERNET HWADDR 00 C0 DF 13 67 OE
INETADDR: 217.72.84.202 BCAST: 217.72.84.202 MASK: 255.255.255.0
UP BROADCAST RUNNING MULTICAST MTV: 1500 METRIC 1
RY PACKETS: 701 NO ERRORS
TY PACKETS: 24 NO ERRORS
COLISSIONS: 0 TXQUELEN: 100
RY BYTES 42060 (41.0 KB) TY BYTES 1440 (1.4KB)
INTERUPT 10 BASE ADDRESS: 0X3000

Videt je, kot da imas broadcast narobe nastavljen. Ta ponavadi ni kar enak IPju kartice, ampak je zadnjih nekaj bitov "1". Ponavadi je broadcast za omrezja klase C enak X.Y.Z.255. Ce pade tvoj naslov v mrezo B klase, potem je broadcast X.Y.255.255. Oboje je lahko res samo, ce ni tvoj ISP razparceliral dan mu obseg stevilk se naprej. Tko na uc bi reku, da si v mrezi tipa C in da bi moral met na koncu 255.
Lahko pa se seveda motim...

Ja, imaš prav, se opravičujem, tisto je tipkarska napaka... BCAST: 217.72.84.255 je prav...

Hm, po nekaj srfanja sem na blef postavil IP na 192.168.100.0 (po nekaterih trditvah auto defolt za tovrstne zunanje mreže), ampak še vedno nič...

Hmm, tole sem našel na netu, če se komu da brati...

Bi lahko imelo vezo z mojim problemom?

topic - @home and just how they decide who gets on their network.

i just spent most of the day at a friend's house pondering over @home's
cable net configuration and trying to get a sketchy idea of how they do
things. any input here would be handy. here's some config info.

Site / Company - Charleston, SC / Comcast @home
Cable modem interface - RCA / Thompson Electronics Model DCM105
Router Box (router)- 486 running LRP w/ 2 3com 509's
Other internal box (box1)- Dual boot w/ LinkSys card
Network Cards - SMC (@home orig.), 3c509 (for router), LinkSys (for box1)

All direct network connections to the cable modem work fine w/ the LinkSys
card in box1, running win98 using DHCP. When router was brought up w/ the
3c509's, w/ eth0 to cablemodem & eth1 to internal, @home's gw would not
reply to a ping, but we would get activity and data lights on the modem.
box1 could talk to router fine on the internal net once configured. Well,
we thought some sort of MAC filtering could be going on, but wait, the
@home people said that any network card could be used, because they send
dhcp info based off the cable modem's MAC. Hmmm.. ok, to test this, we
throw in eth0 from router (3c509) into box1 and boot it dhcp to @home.
Works fine. Okay, but why won't the damn thing work in router? The key -
DHCP. It just so happens @home does use the MAC from your machines
network card, but not for DHCP info. Once you boot a box via dhcp, you
can pull that card, and use it in any other box that boots static. The
only way to get our 3c509 to work in router w/ @home was to throw the card
in box1, boot w/ dhcp, test the net connect, pull the card, throw it back
in router, then all works fine.

Conclusion:
From what i've gathered is that @home performs some type of MAC testing
down the line to see who's who, but what i don't know yet is where this
happens. My guess is either in the cable modem itself, or in the gateway.
But, if it was in the cable modem, then why is it showing cable activity
when i ping? A solution would be to ping someone else on the same
segment, but we didn't know anyone else, and windows boxes (which i'm sure
most @home machines consist of) don't reply to broadcast pings. Also, if
@home's dhcp server replies w/ respect to the cable modem's MAC, then
where is your machine's MAC getting recorded for the filtering to take
place? If this is in the modem, then oh boy think of the fun you could
have. I have a strong feeling that there is some way to remote manage the
cable modem, but have yet to find specs (haven't really looked yet
either). If anyone has some info on cable modem standards, or equipment
specific info, i would appreciate it.

Bottom line comment: To get a network card to work w/ @home, you need to
"initialize" the card first w/ them via dhcp.

Ekola zrihtal. Sedaj dela tako notranja kot zunanja...