[ previous ] [ next ] [ threads ]
 
 From:  "Barber, Patrick (MCI)" <patrick dot barber dash eds at eds dot com>
 To:  Jim Gifford <jim at giffords dot net>, "'m0n0wall at lists dot m0n0 dot ch'" <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Access to webGUI using generic-pc-1.0.img -more in fo
 Date:  Sat, 6 Mar 2004 18:27:39 -0000
Here goes I will cover everything I can with a windows laptop.

The IP address (output of ipconfig /all)

Windows IP Configuration          
Host Name . . . . . . . . . . . . : W2MZ062402         
Primary Dns Suffix  . . . . . . . :          
Node Type . . . . . . . . . . . . : Hybrid         
IP Routing Enabled. . . . . . . . : No         
WINS Proxy Enabled. . . . . . . . : No  
Ethernet adapter Local Area Connection:          
Connection-specific DNS Suffix  . : local         
Description . . . . . . . . . . . : Intel(R) PRO/100 SP Mobile Combo Adapter
Physical Address. . . . . . . . . : 00-03-47-8D-2B-31         
Dhcp Enabled. . . . . . . . . . . : Yes         
Autoconfiguration Enabled . . . . : Yes         
IP Address. . . . . . . . . . . . : 192.168.1.199         
Subnet Mask . . . . . . . . . . . : 255.255.255.0         
Default Gateway . . . . . . . . . : 192.168.1.1         
DHCP Server . . . . . . . . . . . : 192.168.1.1         
DNS Servers . . . . . . . . . . . : 192.168.1.1        
Lease Obtained. . . . . . . . . . : 06 March 2004 17:38:20         
Lease Expires . . . . . . . . . . : 06 March 2004 19:38:20 

My arp tables show (output of arp -a)
Interface: 192.168.1.199 --- 0x2
  Internet Address      Physical Address      Type
  192.168.1.1           4d-4d-00-00-00-00     dynamic   

Routing tables show
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1   192.168.1.199	  20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1	  1
      192.168.1.0    255.255.255.0    192.168.1.199   192.168.1.199	  20
    192.168.1.199  255.255.255.255        127.0.0.1       127.0.0.1	  20
    192.168.1.255  255.255.255.255    192.168.1.199   192.168.1.199	  20
        224.0.0.0        240.0.0.0    192.168.1.199   192.168.1.199	  20
  255.255.255.255  255.255.255.255    192.168.1.199   192.168.1.199	  1
Default Gateway:       192.168.1.1


The output of TCPDUMP shows everything as I would expect:

Aquiring an IP address:

18:10:38.665281 IP 0.0.0.0.68 > 255.255.255.255.67:  xid:0xae3e8b2c file
""[|bootp]
18:10:38.668243 IP m0n0wall.local > 192.168.1.199: icmp 28: echo request seq
0
18:10:39.396705 IP m0n0wall.local.67 > 192.168.1.199.68:  xid:0xae3e8b2c
Y:192.168.1.199 S:m0n0wall.local [|bootp]
18:10:39.397880 IP 0.0.0.0.68 > 255.255.255.255.67:  xid:0xae3e8b2c [|bootp]
18:10:39.403071 IP m0n0wall.local.67 > 192.168.1.199.68:  xid:0xae3e8b2c
Y:192.168.1.199 S:m0n0wall.local [|bootp]
18:10:39.413661 arp who-has 192.168.1.199 tell 192.168.1.199
18:10:39.443505 arp who-has 192.168.1.199 tell 192.168.1.199
18:10:40.445069 arp who-has 192.168.1.199 tell 192.168.1.199
18:10:41.474399 IP 192.168.1.199 > m0n0wall.local: icmp 40: echo request seq
768
18:10:41.506357 IP 192.168.1.199.1081 > 239.255.255.250.1900: udp 133
18:10:41.523610 IP 192.168.1.199.1084 > 239.255.255.250.1900: udp 133
18:10:41.524781 IP 192.168.1.199 > IGMP.MCAST.NET: igmp v3 report, 1 group
record(s)
18:10:41.526860 IP 192.168.1.199.137 > 192.168.1.255.137: udp 68
18:10:41.690607 IP 192.168.1.199.1047 > m0n0wall.local.53:  13+ PTR?
1.1.168.192.in-addr.arpa. (42)
18:10:41.691797 IP m0n0wall.local.53 > 192.168.1.199.1047:  13* 1/0/0
PTR[|domain]
18:10:42.277138 IP 192.168.1.199.137 > 192.168.1.255.137: udp 68
18:10:42.448062 IP 192.168.1.199 > IGMP.MCAST.NET: igmp v3 report, 1 group
record(s)
18:10:42.688830 IP 192.168.1.199.1047 > m0n0wall.local.53:  14+ PTR?
250.255.255.239.in-addr.arpa. (46)
18:10:42.689921 IP m0n0wall.local.53 > 192.168.1.199.1047:  14 NXDomain
0/0/0 (46)


