[ previous ] [ next ] [ threads ]
 
 From:  "Seth Martin" <SethM at turbinegenerator dot com>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] m0n0wall worked with SBC DSL, doesn't with Comcast Cable
 Date:  Fri, 27 May 2005 11:45:02 -0400
That is exactly what I did when I hooked mine up.

-----Original Message-----
From: Don Munyak [mailto:don dot munyak at gmail dot com] 
Sent: Friday, May 27, 2005 10:52 AM
To: Seth Martin
Cc: sleet71 dash m0n0wall at yahoo dot com; m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] m0n0wall worked with SBC DSL, doesn't with
Comcast Cable

I have comcast at home. Simply plugging in m0n0wall always gave me
problems. The steps I take which have yet to fail.

1. Power off Cable modem.
2. Power off m0n0wall.
3. Leave m0n0wall cat5 cables disconnected..ie WAN, LAN, OPT-1
4. Power on Cable Modem and let the CM goes through diagnostic startup
(3-5 minutes)
5. Power up m0n0wall and go through the "initial" config steps, where
you plug in each cable for auto-detect.

I have several CDROM and CF monowall loads that I play with. Following
these steps has never failed me.

I have never cloned the mac, added a hostname or password. Basically
left m0n0wall as DHCP.

- Don

On 5/27/05, Seth Martin <SethM at turbinegenerator dot com> wrote:
> I had to power cycle my Comcast modem, I didn't set a Mac though on
the
> monowall.  I just unplugged the modem for about 2-3minutes and then
> booted it back up.  For some reason just unplugging and re-plugging
> doesn't work, you have to let it sit unpowered for a few minutes for
it
> to flush its old Mac Records...  you tried doing a traceroute out to
an
> IP to see where its stalling out?  Is monowall even getting too the
> modem or is it stalling from the modem to its gateway?
> 
> -----Original Message-----
> From: Craig Williams [mailto:sleet71 dash m0n0wall at yahoo dot com]
> Sent: Thursday, May 26, 2005 11:37 PM
> To: m0n0wall at lists dot m0n0 dot ch
> Subject: Re: [m0n0wall] m0n0wall worked with SBC DSL, doesn't with
> Comcast Cable
> 
> Wow Jim, I'm aware of all that. The "big-I-Internet" huh?
> MAC address has been cloned (stated earlier)
> 
> m0n0wall WAN: 67.184.149.158/21
> m0n0wall LAN: 192.168.1.254/24
> 
> Cable modem: not sure - does it even get an address? SB5100 has a
status
> page at 192.168.100.1, but I'm not able to browse that when it is on
the
> outside edge of the m0n0wall.
> Browsing the cable modem (without m0n0wall) never indicates it has an
> IP. Just signal strength & MAC addresses are listed. Strange that I
can
> browse it when it is on the outside edge of the DLink. Thought I may
> need to setup a static route to it, but then the IP assigned to the
WAN
> interface is DHCP, so I can't create a route to it.
> 
> I use the LAN IP of the m0n0wall for default gateway (on the PC). It
is
> after all the router to get off the LAN. Default gateway the m0n0wall
> receives from Comcast: 67.184.144.1
> 
> 
> Jim Thompson <jim at netgate dot com> wrote:
> 
> Until m0n0 can ping hosts on the big-I-Internet, you'll have no luck
> getting out from 'behind' the NAT
> in m0n0wall.
> 
> What IP address/netmask does m0n0wall get via DHCP?
> 
> What is the IP address/mask of your LAN (or OPTn) interface?
> 
> What is the IP address/mask of your cable modem? (Does this match
> your default route?)
> 
> You might need to clone the MAC address of your notebook on the WAN
> interface.
> 
> jim
> 
> 
> On May 26, 2005, at 4:00 PM, Craig Williams wrote:
> 
> > M0n0wall WAN interface does get an IP.
> >
> >>> PC I did the setup on. The WAN interface gets an address, but I'm
> >>> not able to reach the internet.
> >>>
> > Pinging from M0n0wall diagnostics is always 100% loss.
> >
> > Bryan Kohlstedt wrote:
> > Log into m0n0wall and check to see if the wan interface picked up a
ip
> > address. Try pinging etc from the m0n0wall if it did pick up a
public
> > ip address. Let us know what happened and we can go from there. If
> > it's not even receiving a dhcp ip address let us know and we can go
> > from there.
> >
> > Bryan
> >
> > On 5/26/05, Jim Thompson wrote:
> >
> >> when you 'reach the Internet', do you show up as the IP address of
> >> the cable modem, or the one on your computer?
> >>
> >> (I'm wondering if the cable modem is also running NAT.)
> >>
> >> jim
> >>
> >> On May 26, 2005, at 1:28 PM, Craig Williams wrote:
> >>
> >>
> >>> I'm in the process of switching from SBC DSL to Comcast Cable
> >>> internet.
> >>> Got the Comcast up and running on a single PC.
> >>> Changed m0n0wall from PPPoE to DHCP, and entered the MAC from the
> >>> Rebooted both m0n0wall and the cable modem a LOT.
> >>> Tried setting the hostname too. Also did a factory reset on the
> >>> SB5100, and left it powered off for 5 minutes so it would "forget"
> >>> the MAC from the setup, and then configuring m0n0wall to not fake
> >>> the MAC. Just can't get it to work.
> >>>
> >>> Now when I configure my DLink 524 to do DHCP and plug the cable
> >>> modems ethernet into the WAN port there, everying it just fine.
> >>>
> >>> Are there any tips/tricks getting m0n0wall to work with DHCP/cable
> >>> versus of PPPoe?
> >>>
> >>>
> >>>
> >>
> >>
> >>
---------------------------------------------------------------------
> >> 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
> 
>