I wanted to say that I tried to use both distibutions: Dachstein and Bering
(and not together :-)). (And I still don't know which one
I should use.) Andi in BOTH distros I found this problem. At the and of this
file I'm sending all logs, which I made during my tests.
Sorry for this disorder, but I haven't that cable-modem at home (it's
located at my friend's flat in the same house). I haven't done any changes
in routing
(I've just configured network interfaces) at the original configuration.
But as I wrote: If I restarted computer (roter), it DOESN'T solve this
problem. ONLY possible solution is restart cable modem (power off them
for a while or press small button on it's back side). After that it's
possible to get new lease after restart.
And what about the idea from Alex Ryabtsev, that it could be with
full-duplex mode? I'm not sure in which mode the card is and i can check
it now, because I haven't this card at home just now.
And I've just downloaded new version of Bering, but I've founded some
strange things there (like upper-case commands and strange editor).
Shoud i use Bering or Dachstein for this applicaton?
Thanks, Vasek.
********************************************
Here are some logs from Dachstein:
--------------------------------------
Dachstein LEAF Firewall
:: Interfaces ::
1: lo: mtu 3924 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope global lo
2: eth0: mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:20:18:64:8e:7e brd ff:ff:ff:ff:ff:ff
inet 62.245.70.229/24 brd 62.245.70.255 scope global eth0
3: eth1: mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:40:33:da:f7:8b brd ff:ff:ff:ff:ff:ff
inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1
:: Routes ::
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
62.245.70.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 62.245.70.1 0.0.0.0 UG 0 0 0 eth0
--------------------------------
and ..........
---------------
Oct 13 20:32:26 M7r3f5 dhclient: ip length 328 disagrees with bytes received
332.
Oct 13 20:32:26 M7r3f5 dhclient: accepting packet with data after udp
payload.
Oct 13 20:32:26 M7r3f5 dhclient: DHCPOFFER from 10.0.255.1
Oct 13 20:32:28 M7r3f5 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port
67
Oct 13 20:32:28 M7r3f5 dhclient: ip length 328 disagrees with bytes received
332.
Oct 13 20:32:28 M7r3f5 dhclient: accepting packet with data after udp
payload.
Oct 13 20:32:28 M7r3f5 dhclient: DHCPACK from 10.0.255.1
Oct 13 20:32:33 M7r3f5 dhclient: bound to 62.24.66.141 -- renewal in 6600
seconds.
Oct 14 00:15:48 M7r3f5 dhclient: DHCPREQUEST on eth0 to 62.24.64.9 port 67
Oct 14 00:15:48 M7r3f5 dhclient: DHCPACK from 62.24.64.9
Oct 14 00:15:49 M7r3f5 dhclient: bound to 62.24.66.141 -- renewal in 6600
seconds.
-------------------------
I dont know, why is here DHCPACK from 10.0.255.1 and later DHCPACK from
62.24.64.9. ??????????????
??????????????????????
And why is the adress 10.0.255. I think it should be reserved for internal
networks. ???
***************************************************************************
In Bearing distro I found in log: (!!!)
Oct 14 23:13:05 firewall kernel: Shorewall:rfc1918:DROP:IN=eth0 OUT= MAC=
SRC=192.168.1.254 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=64
ID=8128 DF PROTO=UDP SPT=68 DPT=67 LEN=556
(Why is SRC=192.168.1.254 on eth0??????? This is IP of my router at internal
network!)
Oct 14 23:13:05 firewall kernel: Shorewall:rfc1918:DROP:IN=eth0 OUT=eth0
SRC=10.0.255.1 DST=62.245.70.176 LEN=328 TOS=0x00 PREC=0x00 TTL=62 ID=29104
PROTO=UDP SPT=67 DPT=68 LEN=308
Oct 14 23:13:05 firewall root: The /etc/shorewall/pump script is called with
arg up eth0 62.245.70.176
(Mayby some request from provider... ?)
??????
and also:
Oct 14 23:13:05 firewall pumpd[23772]: PUMP: got lease
Oct 14 23:13:05 firewall pumpd[23772]: intf: device: eth0
Oct 14 23:13:05 firewall pumpd[23772]: intf: set: 416
Oct 14 23:13:05 firewall pumpd[23772]: intf: bootServer: 62.24.64.9
Oct 14 23:13:05 firewall pumpd[23772]: intf: reqLease: 43200
Oct 14 23:13:05 firewall pumpd[23772]: intf: ip: 62.245.70.176
Oct 14 23:13:05 firewall pumpd[23772]: intf: next server: 62.24.64.9
Oct 14 23:13:05 firewall pumpd[23772]: intf: netmask: 255.255.255.0
Oct 14 23:13:05 firewall pumpd[23772]: intf: gateway: 62.245.70.1
Oct 14 23:13:05 firewall pumpd[23772]: intf: dnsServers[0]: 62.24.64.2
Oct 14 23:13:05 firewall pumpd[23772]: intf: dnsServers[1]: 62.24.64.3
Oct 14 23:13:05 firewall pumpd[23772]: intf: numDns: 2
Oct 14 23:13:05 firewall pumpd[23772]: intf: domain: mistral.cz
Oct 14 23:13:05 firewall pumpd[23772]: intf: broadcast: 62.245.70.255
Oct 14 23:13:05 firewall pumpd[23772]: intf: network: 62.245.70.0
*** That's all. *** Thanks again !!!!
---
Odchozí zpráva neobsahuje viry.
Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz).
Verze: 6.0.408 / Virová báze: 230 - datum vydání: 25.10.2002
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
