an the ISP?
Should I be worried about all this?
Yes, you should. Is it staticly configured or obtained from ISP's dhcp
I called my ISP, and this is apparently one of their servers. I don't
know why it's called user-whatever. So all is well on that front.
Regarding the original iss
> tcpdump -netttvvvSXi interfacename
>
> should show you something like
Here it is:
Feb 05 11:59:06.601418 0:b:6:bc:7b:e ff:ff:ff:ff:ff:ff 0806 60: arp
who-has 192.168.0.10 tell 24.145.134.116
: 0001 0800 0604 0001 000b 06bc 7b0e 1891 ...<{...
0010: 8674 c0a8
Aleksandar Milosevic wrote:
What does 'arp -a' and 'netstat -nr -f inet' output on rock?
# arp -a
chadmin (192.168.0.1) at 00:0b:06:bc:7b:0d on dc0
becket.dyndns.org (192.168.1.12) at 00:07:e9:d6:ea:fd on fxp0
? (192.168.1.32) at 00:0c:30:00:06:09 on fxp0
# netstat -nr -f inet
Routing tables
Also, I just noticed in my cable-modem box's configuration page that
the WAN gateway is 24.145.134.65, which reverse dns shows to be
user-0c931i1.cable.mindspring.com.
Isn't it odd that my gateway is another user rather than the ISP?
Should I be worried about all this?
J
Darren Spruell wrote:
As per above, the tcpdump output suggests a more likely
misconfiguration of the cable modem rather than the BSD box.
I'm starting to wonder if it's been deliberately (mis-)configured
this way.
Thinking to reconfigure the cable-modem box myself (as opposed to
going with th
On 2/5/07, Vijay Sankar <[EMAIL PROTECTED]> wrote:
On Monday 05 February 2007 11:55, J. Alfred Prufrock wrote:
>
> > tcpdump -netttvvvSXi interfacename
> >
> > should show you something like
>
> Here it is:
>
> Feb 05 11:59:06.601418 0:b:6:bc:7b:e ff:ff:ff:ff:ff:ff 0806 60: arp
> who-has 192.1
On Monday 05 February 2007 11:55, J. Alfred Prufrock wrote:
>
> > tcpdump -netttvvvSXi interfacename
> >
> > should show you something like
>
> Here it is:
>
> Feb 05 11:59:06.601418 0:b:6:bc:7b:e ff:ff:ff:ff:ff:ff 0806 60: arp
> who-has 192.168.0.10 tell 24.145.134.116
>: 0001 0800 0604
Vijay Sankar wrote:
> By the way, regarding list etiquette, I am copying you because you
> had asked for that in an earlier message. I should not have included
> Darren and John, but what happened was that I did a "Reply All", not
> noticing that you had sent the messages to those two folks as wel
On Sunday 04 February 2007 23:27, J. Alfred Prufrock wrote:
> Darren Spruell wrote:
> > Grab that exchange again with the -n flag to tcpdump. Include the MAC
> > address(es) of the cable modem if you can get them.
>
> Here it is:
>
> 00:14:04.475261 arp who-has 192.168.0.10 tell 24.aaa.bbb.ccc
>
Darren Spruell wrote:
Grab that exchange again with the -n flag to tcpdump. Include the MAC
address(es) of the cable modem if you can get them.
Here it is:
00:14:04.475261 arp who-has 192.168.0.10 tell 24.aaa.bbb.ccc
0001 0800 0604 0001 000b 06bc 7b0e 1891
Vijay Sankar wrote:
Possibly a silly question -- how are you connecting the cable modem to your
OpenBSD server's external interface? Are they all plugged into a switch or
hub or are you using a cable from the external interface directly to the
cable modem?
The external NIC connects directly t
On 2/4/07, J. Alfred Prufrock <[EMAIL PROTECTED]> wrote:
PS: I notice that when I reply-all to Vijay, Darren's and John's email
addresses also show up. What's the etiquette here? Should I reply
to just Vijay and misc, or to everyone whose address is included?
Or will the list-man
On 2/4/07, J. Alfred Prufrock <[EMAIL PROTECTED]> wrote:
tcpdump -vv -x -l results attached below.
I just ran tcpdump; here's the line at which I get the
error/warning/log message:
19:14:03.562039 arp who-has rock tell 24.aaa.bbb.ccc
[Note: 24.aaa.bbb.ccc is the cable-modem box's WAN address.]
On Sunday 04 February 2007 18:37, J. Alfred Prufrock wrote:
> Darren Spruell wrote:
> > It's curious that the outside interface address on the cable modem
> > is showing up for any reason on the internal network.
>
> Right, this is what first puzzled me too.
Possibly a silly question -- how are
Darren Spruell wrote:
> It's curious that the outside interface address on the cable modem
> is showing up for any reason on the internal network.
Right, this is what first puzzled me too.
> You might use tcpdump or similar on your internal network to
> determine what kind of traffic it relates
On 2/4/07, J. Alfred Prufrock <[EMAIL PROTECTED]> wrote:
John wrote:
> And, as far as getting the obsd box to talk to the modem was concerned,
> that's it! There is other stuff involved in getting the box to talk to
> the lan and v/v. I found it useful getting just the box to work with the
> mode
John wrote:
And, as far as getting the obsd box to talk to the modem was concerned,
that's it! There is other stuff involved in getting the box to talk to
the lan and v/v. I found it useful getting just the box to work with the
modem, it's not clear in your message if that is also your situation.
On Sat, Feb 03, 2007 at 03:31:08PM -0500, J. Alfred Prufrock wrote:
> Hi guys,
>
> I recently switched ISPs, and my new ISP (Time-Warner) gave me a
> Motorola SBG1000 cable-modem box. My OpenBSD machine, which used to
> connect directly to my old ISP's servers, is now behind this box. I'm
> runn
Hi guys,
I recently switched ISPs, and my new ISP (Time-Warner) gave me a
Motorola SBG1000 cable-modem box. My OpenBSD machine, which used to
connect directly to my old ISP's servers, is now behind this box. I'm
running a GENERIC 4.0 kernel which has never had any problems with my
hardware.
My
19 matches
Mail list logo
