DHCP question

View: New views
20 Messages — Rating Filter:   Alert me  
< Prev | 1 - 2 | Next >

DHCP question

by Hari-26 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello. I just finished installing OpenBSD 4.3. The dhcp setup during
network configuration was fine, meaning, IP address was properly
assigned. I went ahead with the default values provided. However,
after rebooting post installation, I am getting the following messages
that seems to point to a network problem (and of course, no IP address
is assigned):

<messages>
fxp0: warning: SCB timed out (x 3)
fxp0: config command timeout
DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
send_packet: Network is down
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
</messages>

Several `intervals` are tried.

Dump of some relevant(?) files:

#ifconfig
lo0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
         groups: lo
         inet 127.0.0.1 netmask 0xff000000
         inet6 ::1 prefixlen 128
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
fxp0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
         lladdr 00:16:76:13:ad:54
         media: Ethernet autoselect (100baseTX full-duplex)
         status: active
         inet6 fe80::216::76ff::fe13::ad54%fxp0 prefixlen 64 tentative
scopeid 0x1
enc0: flags=0<> mtu 1536

#cat /etc/hosts:
::1 localhost.WORKGROUP locahost
127.0.0.1 localhost.WORKGROUP localhost
::1 mercury.WORKGROUP mercury
127.0.0.1 mercury.WORKGROUP mercury

#cat /etc/hostname.fxp0:
dhcp NONE NONE NONE

#cat /etc/resolv.conf
lookup file bind

# hostname
mercury.my.domain

#domainname

(none)

For my internet connection, I have a router that acts as a DHCP server
assigning IPs as 192.168.11.x. Why is the OpenBSD box not assigned an
IP by this router? Can anyone please let me know how I can get the
network up and running on the OpenBSD box?

Please let me know in case I have missed out on listing any config files.

Thanks.

Hari


Re: DHCP question

by Tomas Bodzar-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

$man fxp

timed out -> problem with network

from your post :
send_packet: Network is down

-----Original Message-----
From: owner-misc@... [mailto:owner-misc@...] On Behalf Of
Hari
Sent: Wednesday, July 23, 2008 9:33 AM
To: misc@...
Subject: DHCP question

Hello. I just finished installing OpenBSD 4.3. The dhcp setup during
network configuration was fine, meaning, IP address was properly
assigned. I went ahead with the default values provided. However,
after rebooting post installation, I am getting the following messages
that seems to point to a network problem (and of course, no IP address
is assigned):

<messages>
fxp0: warning: SCB timed out (x 3)
fxp0: config command timeout
DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
send_packet: Network is down
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
</messages>

Several `intervals` are tried.

Dump of some relevant(?) files:

#ifconfig
lo0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
         groups: lo
         inet 127.0.0.1 netmask 0xff000000
         inet6 ::1 prefixlen 128
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
fxp0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
         lladdr 00:16:76:13:ad:54
         media: Ethernet autoselect (100baseTX full-duplex)
         status: active
         inet6 fe80::216::76ff::fe13::ad54%fxp0 prefixlen 64 tentative
scopeid 0x1
enc0: flags=0<> mtu 1536

#cat /etc/hosts:
::1 localhost.WORKGROUP locahost
127.0.0.1 localhost.WORKGROUP localhost
::1 mercury.WORKGROUP mercury
127.0.0.1 mercury.WORKGROUP mercury

#cat /etc/hostname.fxp0:
dhcp NONE NONE NONE

#cat /etc/resolv.conf
lookup file bind

# hostname
mercury.my.domain

#domainname

(none)

For my internet connection, I have a router that acts as a DHCP server
assigning IPs as 192.168.11.x. Why is the OpenBSD box not assigned an
IP by this router? Can anyone please let me know how I can get the
network up and running on the OpenBSD box?

Please let me know in case I have missed out on listing any config files.

Thanks.

Hari


Re: DHCP question

by Hari-26 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 4:53 PM, Tomas Bodzar <Tomas.Bodzar@...> wrote:
> $man fxp
>
> timed out -> problem with network
>
> from your post :
> send_packet: Network is down

The network is good and working and this OpenBSD box is able to grab
an IP address during the initial network configuration during
installation*. I have checked the cables, etc....everything is fine.
Its only when I reboot post install, the network is not found and
consequently no IP is assigned.

* To verify this, I have reinstalled OpenBSD 4.3 multiple times (on
the same computer, same location). _Everytime_, an IP address is
assigned properly during the initial configuration.

Hari


Re: DHCP question

by Tomas Bodzar-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Ok.So next step.

$sudo ifconfig fxp0 dhcp up

gives what?

-----Original Message-----
From: Hari [mailto:innomotive@...]
Sent: Wednesday, July 23, 2008 10:00 AM
To: Tomas Bodzar
Cc: misc@...
Subject: Re: DHCP question

On Wed, Jul 23, 2008 at 4:53 PM, Tomas Bodzar <Tomas.Bodzar@...> wrote:
> $man fxp
>
> timed out -> problem with network
>
> from your post :
> send_packet: Network is down

The network is good and working and this OpenBSD box is able to grab
an IP address during the initial network configuration during
installation*. I have checked the cables, etc....everything is fine.
Its only when I reboot post install, the network is not found and
consequently no IP is assigned.

* To verify this, I have reinstalled OpenBSD 4.3 multiple times (on
the same computer, same location). _Everytime_, an IP address is
assigned properly during the initial configuration.

Hari


Re: DHCP question

by Hari-26 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 5:05 PM, Tomas Bodzar <Tomas.Bodzar@...> wrote:
> Ok.So next step.
>
> $sudo ifconfig fxp0 dhcp up
>
> gives what?

$sudo ifconfig fxp0 dhcp up
ifconfig: dhcp: bad value
$

:-(


Re: DHCP question

by Tomas Bodzar-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Eh,I missed something.Look at /etc/hosts and $hostname
Why is localhost.WORKGROUP localhost in /etc/hosts and
mercury.my.domain in $hostname ?

-----Original Message-----
From: owner-misc@... [mailto:owner-misc@...] On Behalf Of
Hari
Sent: Wednesday, July 23, 2008 9:33 AM
To: misc@...
Subject: DHCP question

Hello. I just finished installing OpenBSD 4.3. The dhcp setup during
network configuration was fine, meaning, IP address was properly
assigned. I went ahead with the default values provided. However,
after rebooting post installation, I am getting the following messages
that seems to point to a network problem (and of course, no IP address
is assigned):

<messages>
fxp0: warning: SCB timed out (x 3)
fxp0: config command timeout
DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
send_packet: Network is down
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
</messages>

Several `intervals` are tried.

Dump of some relevant(?) files:

#ifconfig
lo0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
         groups: lo
         inet 127.0.0.1 netmask 0xff000000
         inet6 ::1 prefixlen 128
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
fxp0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
         lladdr 00:16:76:13:ad:54
         media: Ethernet autoselect (100baseTX full-duplex)
         status: active
         inet6 fe80::216::76ff::fe13::ad54%fxp0 prefixlen 64 tentative
scopeid 0x1
enc0: flags=0<> mtu 1536

#cat /etc/hosts:
::1 localhost.WORKGROUP locahost
127.0.0.1 localhost.WORKGROUP localhost
::1 mercury.WORKGROUP mercury
127.0.0.1 mercury.WORKGROUP mercury

#cat /etc/hostname.fxp0:
dhcp NONE NONE NONE

#cat /etc/resolv.conf
lookup file bind

# hostname
mercury.my.domain

#domainname

(none)

For my internet connection, I have a router that acts as a DHCP server
assigning IPs as 192.168.11.x. Why is the OpenBSD box not assigned an
IP by this router? Can anyone please let me know how I can get the
network up and running on the OpenBSD box?

Please let me know in case I have missed out on listing any config files.

Thanks.

Hari


Re: DHCP question

by Hari-26 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 5:11 PM, Tomas Bodzar <Tomas.Bodzar@...> wrote:
> Eh,I missed something.Look at /etc/hosts and $hostname
> Why is localhost.WORKGROUP localhost in /etc/hosts and
> mercury.my.domain in $hostname

I have long suspected that this is the problem. I am a novice at this
and I have little understanding. I have gone through the man pages for
/etc/hosts but I could not figure out what exactly I was doing wrong.

What should /etc/hosts read as? And what should the $hostname be? The
machine is to be named "mercury".

> $sudo ifconfig fxp0 up
fxp0: warning: SCB timed out (x3)
fxp0: config command timeout

Hari


Re: DHCP question

by inna kholodova :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

did you try
'dhclient' ?

On Jul 23, 2008, at 1:08 PM, Hari wrote:

> On Wed, Jul 23, 2008 at 5:05 PM, Tomas Bodzar  
> <Tomas.Bodzar@...> wrote:
>> Ok.So next step.
>>
>> $sudo ifconfig fxp0 dhcp up
>>
>> gives what?
>
> $sudo ifconfig fxp0 dhcp up
> ifconfig: dhcp: bad value
> $
>
> :-(


Re: DHCP question

by Robert Blacquiere-8 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 05:08:31PM +0900, Hari wrote:
> On Wed, Jul 23, 2008 at 5:05 PM, Tomas Bodzar <Tomas.Bodzar@...> wrote:
> > Ok.So next step.
> >
> > $sudo ifconfig fxp0 dhcp up
> >
> > gives what?
>
> $sudo ifconfig fxp0 dhcp up
> ifconfig: dhcp: bad value

please try:

ps ax | grep dhclient

Is dhclient still running? if so please kill this process

$sudo pkill dhclient

Then try to get a lease

$sudo dhclient fxp0


Regards

Robert

--
Microsoft: Where do you want to go today?
Linux: Where do you want to go tomorrow?
FreeBSD: Are you guys coming or what?
OpenBSD: Hey guys you left some holes out there!


Parent Message unknown Re: DHCP question

by Tony Abernethy :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hari wrote:

>Hello. I just finished installing OpenBSD 4.3. The dhcp setup during
>network configuration was fine, meaning, IP address was properly
>assigned. I went ahead with the default values provided. However,
>after rebooting post installation, I am getting the following messages
>that seems to point to a network problem (and of course, no IP address
>is assigned):
>
><messages>
>fxp0: warning: SCB timed out (x 3)
>fxp0: config command timeout
>DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
>send_packet: Network is down
>No DHCPOFFERS received.
>No working leases in persistent database - sleeping.
></messages>
>
>Several `intervals` are tried.
>
>Dump of some relevant(?) files:
>
>#ifconfig
>lo0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
>         groups: lo
>         inet 127.0.0.1 netmask 0xff000000
>         inet6 ::1 prefixlen 128
>         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
>fxp0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
>         lladdr 00:16:76:13:ad:54
>         media: Ethernet autoselect (100baseTX full-duplex)
>         status: active
>         inet6 fe80::216::76ff::fe13::ad54%fxp0 prefixlen 64 tentative
>scopeid 0x1
>enc0: flags=0<> mtu 1536

Silly question, but WHAT IP is actually assigned during install?
I think something like ifconfig before the halt might work
I assume you are installing from CD, not from network
It might be as simple as a cable not completely plugged in.
Good Luck


Re: DHCP question

by Hari-26 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 5:36 PM, Tony Abernethy <tony@...> wrote:
> Silly question, but WHAT IP is actually assigned during install?
> I think something like ifconfig before the halt might work
> I assume you are installing from CD, not from network
> It might be as simple as a cable not completely plugged in.

IIRC, it was 192.168.11.8. The DNS was properly identified as the
router (192.168.11.1).

I dont think there is a problem with the cabling. (I double checked
this with a laptop).

Hari


Parent Message unknown Re: DHCP question

by Tony Abernethy :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hari wrote:

>On Wed, Jul 23, 2008 at 5:36 PM, Tony Abernethy <tony@...> wrote:
>> Silly question, but WHAT IP is actually assigned during install?
>> I think something like ifconfig before the halt might work
>> I assume you are installing from CD, not from network
>> It might be as simple as a cable not completely plugged in.
>
>IIRC, it was 192.168.11.8. The DNS was properly identified as the
>router (192.168.11.1).
>
>I dont think there is a problem with the cabling. (I double checked
>this with a laptop).
>
>Hari

If you got an IP, at lot of things have to be working.
?? What from /etc/hostname.fxp0


Re: DHCP question

by Almir Karic-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 04:33:27PM +0900, Hari wrote:

> Hello. I just finished installing OpenBSD 4.3. The dhcp setup during
> network configuration was fine, meaning, IP address was properly
> assigned. I went ahead with the default values provided. However,
> after rebooting post installation, I am getting the following messages
> that seems to point to a network problem (and of course, no IP address
> is assigned):
>
> <messages>
> fxp0: warning: SCB timed out (x 3)
> fxp0: config command timeout
> DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
> send_packet: Network is down
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> </messages>
>
> Several `intervals` are tried.
>
> Dump of some relevant(?) files:
>
> #ifconfig
> lo0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
>          groups: lo
>          inet 127.0.0.1 netmask 0xff000000
>          inet6 ::1 prefixlen 128
>          inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
> fxp0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208

isn't having LOOPBACK flag and mtu 33208 on a 'real' interface strange?


--
vi vi vi -- the number fo the beast


Re: DHCP question

by Hari-26 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 5:48 PM, Almir Karic <almir@...> wrote:
>> #ifconfig
>> lo0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
>>          groups: lo
>>          inet 127.0.0.1 netmask 0xff000000
>>          inet6 ::1 prefixlen 128
>>          inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
>> fxp0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
>
> isn't having LOOPBACK flag and mtu 33208 on a 'real' interface strange?

Apologies. This is my fault. I copied the text incorrectly.

#ifconfig

 lo0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
          groups: lo
          inet 127.0.0.1 netmask 0xff000000
          inet6 ::1 prefixlen 128
          inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
 fxp0: flags-8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500

Rest is OK.

Apologies once again.

Hari


Parent Message unknown Re: DHCP question

by Tony Abernethy :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hari wrote:

>On Wed, Jul 23, 2008 at 5:11 PM, Tomas Bodzar <Tomas.Bodzar@...> wrote:
>> Eh,I missed something.Look at /etc/hosts and $hostname
>> Why is localhost.WORKGROUP localhost in /etc/hosts and
>> mercury.my.domain in $hostname
>
>I have long suspected that this is the problem. I am a novice at this
>and I have little understanding. I have gone through the man pages for
>/etc/hosts but I could not figure out what exactly I was doing wrong.
>
>What should /etc/hosts read as? And what should the $hostname be? The
>machine is to be named "mercury".
>
>> $sudo ifconfig fxp0 up
>fxp0: warning: SCB timed out (x3)
>fxp0: config command timeout
>
>Hari
>

My (not so) humble opinion.
/etc/hosts is the poor man's DNS -- what name to what IP
::1 localhost.foo.bar localhost
127.0.0.1 localhost.foo.bar localhost
::1 gw.foo.bar gw this-box
192.168.10.1    gw this-box gw.foo.bar
192.168.10.22  that-box

Actually the local box can have a lot of names, all for the same IP.

Looks like your hostname goes into /etc/myname


Re: DHCP question

by Hari-26 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 5:57 PM, Tony Abernethy <tony@...> wrote:

> My (not so) humble opinion.
> /etc/hosts is the poor man's DNS -- what name to what IP
> ::1 localhost.foo.bar localhost
> 127.0.0.1 localhost.foo.bar localhost
> ::1 gw.foo.bar gw this-box
> 192.168.10.1    gw this-box gw.foo.bar
> 192.168.10.22  that-box
>
> Actually the local box can have a lot of names, all for the same IP.
>
> Looks like your hostname goes into /etc/myname

I just popped the CD in and the installation is on now. This is what
am getting during network configuration:

System hostname? mercury
Configure the network? [Yes]
Available interfaces are: fxp0
Which one do you want to initialize? (or 'done') [fxp0]
Symbolic (host) name for fxp0? [mercury]
The media options for fxp0 are currently
                media: Ethernet autoselect (qoobaseTX full-duplex)
Do you want to change the media options? [no]
IPv4 address for fxp0? (or 'none' or 'dhcp') dhcp
Issuing hostname-associated DHCP request for fxp0.
DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 2
DHCPOFFER from 192.168.11.1
DHCPREQUEST on fxp0 to 255.255.255.255 port 67
DHCPACK from 192.168.11.1
bound to 192.168.11.8 -- renewal in 86400 seconds
IPv6 address for fxp0? (or rtsol or none) [none]
No more interfaces to initialize.
DNS domain name? (e.g. 'bar.com') [my.domain]
DNS nameserver? (IP address or 'none') [192.168.11.1] none
Default IPv4 route? (IPv4 address, 'dhcp' or 'none') [dhcp]
Edit hosts with ed? [no]
Do you want to do any manual network configuration? [no]

After this, ifconfig on the system gives:

$ifconfig
lo: flags=8008<LOOPBACK,MULTICAST> mtu 33208
         groups: lo
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         lladdr 00:16:76:13:ad:54
         groups: dhcp egress
         media: Ethernet autoselect (100baseTX full-duplex)
         status: active
         inet6 fe80:216:76ff:fe13:ad54%fxp0 prefixlen 64 scopeid 0x1
         inet 192.168.11.8 netmask 0xffffff00 broadcast 192.168.11.255

After rebooting, the network is not up. Getting the error messages I
posted initially.

Hari


Re: DHCP question

by Robert Blacquiere-8 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 05:19:26PM +0900, Hari wrote:

> On Wed, Jul 23, 2008 at 5:11 PM, Tomas Bodzar <Tomas.Bodzar@...> wrote:
> > Eh,I missed something.Look at /etc/hosts and $hostname
> > Why is localhost.WORKGROUP localhost in /etc/hosts and
> > mercury.my.domain in $hostname
>
> I have long suspected that this is the problem. I am a novice at this
> and I have little understanding. I have gone through the man pages for
> /etc/hosts but I could not figure out what exactly I was doing wrong.
>
> What should /etc/hosts read as? And what should the $hostname be? The
> machine is to be named "mercury".
>
> > $sudo ifconfig fxp0 up
> fxp0: warning: SCB timed out (x3)
> fxp0: config command timeout

I thing here is the real problem. It seems the fxp0 interface fails to
do some initializing. This probably results in the interface not being
fully enabled/up.

I'me not sure what SCB is but i think is related to signaling / irq ?

Do you see this also with the bsd.rd kernel? Please look if there are
differences between the to in dmesg and ifconfig fxp0 ?

Regards

Robert

--
Microsoft: Where do you want to go today?
Linux: Where do you want to go tomorrow?
FreeBSD: Are you guys coming or what?
OpenBSD: Hey guys you left some holes out there!


Re: DHCP question

by Hari-26 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jul 23, 2008 at 6:16 PM, Robert Blacquiere
<guldan@...> wrote:
> I thing here is the real problem. It seems the fxp0 interface fails to
> do some initializing. This probably results in the interface not being
> fully enabled/up.
>
> I'me not sure what SCB is but i think is related to signaling / irq ?
>
> Do you see this also with the bsd.rd kernel? Please look if there are
> differences between the to in dmesg and ifconfig fxp0 ?

I checked dmesg and the output of 'ifconfig fxp0 up'. There is no
difference. The only time out messages listed in dmesg are from fxp0
(dmesg | grep -i time).

How do I check the SCB thing with the bsd.rd kernel?

Hari


Parent Message unknown Re: DHCP question

by Tony Abernethy :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Almir Karic wrote"

>On Wed, Jul 23, 2008 at 04:33:27PM +0900, Hari wrote:
>> Hello. I just finished installing OpenBSD 4.3. The dhcp setup during
>> network configuration was fine, meaning, IP address was properly
>> assigned. I went ahead with the default values provided. However,
>> after rebooting post installation, I am getting the following messages
>> that seems to point to a network problem (and of course, no IP address
>> is assigned):
>>
>> <messages>
>> fxp0: warning: SCB timed out (x 3)
>> fxp0: config command timeout
>> DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
>> send_packet: Network is down
>> No DHCPOFFERS received.
>> No working leases in persistent database - sleeping.
>> </messages>
>>
>> Several `intervals` are tried.
>>
>> Dump of some relevant(?) files:
>>
>> #ifconfig
>> lo0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
>>          groups: lo
>>          inet 127.0.0.1 netmask 0xff000000
>>          inet6 ::1 prefixlen 128
>>          inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
>> fxp0: flags-8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
>
>isn't having LOOPBACK flag and mtu 33208 on a 'real' interface strange?

mine shows  (normal) MTU 1500
Overlength packets are treated like errors by most everything. (IIRC)
# ifconfig fxp0
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:90:27:36:ef:22
        groups: egress
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 12.49.127.241 netmask 0xffffff80 broadcast 12.49.127.255
        inet6 fe80::290:27ff:fe36:ef22%