When pinging 192.168.1.1

17:38:27.561635 IP W2MZ062402.local > m0n0wall.local: icmp 40: echo request
seq 1792
17:38:32.671367 IP W2MZ062402.local > m0n0wall.local: icmp 40: echo request
seq 2048
17:38:37.678854 IP W2MZ062402.local > m0n0wall.local: icmp 40: echo request
seq 2304
17:38:42.685725 IP W2MZ062402.local > m0n0wall.local: icmp 40: echo request
seq 2560


When trying to connect with web browser - proxy settings disabled URL =
http://192.168.1.1/

17:38:52.865198 IP W2MZ062402.local.1059 > m0n0wall.local.80: S
2512826859:2512826859(0) win 65520 <mss 1260,nop,nop,sackOK> (DF)
17:38:55.803683 IP W2MZ062402.local.1059 > m0n0wall.local.80: S
2512826859:2512826859(0) win 65520 <mss 1260,nop,nop,sackOK> (DF)
17:39:01.812318 IP W2MZ062402.local.1059 > m0n0wall.local.80: S
2512826859:2512826859(0) win 65520 <mss 1260,nop,nop,sackOK> (DF)

Here is an output of NMAP (nmap -sS -PT -PI -O -T 3 192.168.1.1)

Starting nmap V. 3.00 ( www.insecure.org/nmap )
Note: Host seems down. If it is really up, but blocking our ping probes, try
-P0
Nmap run completed -- 1 IP address (0 hosts up) scanned in 30 seconds


The image was written to a 3Gb hard drive with the commend:

Gunzip -c generic-pc-xxx.img | dd of=/dev/hdc bs=16k

As instructed on the website

Quite honestly I am stuck...everything seems ok and I don't think I could
provide any more information as there is no command line acces/tools on
m0n0...m0n0 is booting with no errors I can access the very limited menu via
the console cable, I can use the menu options through the console
cable...but I cannot access the webGUI or ping m0n0 on either a generic-pc,
or Nokia IP120 with a client attached to the LAN interface with a crossover
cable.

I get the same results with both pb27 or version 1.0.
 
-----Original Message-----
From: Jim Gifford [mailto:jim at giffords dot net] 
Sent: 05 March 2004 14:42
To: 'm0n0wall at lists dot m0n0 dot ch'
Subject: Re: [m0n0wall] Access to webGUI using generic-pc-1.0.img -more in
fo


Ok, I'll try a few more things.  What address are you getting from DHCP? By
default, the dynamic range is 192.168.1.100 through 192.168.1.199, and it
gives them out from the top down, so the first machine should get
192.168.1.199.  If this isn't what you see, then there's some other problem
here.  Also, after you get the DHCP lease, try seeing what your arp tables
look like.  That'd be arp -na under linux for example.  After that, check
your routing tables.  That'd be netstat -nr under linux.  If you can use a
linux box to test with, try running 'tcpdump -n -i eth0' before attempting
to access the web gui and see what kind of traffic you see.  Also, many web
browsers don't always treat a raw IP address as an IP address, and instead
try to do an automated internet search for it instead.  Make sure you use
http://192.168.1.1/ as the URL. Additionally, make sure you launch the web
browser *after* acquiring the DHCP lease.  Many web browsers will cache the
dns resolving stuff and ip address stuff upon startup, and won't always
behave properly if the network config changes after browser startup.

Oh yeah, while running tcpdump, see if you can ping 192.168.1.1, it should
respond to pings.

Hope this helps,
jim

