I am now pinging between the nodes. This seems to be going OK, apart from the fact that the dialup (ppp) below is actually not working... strange but true! All is well until I bring the other machine up and then all of a sudden the net connection goes. I then disconnect from the internet, because even though it says im connected it won't communicate, and try and reconnect. Kppp will connect me and log me on but won't get me anywhere. !
I have just clicked. The default route is being set to 192.168.0.1 sending me to me. I changed the default to paradise and it worked. I could both ping and access the internet. Now the question is - how do I set this so I don't have to go in and manually configure the routing table every time? There doesn't seem to be anything in the control centre...
I suppose the next question is how do I set up a proxy? The control centre just has two lines, and I can't work out what to put in there to "make a proxy". Any suggestions more than welcome.
Cheers
Anton


[EMAIL PROTECTED] antonovich]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:05:1C:19:CF:12
         inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:9 errors:0 dropped:0 overruns:0 frame:0
         TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:1538 (1.5 Kb)  TX bytes:3574 (3.4 Kb)
         Interrupt:18 Base address:0x9f00

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:135 errors:0 dropped:0 overruns:0 frame:0
         TX packets:135 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:8870 (8.6 Kb)  TX bytes:8870 (8.6 Kb)

ppp0      Link encap:Point-to-Point Protocol
         inet addr:210.246.27.93  P-t-P:202.0.46.83  Mask:255.255.255.255
         UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1524  Metric:1
         RX packets:32 errors:1 dropped:0 overruns:0 frame:0
         TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:3
         RX bytes:1739 (1.6 Kb)  TX bytes:1033 (1.0 Kb)


[EMAIL PROTECTED] antonovich]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
202.0.46.83 * 255.255.255.255 UH 0 0 0 ppp0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
192.168.136.0 * 255.255.255.0 U 0 0 0 vmnet8
172.16.140.0 * 255.255.255.0 U 0 0 0 vmnet1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
[EMAIL PROTECTED] antonovich]#
Nick Rout wrote:


On Sun, 28 Sep 2003 18:44:19 +1200
Anton <[EMAIL PROTECTED]> wrote:



hi
below you will find the outputs from ifconfig and route. Sorry if I
was unclear, its pretty hard for a newbie to know what is and isnt' important...



cool, no sweat.




I have been playing around and the eth0:9 entry has now appeared. I have been having problems accessing the net since playing around but the good ol' restart seems to do wonders :-). The sit as it
stands is. Machine A has XP - mandrake 9.1 dual boot and is access pt
to net (the IP it was being assigned before was 192.168.1.1, but now i
don't know, below is different). Other machine is ME and has ip 198.168.0.163. It is working perfectly between XP and ME, i.e., file access to both machines from both machines and access from both
machines to net via the XP machine. 'dose pretty much took care of
everything. The hardware is OK. I tried using the Mandrake control
centre to get things working... and tried assigning the mdk machine
192.168.0.1 to get it on the same subnet (both seem to have 24 bit
masks). Unfortunately, things seem to have got a little complicated
and it didn't like me assigning an address statically. No pinging
seems to be possible, but that is not surprising, as I wouldn't have a
clue how to edit the routing table (its obviously no going anywhere
with those entries)!. I hope this is a little more informative.
Cheers
Anton


[EMAIL PROTECTED] antonovich]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:05:1C:19:CF:12
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:29 errors:0 dropped:0 overruns:0 frame:0
         TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:2225 (2.1 Kb)  TX bytes:9276 (9.0 Kb)
         Interrupt:18 Base address:0x9f00




eth0 (ethernet) has no IP address at all. use the mandrake tool to set it to something on the same subnet as the ME machine. you should then be able to ping the ME machine.



eth0:9 Link encap:Ethernet HWaddr 00:05:1C:19:CF:12
inet addr:169.254.157.231 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:18 Base address:0x9f00





I think this address has been set because eth0 could not get an IP address. the 169.254 netblock is a "dummy" address for machines that can't autoconfigure an ip address (either from dhcp or from domething preset)




lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:133 errors:0 dropped:0 overruns:0 frame:0
         TX packets:133 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:8718 (8.5 Kb)  TX bytes:8718 (8.5 Kb)

ppp0 Link encap:Point-to-Point Protocol
inet addr:210.246.27.13 P-t-P:202.0.46.83 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1524 Metric:1 RX packets:172 errors:1 dropped:0
overruns:0 frame:0 TX packets:159 errors:0 dropped:0
overruns:0 carrier:0 collisions:0 txqueuelen:3
RX bytes:81722 (79.8 Kb) TX bytes:14044 (13.7 Kb)


vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.140.1 Bcast:172.16.140.255 Mask:255.255.255.0 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:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:192.168.136.1 Bcast:192.168.136.255 Mask:255.255.255.0 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:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


[EMAIL PROTECTED] antonovich]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
202-0-46-83.par * 255.255.255.255 UH 0 0 0 ppp0 192.168.136.0 * 255.255.255.0 U 0 0 0 vmnet8
172.16.140.0 * 255.255.255.0 U 0 0 0 vmnet1
169.254.0.0 * 255.255.0.0 U 0 0




this route is as a result of eth0:9 (see comment above). report back
if/when you manage to get eth0 with an ip address and pinging the ME
machine :-)





0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 202-0-46-83.par 0.0.0.0 UG 0 0 0 ppp0


Nick Rout wrote:



On Sun, 28 Sep 2003 13:18:21 +1200
Anton <[EMAIL PROTECTED]> wrote:





Things seem to be hunky dory from the XP boot (accessing the other
winME machine) so I'm pretty sure things are working ok. The card is
recognised and seems to be installed properly. (Sorry, but I'm just starting...) What now? I would like to have the 'net connection from
(xp + mandrake9.1 on the box) linux so my wife can connect to the
internet with her ME via me (sorry, that was bad :-). It's a std
10/100 to 10/100 enet with UTP in between. Any suggestions on where


to>start? Easiest options first please!


Cheers
Anton
ps I would love to rid my home of ME, but the wife would skin me if


I >put Linux on her box... she isn't a devotee yet... :-)






your question is pretty unclear, its hard to get people to help if
you cannot write clearly about your setup and problem.

I THINK from your question that you have a winxp/linux dual boot
machine (A) which will connect to the net and which in xp will
connect to the ME computer (B). You want to be able to connect to the
net from the ME machine.

OK when A is in linux, what is its LAN IP address?

what is the win ME machines IP address?

can you ping from A to B or from B to A?

if you can't then you fundamentally need to get your LAN set up
before you can consider sharing the internet.

As the B machine obviously has networking sorted, I suggect you work
on the A. How did you set up the network card in linux and what are
the results of the following commands (you may need to be root)

ifconfig
route


Report back and we will try to help :-)






















Reply via email to