Re: what the $#@*
From: Bit Twister (BitTwister@localhost.localdomain)Date: 12/12/01
- Next message: WindersBoy: "Re: IPchains and FTP performance"
- Previous message: magikh0e@penguin-security.com: "Re: Snort woes"
- In reply to:(deleted message) Brad Olin: "what the $#@*"
- Next in thread: Trøütmån: "Re: what the $#@*"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: BitTwister@localhost.localdomain (Bit Twister) Date: Wed, 12 Dec 2001 21:48:20 GMT
In article <gdif1ucltqhfdopm77uqo9hgksp3r482so@4ax.com>, Brad Olin wrote:
>
> what is this? The mac address is not valid because it has way too many
> bits.
>
> Dec 12 12:56:40 ns1 kernel: INPUT DROP tcp IN=eth0 OUT=
> MAC=00:50:8b:6c:cb:19:00:02:16:64:94:79:08:00 SRC=12.237.169.255
> DST=XX.XX.XX.XX LEN=40 TOS=0x00 PREC=0x00 TTL=109 ID=1633 DF PROTO=TCP
> SPT=1204 DPT=80 WINDOW=0 RES=0x00 RST URGP=0
Well if you are using dhcpc, do a
cat /etc/dhcpc/dhcpcd-eth0.info
You may notice that the first half matches
DHCPCHADDR = Client's mac and the
DHCPSHADDR = dhcp Server's mac matches second half
- Next message: WindersBoy: "Re: IPchains and FTP performance"
- Previous message: magikh0e@penguin-security.com: "Re: Snort woes"
- In reply to:(deleted message) Brad Olin: "what the $#@*"
- Next in thread: Trøütmån: "Re: what the $#@*"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|