On Fri, Mar 05, 2004 at 02:14:22PM -0000, Barber, Patrick (MCI) wrote:
> For testing to LAN interface I was using a cross over cable
> 
> -----Original Message-----
> From: Christiaens Joachim [mailto:jchristi at oce dot be]
> Sent: 05 March 2004 13:56
> To: 'Barber, Patrick (MCI)'
> Cc: 'm0n0wall at lists dot m0n0 dot ch'
> Subject: RE: [m0n0wall] Access to webGUI using generic-pc-1.0.img -more in
fo
> 
> 
> What about the connectivity? Are you using a hub / switch / router 
> between the m0n0 and the client or maybe a crossover cable? You said 
> you found no ports open, but DHCP works... broadcast VS unicast... 
> hmmm :-s
> 
> Joachim
> 
> > -----Original Message-----
> > From: Barber, Patrick (MCI) [mailto:patrick dot barber dash eds at eds dot com]
> > Sent: vrijdag 5 maart 2004 14:41
> > To: 'm0n0wall at lists dot m0n0 dot ch'
> > Subject: RE: [m0n0wall] Access to webGUI using generic-pc-1.0.img 
> > -more in fo
> > 
> > 
> > Was worth a try...my IE settings were originally with proxy server 
> > set, however I have firefox set with two profiles...one with proxy
> > server (wasn't
> > used) one without proxy server (used for testing)...
> > 
> > As another possible I tried using two separate PCs to access 
> > webGUI...my
> > laptop(w2k) using IE and firefox, and my desktop SuSE linux
> > running firefox.
> > 
> > Still no joy...
> > 
> > -----Original Message-----
> > From: Jim Gifford [mailto:jim at giffords dot net]
> > Sent: 05 March 2004 12:50
> > To: 'm0n0wall at lists dot m0n0 dot ch'
> > Subject: Re: [m0n0wall] Access to webGUI using
> > generic-pc-1.0.img -more in
> > fo
> > 
> > 
> > I ran into a situation yesterday where my laptop worked fine with 
> > m0n0wall, and 2 machines I tested with worked fine, but 5 other of 
> > the client's machines couldn't access the web gui.  I finally 
> > tracked it down to the
> > proxy server settings on those 5 machines being configured to 
> > use a proxy
> > that couldn't access the internal LAN addresses (the proxy 
> > was in the DMZ).
> > Once I disabled that, all 5 worked fine.  So, if you haven't 
> > already, try
> > disabling any proxy server configurations in IE.
> > 
> > I spent a good amount of time tracking this one down, as all the 
> > functional machines were on one side of the street and the "broken" 
> > ones were on the
> > other side of the street.  (the LAN has a 100Mbit fiber link under the
> > highway between the two facilities).  We were first looking 
> > for a link layer
> > problem because of the seeming geographic association of the problem.
> > 
> > hope this helps,
> > jim
> > 
> > On Fri, Mar 05, 2004 at 08:57:39AM -0000, Barber, Patrick (MCI) 
> > wrote:
> > > Tried the same image on a generic-pc with the same results...DHCP 
> > > server released an IP address, DHCP client received an IP address. 
> > > Tried access webGUI with Internet Exploder it timed out,
> > tried access
> > > webGUI with Mozilla Firefox it timed out.
> > > 
> > > I have also tried pb27 on the Nokia, and a generic PC with the 
> > > same reults....
> > > 
> > > Help...I really like the look of this product...it answers all my 
> > > problems...and I would really like to try it....
> > > 
> > > Patrick
> > > 
> > > -----Original Message-----
> > > From: Barber, Patrick (MCI)
> > > Sent: 04 March 2004 12:55
> > > To: 'm0n0wall at lists dot m0n0 dot ch'
> > > Subject: [m0n0wall] Access to webGUI using generic-pc-1.0.img
> > > 
> > > 
> > > Hi,
> > > I have installed the latest version onto a Harddisk, installed the 
> > > Harddisk into a Nokia IP120 which boots fine. The DHCP
> > client on the
> > > WAN interface gets an IP address from a DHCP server OK...the DHCP 
> > > server on LAN Interface is releasing IP addresses to clients OK. 
> > > However I cannot connect to the webGUI with a client on the LAN 
> > > interface.
> > > 
> > > 
> > > During Bootup messages I See the following message
> > > 
> > > IP Filter: v3.4.31 initialized.  Default = block all, Logging = 
> > > enabled
> > > 
> > > If I scan the m0n0wall with NMAP I see no ports open? Which
> > I think is
> > > abit strange as it is accepting and replying DHCP requests.
> > > 
> > > If I run tcpdump on the client I see the syn packets leave
> > the client
> > > going to m0n0wall on TCP port 80 but get no syn/ack packets.
> > > 
> > > 
> > > Can anyone please help?
> > > 
> > > 
> > > 
> > > --
> > > 
> > > Patrick Barber
> > > 
> > > 
> > > 
> > --------------------------------------------------------------------
> > -
> > > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> > > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> > > 
> > > 
> > --------------------------------------------------------------------
> > -
> > > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> > > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> > > 
> > 
> > --------------------------------------------------------------------
> > -
> > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> > 
> > --------------------------------------------------------------------
> > -
> > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> > 
> 
> 
> -----------------------------------------------
> MISSION STATEMENT
> -----------------------------------------------
> Oce enables its customers to manage their documents efficiently and
effectively by offering innovative print and document management products
and services for professional environments.
> 
> -----------------------------------------------
> DISCLAIMER
> -----------------------------------------------
> This e-mail message and any attachment are intended for the sole use of
the
> recipient(s) named above and may contain information which is confidential
and/or protected by intellectual property rights. Any use of the information
contained herein (including, but not limited to, total or partial
reproduction, communication or distribution in any form) by other persons
than the designated recipient(s) is prohibited.
> 
> If you have received this e-mail in error, please notify the sender 
> either by telephone (0032-2-729.48.11) or by e-mail and delete the 
> material from any computer. Oce-Belgium/Oce-Interservices is nor 
> responsible for the correct and complete transfer of the contents of 
> the sent e-mail, neither for the receipt on due time.  This e-mail 
> message does not bring about a contractual obligation for 
> Oce-Belgium/Oce-Interservices.
> 
> Thank you for your cooperation.
> 
> For further information about Oce-Belgium/Oce-Interservices please see 
> our website at www.oce.be
> 
> -----------------------------------------------
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch

---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch