Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: networking trouble
- To: tlug@example.com
- Subject: Re: networking trouble
- From: B0Ti <9915104t@example.com>
- Date: Sat, 26 May 2001 12:27:14 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- Organization: Kobe University, Japan
- References: <3B0DEE65.3B255773@example.com> <20010525144314.A30956@example.com> <3B0DFB06.7CB463FD@example.com> <20010525153130.B30956@example.com> <3B0E0929.DC292FA0@example.com> <20010525171435.E30956@example.com> <3B0E20F6.2C15BCC2@example.com> <20010525190135.B5613@example.com> <3B0E34AC.244A32B6@example.com> <20010525195629.D5613@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <fWagaD.A.dTG.SAyD7@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: boti
Thomas O'Dowd wrote: > Hmmm? So to get things straight... > > Here is my understanding of your prob: > V is on the L right. Vmware is running on Desktop! ifconfig on Desktop: eth0 Link encap:Ethernet HWaddr 00:90:CC:08:6D:9A inet addr:192.168.1.83 Bcast:192.168.1.255 Mask:255.255.255.0 vmnet1 Link encap:Ethernet HWaddr 00:50:56:01:00:00 inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0 > (D refers to Desktop internal address) > > D ping L? yep? > D ping V? yep? > L ping D? yep? > L ping V? yep? > V ping L? yep? > V ping D? Nope? exactly. > If it's like that then perhaps there is a firewall running on D which > stops incoming ping from the internal interface except from L's IP??? > Try looking at ipchains -L or iptables -L on your desktop? I tried some of the iptable rules ASZ suggested earlier. [root@example.com boti]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT icmp -- 192.168.1.0/24 anywhere ACCEPT tcp -- 192.168.1.0/24 anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- 192.168.1.0/24 anywhere ACCEPT all -- anywhere 192.168.1.0/24 Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT icmp -- anywhere 192.168.1.0/24 ACCEPT tcp -- anywhere 192.168.1.0/24 ACCEPT icmp -- anywhere 192.168.1.0/24 > Try also looking at the arp tables on the desktop and vmware... /sbin/arp -a > should show up the relevant ip addresses if the ping is getting through. arp -a on Desktop: ? (192.168.1.254) at 00:00:F4:74:B1:7E [ether] on eth0 (This is the gateway of the ISP) Laptop (192.168.1.10) at 08:00:46:05:63:69 [ether] on eth0 Shouldn't vmware show up here ? arp on Laptop: Address HWtype HWaddress Flags Mask Iface192.168.1.11 ether 00:50:56:85:00:01 C eth0 (This is vmware) Desktop ether 00:90:CC:08:6D:9A C eth0 When I ping Laptop from Vmware, packets travel like this, if i'm not mistaken: vmnet1@example.com>eth0@example.com>eth0@example.com Pinging Desktop from Vmware is just the first part of this, and I still don't have a clue why it's not getting there. I have mandrake running on vmware also besides winsuxx95, i will try that next. BTW, what ethernet driver in the kernel supports vmware ? B0Ti.
- References:
- networking trouble
- From: B0Ti <9915104t@example.com>
- Re: networking trouble
- From: Jonathan Q <jq@example.com>
- Re: networking trouble
- From: B0Ti <9915104t@example.com>
- Re: networking trouble
- From: Jonathan Q <jq@example.com>
- Re: networking trouble
- From: B0Ti <9915104t@example.com>
- Re: networking trouble
- From: Jonathan Q <jq@example.com>
- Re: networking trouble
- From: B0Ti <9915104t@example.com>
- Re: networking trouble
- From: "Thomas O'Dowd" <tom@example.com>
- Re: networking trouble
- From: B0Ti <9915104t@example.com>
- Re: networking trouble
- From: "Thomas O'Dowd" <tom@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: Further horrors of 'ksysv' [FTP login failure]
- Next by Date: Linux drivers for Fujitsu TFT monitors
- Prev by thread: Re: networking trouble
- Next by thread: Re: networking trouble
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links